cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Join Customer Connection to register!
14374
Views
10
Helpful
3
Replies
shaunoc46
Beginner

Question regarding Management Interface on Nexus 5000

Not familiar with Nexus line and had a question about setting up the management interface on a Nexus 5010 switch.  I'm attempting to upload a new IOS and can't get connectivity.  Currently, I have a team of stacked Nexus 5010's connecting to a pair of access swtiches that are providing the connection to the core.  I understand this isn't best practice but it was our only option at the time.  Anyways each Nexus switch uses two ports for a vPC connection to the pair of redundant access switches and then each one of the management interfaces on the Nexus's are connected to these access switches as well.  I'm attempting to set up the clock and NTP servers as well for the Nexus switches but having some troubles getting the communication going.  I'm not able to ping anything from within the Nexus, even the IP address of the Nexus.  I'm able to ping and telnet to the Nexus from anywhere outside of Nexus.  When I attempt to ping from the Nexus I get a "no route to host" response.  There is a route to the gateway in place for the vrf context management.  Will I need to set up the access switch connecting to the Nexus to be a trunked port to allow all traffic?  Is it an option to do away with the managment interface IP and just assign a SVI for management reasons?  I ask the SVI question because the NTP servers are on a separate subnet than that of the IP address of the Nexus.  Below is some information on the configuration as it stands now.  Thanks in advance for any help!

Nexus 1

vrf context management
  ip route 0.0.0.0/0 10.31.35.1

vpc domain 10
  peer-keepalive destination 10.31.35.26

interface port-channel3  (assigned to int E1/1)
  switchport mode trunk
  vpc 3
  switchport trunk native vlan 70
  speed 1000
interface port-channel4 (assigned to int E1/2)
  switchport mode trunk
  vpc 4
  switchport trunk native vlan 70
  speed 1000

interface port-channel19 (assigned to int E1/19 & 20)
  description NexusUplinks
  switchport mode trunk
  vpc peer-link
  switchport trunk native vlan 70
  spanning-tree port type network
  speed 10000

interface mgmt0
  vrf member management
  ip address 10.31.35.25/24

Nexus 2

vrf context management
   ip route 0.0.0.0/0 10.31.35.1

vpc domain 10
   peer-keepalive destination 10.31.35.25

interface port-channel3  (assigned to int E1/1)
   switchport mode trunk
   vpc 3
   switchport trunk native vlan 70
   speed 1000
interface port-channel4 (assigned to int E1/2)
   switchport mode trunk
   vpc 4
   switchport trunk native vlan 70
   speed 1000

interface port-channel19 (assigned to int E1/19 & 20)
   description NexusUplinks
   switchport mode trunk
   vpc peer-link
   switchport trunk native vlan 70
   spanning-tree port type network
   speed 10000

interface mgmt0

  vrf member management

  ip address 10.31.35.26/24

Access switches connected to the management interfaces of the Nexus's are only set up as an access port and allowing only that certain vlan traffic to pass.  If I set the port to be a trunk port will the Cisco managment interface be able to pick that up or will it lose connection?

Thanks!

3 REPLIES 3
Jerry Ye
Cisco Employee

How did you issue the ping command? The correct syntex should be

ping x.x.x.x vrf management

If you are trying to do ping x.x.x.x, it will try to use the default vrf which has not interface and route, and you will get the No route to host message.

Example output from my lab N5K:

N5K1# ping 14.128.173.12
PING 14.128.173.12 (14.128.173.12): 56 data bytes
ping: sendto 14.128.173.12 64 chars, No route to host

--- 14.128.173.12 ping statistics ---
1 packets transmitted, 0 packets received, 100.00% packet loss
N5K1# ping 14.128.173.12 vrf management
PING 14.128.173.12 (14.128.173.12): 56 data bytes
64 bytes from 14.128.173.12: icmp_seq=0 ttl=254 time=3.33 ms
64 bytes from 14.128.173.12: icmp_seq=1 ttl=254 time=4.114 ms
64 bytes from 14.128.173.12: icmp_seq=2 ttl=254 time=3.873 ms
64 bytes from 14.128.173.12: icmp_seq=3 ttl=254 time=4.366 ms
64 bytes from 14.128.173.12: icmp_seq=4 ttl=254 time=3.739 ms

--- 14.128.173.12 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 3.33/3.884/4.366 ms

HTH,

jerry

Thanks

u mmm yea its a programing probem u need make new default1 call it put routeing in there save it u see only management port can use but cant be config to ping easy becuase lock down so easy fix i got a wire fiber traseaver set box 1000
next add new route called default1 added route there 0.0.0.0/0 192.x.x.x and work i mess with this week was no getting around management port did not want be put on same network as internet, now they may be real fix but only fix i ever found got fix today also dont forget to add the cisco snmp part as cicso uploads updates to it