Tuesday, October 23, 2018

Why isn't this VLAN interface being added to the routing tables on a Cisco 9300 stack?

I’ve configured VLAN 100 on my soon-to-be core 9300 stack for a routed transit network to my edge firewalls. It’s configured similarly to all of the Access VLANs on the stack:

! interface Vlan100 description EDGE_TRANSIT ip address 10.1.100.101 255.255.255.252 ! 

However the network isn’t showing up in the routing table, and even though the command “ip default-network 10.1.100.102” is in the running-config it’s still not showing up in the routing table as having a gateway of last resort:

Gateway of last resort is not set 10.0.0.0/8 is variably subnetted, 26 subnets, 2 masks C 10.1.12.0/24 is directly connected, Vlan12 L 10.1.12.1/32 is directly connected, Vlan12 C 10.1.13.0/24 is directly connected, Vlan13 L 10.1.13.1/32 is directly connected, Vlan13 C 10.1.14.0/24 is directly connected, Vlan14 L 10.1.14.1/32 is directly connected, Vlan14 C 10.1.15.0/24 is directly connected, Vlan15 L 10.1.15.1/32 is directly connected, Vlan15 C 10.1.16.0/24 is directly connected, Vlan16 L 10.1.16.1/32 is directly connected, Vlan16 C 10.1.17.0/24 is directly connected, Vlan17 L 10.1.17.1/32 is directly connected, Vlan17 C 10.1.18.0/24 is directly connected, Vlan18 L 10.1.18.1/32 is directly connected, Vlan18 C 10.1.19.0/24 is directly connected, Vlan19 L 10.1.19.1/32 is directly connected, Vlan19 C 10.1.20.0/24 is directly connected, Vlan20 L 10.1.20.1/32 is directly connected, Vlan20 C 10.1.28.0/24 is directly connected, Vlan28 L 10.1.28.1/32 is directly connected, Vlan28 C 10.1.60.0/24 is directly connected, Vlan60 L 10.1.60.6/32 is directly connected, Vlan60 C 10.1.70.0/24 is directly connected, Vlan70 L 10.1.70.1/32 is directly connected, Vlan70 C 10.1.200.0/24 is directly connected, Vlan200 L 10.1.200.1/32 is directly connected, Vlan200 

Why isn’t that network for VLAN 100 showing up in the routing table, and why isn’t it taking the default-network command?



No comments:

Post a Comment