New switches and VTP headaches

[jayu]

Got in some new C9300L units, one L3 the other L2.  Setup VTP server on the L3 and all four VLAN's are showing up fine in the L2.  However, the L2 can't ping anything or be pinged by anything but the L3 switch it's directly connected to.  Both switches see each other in CDP/LLDP Neighbors.  I feel like I'm missing something super simple but my first discipline is not in Cisco so I'm grasping at straws.  

[MHM Cisco World]

for L2 to  ping you need 
ip defualt-gateway 

[jayu]

L2 Gateway is set to the SVI address of the L3 interface (Native VLAN IP).  I've had this set to the DG of the router and it made no difference.  I'm open to suggestions though.

[MHM Cisco World]

are you run any VRF for management ?

[jayu]

I have a VRF Management statement on the default 0/0 interface but that's not hooked into anything on either unit and the L3 is working fine (except not passing data from the L2 properly).  

[MHM Cisco World · Accepted solution]

remove the management VRF and try again.

[jayu]

When I try that, I get two errors.  The first is: Management interface VRF Mgmt-vrf can not be removed.

The second (trying to remove it from the default Gig0/0 interface) is Error in configuring Ethernet: No switchport

[MHM Cisco World]

show ip route 
and share the SW model and IOS Ver. 

[jayu]

Both switches are Cisco C9300L units running IOS 17.9.1.  

===================================================================================
#show ip route
Extended Host Mode is enabled
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, m - OMP
n - NAT, Ni - NAT inside, No - NAT outside, Nd - NAT DIA
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
H - NHRP, G - NHRP registered, g - NHRP registration summary
o - ODR, P - periodic downloaded static route, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR
& - replicated local route overrides by connected
Gateway of last resort is 192.168.4.3 to network 0.0.0.0
S* 0.0.0.0/0 [0/0] via 192.168.4.3
192.168.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 192.168.4.0/24 is directly connected, Vlan172
L 192.168.4.1/32 is directly connected, Vlan172
192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.1.0/24 is directly connected, Vlan100
L 192.168.1.1/32 is directly connected, Vlan100

[MHM Cisco World]

try this way 
ping x.x.x.x source vlan <x> <<<- VLAN IP 
if you success then 
this is bug and I will search and find this bug number and update you. 
note:- use the VLAN can access GW

[jayu]

From the L3 switch (the one that can ping everything) I can ping the L2 switch with normal command as well as the source VLAN command.  From L2 switch, I can't ping anything even with the source VLAN command.  

So, I found a VRF statement on the non-working switch and removed it.  I can now PING to the L3 switch it's directly connected to and up into the server stack.  Can you explain why VRF is so destructive that it would prevent this?

[MHM Cisco World]

Yes this simple L2 not L3 but still add VRF make connectivity issue. 
so I will search and check Cisco release note for 17.9.1., try to figure out why this happened or what is workaround instead of remove VRF.
If I get answer I will update you.

[jayu]

Thank you!  Your help has been much appreciated!

[jayu]

One more thing...minor really, but on the L2, though I can ping out from that unit, I can't ping that unit from my PC so I can't login remotely.  

And a curiosity I haven't looked into yet...but one of my VLAN's keeps bringing down the L3 unit (VLAN101).  I have tried different IP's and it'll stay up fine for a few minutes then crash.  I have to command-line in and disable the VLAN to get it back.  Once it comes back, it acts fine until I re-enable the VLAN.  The 101 is the more important one as it actually hosts the end-user PC's and will be necessary later on.

[MHM Cisco World]

you meaning the VLAN is UP for few time then down ? 
OK 
show vlan 
check which port connect to this VLAN 
then 
show spanning tree 
check the port is FWD or BLK ?