Switch(config)# end\nSwitch# show ip redirects\n<\/code><\/pre>\nThe output displays the default gateway currently registered with the IP stack:<\/p>\n
Default gateway is 192.168.10.1\n\nHost Gateway\n<\/code><\/pre>\nYou can also confirm the command in the running configuration:<\/p>\n
Switch# show running-config | include ip default-gateway\nip default-gateway 192.168.10.1\n<\/code><\/pre>\n<\/span>Step 5: Save Changes to NVRAM<\/span><\/h3>\nCommit the active configuration to non-volatile memory so that it survives reboots:<\/p>\n
Switch# copy running-config startup-config\nDestination filename [startup-config]? [Enter]\nBuilding configuration...\n[OK]\n<\/code><\/pre>\n
\n<\/span>Boilerplate Configuration Template<\/span><\/h2>\nUse this self-contained script for new device provisioning or automated staging scripts. Replace bracketed placeholders (<...><\/code>) with your site-specific network parameters.<\/p>\n! ========================================================\n! CISCO CATALYST LAYER 2 MANAGEMENT BOILERPLATE TEMPLATE\n! ========================================================\nconfigure terminal\n\n! Step 1: Disable Global IP Routing (Enforces L2 behavior)\nno ip routing\n\n! Step 2: Define Management VLAN in Database\nvlan <VLAN_ID>\n name Management_Network\n exit\n\n! Step 3: Configure Management SVI\ninterface vlan <VLAN_ID>\n description Remote_In-Band_Management\n ip address <SWITCH_MGMT_IP> <SUBNET_MASK>\n no shutdown\n exit\n\n! Step 4: Configure Default Gateway\nip default-gateway <GATEWAY_IP>\n\n! Step 5: Optional - Basic Remote Access Prerequisites\nip domain-name <DOMAIN_NAME>\ncrypto key generate rsa modulus 2048\nline vty 0 15\n transport input ssh\n login local\n exit\n\nend\nwrite memory\n<\/code><\/pre>\n
\n<\/span>Configuring a Default Gateway in a Dedicated Management VRF<\/span><\/h2>\nModern enterprise platforms\u2014including Cisco Catalyst 9000 switches running Cisco IOS-XE and Cisco Nexus switches running NX-OS\u2014isolate out-of-band (OOB) management traffic from the global forwarding table using a dedicated Virtual Routing and Forwarding (VRF) instance (typically named Mgmt-vrf<\/code> on IOS-XE or management<\/code> on NX-OS). <\/p>\nBecause VRFs utilize distinct routing tables, the standard ip default-gateway<\/code> command does not apply to interfaces bound to a VRF. Instead, a static default route within that specific VRF must be defined.<\/p>\n<\/span>1. Cisco IOS-XE (Catalyst 9000 Out-of-Band Port GigabitEthernet0\/0<\/code>)<\/span><\/h3>\nStep 1: Associate Interface with the Management VRF<\/h4>\n
Enter the dedicated physical management interface, attach the pre-defined VRF, and assign its IP:<\/p>\n
Switch# configure terminal\nSwitch(config)# interface GigabitEthernet0\/0\nSwitch(config-if)# description Dedicated_Out-Of-Band_Port\nSwitch(config-if)# vrf forwarding Mgmt-vrf\nSwitch(config-if)# ip address 10.10.100.15 255.255.255.0\nSwitch(config-if)# no shutdown\nSwitch(config-if)# exit\n<\/code><\/pre>\nStep 2: Configure the Default Route within the Management VRF<\/h4>\n
Specify the next-hop gateway inside the VRF context:<\/p>\n
Switch(config)# ip route vrf Mgmt-vrf 0.0.0.0 0.0.0.0 10.10.100.1\nSwitch(config)# end\n<\/code><\/pre>\nStep 3: Validate VRF Connectivity<\/h4>\n
Ping the gateway explicitly referencing the VRF:<\/p>\n
Switch# ping vrf Mgmt-vrf 10.10.100.1\n<\/code><\/pre>\n
\n<\/span>2. Cisco NX-OS (Nexus Platform mgmt0<\/code>)<\/span><\/h3>\nNexus switches isolate the physical mgmt0<\/code> port into the management<\/code> VRF by default.<\/p>\nStep 1: Configure the mgmt0<\/code> Interface<\/h4>\nswitch# configure terminal\nswitch(config)# interface mgmt0\nswitch(config-if)# description OOB_Management\nswitch(config-if)# vrf member management\nswitch(config-if)# ip address 10.10.100.20\/24\nswitch(config-if)# no shutdown\nswitch(config-if)# exit\n<\/code><\/pre>\nStep 2: Define the Static Route within the management<\/code> VRF Context<\/h4>\nswitch(config)# vrf context management\nswitch(config-vrf)# ip route 0.0.0.0\/0 10.10.100.1\nswitch(config-vrf)# exit\nswitch(config)# copy running-config startup-config\n<\/code><\/pre>\nStep 3: Test Reachability<\/h4>\nswitch# ping 10.10.100.1 vrf management\n<\/code><\/pre>\n
\n<\/span>Troubleshooting Guide: Resolving Default Gateway Unreachability<\/span><\/h2>\nIf the switch cannot ping its default gateway or administrators cannot establish remote SSH sessions across subnets, proceed through these diagnostic checks:<\/p>\n
[Cannot Ping Gateway]\n \u2502\n \u25bc\n[Step 1: Check SVI Status] \u2500\u2500\u2500\u2500 (Down\/Down) \u2500\u2500\u2500\u25ba Verify physical port\/trunk exists & is up\n \u2502 (Up\/Up)\n \u25bc\n[Step 2: Check Routing State] \u2500\u2500 (`ip routing` on) \u2500\u25ba Remove gateway, configure `ip route 0.0.0.0`\n \u2502 (`no ip routing`)\n \u25bc\n[Step 3: Check Subnet\/IP] \u2500\u2500\u2500\u2500 (Mismatch) \u2500\u2500\u2500\u2500\u25ba Correct SVI mask & gateway IP to same subnet\n \u2502 (Correct)\n \u25bc\n[Step 4: Check ARP Table] \u2500\u2500\u2500\u2500 (Incomplete) \u2500\u2500\u25ba Check VLAN tagging, trunk allowlists, router SVI\n \u2502 (MAC Resolved)\n \u25bc\n[Step 5: Check Ping Source] \u2500\u2500\u25ba Test `ping <GW> source vlan <ID>` to verify control plane path\n<\/code><\/pre>\n<\/span>Step 1: Verify SVI Operational Status<\/span><\/h3>\nAn SVI remains down unless at least one access port in that VLAN is connected (up\/up<\/code>) or a trunk port carrying that VLAN is operational.<\/p>\nSwitch# show ip interface brief | include Vlan\nVlan10 192.168.10.15 YES manual up up\n<\/code><\/pre>\n\n- If Status is
down<\/code> or administratively down<\/code>:<\/strong> Run no shutdown<\/code> on the interface. Verify that the VLAN exists in the VLAN database (show vlan brief<\/code>) and that associated trunk\/access ports are physically connected.<\/li>\n<\/ul>\n<\/span>Step 2: Verify IP Routing Status<\/span><\/h3>\nIf someone enabled IP routing on a switch intended to function as Layer 2, the ip default-gateway<\/code> command is ignored.<\/p>\n