cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1165
Views
0
Helpful
3
Replies

Troubleshooting SVI issue on Nexus 5010

Hello Experts,

 

I turn my head towards you again seeking inputs to resolve an issue in bringing up a SVI on Nexus 5010 that I want to use for Peer-keepalive.

 

I have similar config on both 5010's. However, SVI on switch is up and not on other. 

 

For now, I have peer-keepalive up and running on management interface.

 

Switch 1:

Vlan1009 is down, line protocol is down
Hardware is EtherSVI, address is 0005.73c3.a6fc
Internet Address is 1.1.2.1/30
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec

 

ping 1.1.2.1 vrf keepalive-vpc
PING 1.1.2.1 (1.1.2.1): 56 data bytes
ping: sendto 1.1.2.1 64 chars, No route to host
Request 0 timed out
ping: sendto 1.1.2.1 64 chars, No route to host
Request 1 timed out
ping: sendto 1.1.2.1 64 chars, No route to host
Request 2 timed out
ping: sendto 1.1.2.1 64 chars, No route to host
Request 3 timed out
ping: sendto 1.1.2.1 64 chars, No route to host
Request 4 timed out

 

show ip route vrf keepalive-vpc
IP Route Table for VRF "keepalive-vpc"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]

 =========================================================================

Switch 2:

Vlan1009 is up, line protocol is up
Hardware is EtherSVI, address is 0005.73c3.a6bc
Internet Address is 1.1.2.2/30
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec

 

ping 1.1.2.2 vrf keepalive-vpc
PING 1.1.2.2 (1.1.2.2): 56 data bytes
64 bytes from 1.1.2.2: icmp_seq=0 ttl=255 time=0.619 ms
64 bytes from 1.1.2.2: icmp_seq=1 ttl=255 time=0.484 ms
64 bytes from 1.1.2.2: icmp_seq=2 ttl=255 time=0.473 ms
64 bytes from 1.1.2.2: icmp_seq=3 ttl=255 time=0.46 ms
64 bytes from 1.1.2.2: icmp_seq=4 ttl=255 time=0.796 ms

 

show ip route vrf keepalive-vpc
IP Route Table for VRF "keepalive-vpc"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]

1.1.2.0/30, ubest/mbest: 1/0, attached, pending
*via 1.1.2.2, Vlan1009, [0/0], 01:56:53, direct
1.1.2.2/32, ubest/mbest: 1/0, attached, pending
*via 1.1.2.2, Vlan1009, [0/0], 01:56:53, local

 

What am I missing here?

 

-Raghav

3 Replies 3

Kirk J
Cisco Employee
Cisco Employee

Greetings.

Can you confirm the feature is enabled?

#show feature | in en

and make sure you see

interface-vlan 1 enabled

?

 

Thanks,

Kirk...

Hi Kirk,

 

Thanks for your time, I verified and see interface-vlan 1 is enabled.

 

sh feature | i en
dhcp 1 enabled
fex 1 enabled
hsrp_engine 1 disabled
interface-vlan 1 enabled
lacp 1 enabled
lldp 1 enabled
sshServer 1 enabled
tacacs 1 enabled
udld 1 enabled
vpc 1 enabled

 

sh int vlan 1
Vlan1 is administratively down, line protocol is down
Hardware is EtherSVI, address is 0005.73c3.a6bc
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec

 

_Raghav.

Make sure both the vlan and the vlan interface have 'no shut' applied.

Also, do you have any physical interfaces that allow the vlan in question on the 1st switch?

 

Thanks,

Kirk...

Review Cisco Networking for a $25 gift card