cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6408
Views
0
Helpful
11
Replies
Highlighted
Beginner

Connecting Nexus 5548 to Catalyst 6500 VS S720 - 10 G

good day,

Could anyone out-there please assit me with basic connectivity/configuration of the 2 devices for the 2 devcies communicate e.g be able to ping each other managemnet interfaces.

Nexus Configuration:

vrf context management

  ip route 0.0.0.0/0 10.200.1.4

vlan 1

interface mgmt0

  ip address 10.200.1.2/16

Catalyst 6500:

interface Vlan1

description Nexus

ip address 10.200.1.4 255.255.0.0

!

interface TenGigabitEthernet5/4

switchport

Note: I am able to get all the devices throught SH CDP NEIG command. assist please.

11 REPLIES 11
Highlighted
Beginner

I can't even ping the mgmt0 interface from the same Nexus switch guys

Highlighted

In order to issue a ping from the 5K you need to add the vrf to the command: ping x.x.x.x vrf management

Bill

Sent from Cisco Technical Support iPad App

Highlighted

I did try that but still nothing. I even tried to ping the mgmt0 interface from the same nexus but nothing again

Highlighted

Is MGMT0 connected and what is it connected to?

Highlighted

MGMT0 is connected to a catalyst 3560 access port, with a UTP. The catalyst 3560 management vlan (vlan 1) is on the same subnet with the mgmt0, but I can still not ping either of the devices.

I tried to configure default gateway to point to the 3560, and even 6500 management vlans, still nothing. Still on that default configuration, which address should I really use as the next hop under mgmt0?

Highlighted

That's strange.   If MGMT0 is up, you should be able to ping it from the same 5548.   I have 5548s attached to a management 4948's access ports in vlan3.  The 4948 has a vlan3 uplink port connected to a router that I use as my default gateway, as you might expect.   Shouldn't matter much though... even if your 5548 mgmt0 is only attached to the 3560 and the 3560's managment IP is in the same vlan as the 5548's port... you should still be able to ping each other and yourself.

Try these commands from the console of your 5548 (substitute your own IP address) and show us the output:

N5K# show ip int mgmt0
IP Interface Status for VRF "management"(2)
mgmt0, Interface status: protocol-up/link-up/admin-up, iod: 2,
  IP address: 10.13.37.201, IP subnet: 10.13.37.128/25
  IP broadcast address: 255.255.255.255
  IP multicast groups locally joined:
      224.0.0.2  224.0.0.1  239.255.70.83 
  IP MTU: 1500 bytes (using link MTU)
  IP primary address route-preference: 0, tag: 0
  IP proxy ARP : disabled
  IP Local Proxy ARP : disabled
  IP multicast routing: disabled
  IP icmp redirects: enabled
  IP directed-broadcast: disabled
  IP icmp unreachables (except port): disabled
  IP icmp port-unreachable: enabled
  IP unicast reverse path forwarding: none
  IP load sharing: none
  IP interface statistics last reset: never
  IP interface software stats: (sent/received/forwarded/originated/consumed)
    Unicast packets    : 11178416/11024843/7087/11171329/0
    Unicast bytes      : 1051235718/1328146522/1603811/1049631907/0
    Multicast packets  : 145190/695168/0/145190/549780
    Multicast bytes    : 23328532/92704168/0/23328532/83603616
    Broadcast packets  : 0/0/0/0/0
    Broadcast bytes    : 0/0/0/0/0
    Labeled packets    : 0/0/0/0/0
    Labeled bytes      : 0/0/0/0/0

N5K# show cdp nei

Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge

                  S - Switch, H - Host, I - IGMP, r - Repeater,

                  V - VoIP-Phone, D - Remotely-Managed-Device,

                  s - Supports-STP-Dispute, M - Two-port Mac Relay

Device ID              Local Intrfce   Hldtme  Capability  Platform      Port ID
netmgmt4948        mgmt0           174     R S I       WS-C4948      Gig1/16     

N5K# ping 10.13.37.201 vrf management
PING 10.13.37.201 (10.13.37.201): 56 data bytes
64 bytes from 10.13.37.201: icmp_seq=0 ttl=255 time=0.33 ms
64 bytes from 10.13.37.201: icmp_seq=1 ttl=255 time=0.259 ms
64 bytes from 10.13.37.201: icmp_seq=2 ttl=255 time=0.328 ms
64 bytes from 10.13.37.201: icmp_seq=3 ttl=255 time=0.326 ms
64 bytes from 10.13.37.201: icmp_seq=4 ttl=255 time=0.327 ms

--- 10.13.37.201 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.259/0.313/0.33 ms

Highlighted

Nexus# sh ip int mgmt0

IP Interface Status for VRF "management"(2)

mgmt0, Interface status: protocol-up/link-up/admin-up, iod: 2,

IP address: 10.13.37.201, IP subnet: 10.13.37.128/25

IP broadcast address: 255.255.255.255

IP multicast groups locally joined: none

IP MTU: 1500 bytes (using link MTU)

IP primary address route-preference: 0, tag: 0

IP proxy ARP : disabled

IP Local Proxy ARP : disabled

IP multicast routing: disabled

IP icmp redirects: enabled

IP directed-broadcast: disabled

IP icmp unreachables (except port): disabled

IP icmp port-unreachable: enabled

IP unicast reverse path forwarding: none

IP load sharing: none

IP interface statistics last reset: never

IP interface software stats: (sent/received/forwarded/originated/consumed)

Unicast packets : 0/83401/0/20/20

Unicast bytes : 0/8083606/0/1680/1680

Multicast packets : 0/18518/0/0/0

Multicast bytes : 0/3120875/0/0/0

Broadcast packets : 0/285/0/0/0

Broadcast bytes : 0/98090/0/0/0

Labeled packets : 0/0/0/0/0

Labeled bytes : 0/0/0/0/0

Nexus# sh cdp nei

Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge

S - Switch, H - Host, I - IGMP, r - Repeater,

V - VoIP-Phone, D - Remotely-Managed-Device,

s - Supports-STP-Dispute

Device-ID Local Intrfce Hldtme Capability Platform Port ID

3560 mgmt0 178 S I WS-C3560-24PS Fas0/23

6500 Eth1/32 135 R S I WS-C6509-E Ten5/4

Nexus# ping 10.13.37.201 vrf management

PING 10.13.37.201 (10.13.37.201): 56 data bytes

64 bytes from 10.13.37.201: icmp_seq=0 ttl=255 time=0.278 ms

64 bytes from 10.13.37.201: icmp_seq=1 ttl=255 time=0.174 ms

64 bytes from 10.13.37.201: icmp_seq=2 ttl=255 time=0.169 ms

64 bytes from 10.13.37.201: icmp_seq=3 ttl=255 time=0.165 ms

64 bytes from 10.13.37.201: icmp_seq=4 ttl=255 time=0.165 ms

--- 10.13.37.201 ping statistics ---

5 packets transmitted, 5 packets received, 0.00% packet loss

round-trip min/avg/max = 0.165/0.19/0.278 ms

Nexus# ping 10.13.37.202

PING 10.13.37.202 (10.13.37.202): 56 data bytes

ping: sendto 10.13.37.202 64 chars, No route to host

Request 0 timed out

ping: sendto 10.13.37.202 64 chars, No route to host

Request 1 timed out

ping: sendto 10.13.37.202 64 chars, No route to host

Request 2 timed out

ping: sendto 10.13.37.202 64 chars, No route to host

Request 3 timed out

ping: sendto 10.13.37.202 64 chars, No route to host

Request 4 timed out

--- 10.13.37.202 ping statistics ---

5 packets transmitted, 0 packets received, 100.00% packet loss

Nexus# ping 10.13.37.203

PING 10.13.37.203 (10.13.37.203): 56 data bytes

ping: sendto 10.13.37.203 64 chars, No route to host

Request 0 timed out

ping: sendto 10.13.37.203 64 chars, No route to host

Request 1 timed out

ping: sendto 10.13.37.203 64 chars, No route to host

Request 2 timed out

ping: sendto 10.13.37.203 64 chars, No route to host

Request 3 timed out

ping: sendto 10.13.37.203 64 chars, No route to host

Request 4 timed out

--- 10.13.37.203 ping statistics ---

5 packets transmitted, 0 packets received, 100.00% packet loss

3560#ping 10.13.37.201

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.13.37.201, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

Note: Now I want to be able to ping Nexus (10.13.37.201) from the 6509 (10.13.37.203), and again be able to ping both the 3560 (10.13.37.202) and 6509 (10.13.37.203) from the Nexus please. How can I do that. I can ping nexus from 3560 as shown above.

Highlighted

The Nexuses have what I would call a "true" management interface, where the Catalyst 3560 and 6500 has a "virtual" management interface.   You must talk to the Nexus via the mgmt0 physical interface.  Where the 3560 and 6500 will respond across any link that carries the vlan... the Nexus will not.   See the attached example.  

The link between the 6500 and the 3560 could be a trunk that carries vlan3 instead of an access port.   There could be a link between the 6500 and the Nexus... but you can't use that to talk to the management interface.   That must be done across mgmt0.

On the Nexus, you must use the "vrf management" at the end of any ping for it to work  

I hope this helps!

Andy

Highlighted

Thank you very much, I now understand how this thing works....

So if I was to get away with the 3560, I must have two connections into the 6500, one through the 6500 uplink to the Ethernet interface in the nexus and then one connection through one of the 6500 Ethernet interfaces to mgmt0. Thats when I will be able to ping each deveice, and ofcourse this will be through the management interface only. Cooool

Thanks hey....

Highlighted

Yes, what you propose will work fine, especially if you only have one 5548.   Best practice would suggest that once you have more than one 5K, and if you want to tie them together for vPC operations, you should use a separate out-of-band switch to tie the management ports together.  We re-used an older 4948 for this purpose, but about anything would work.  I'm under the impression Cisco is moving away from the virtual management interface concept and toward a true management port.   The new 6500 Sup-2T appears to be this way, as are all the Nexus family.

Highlighted

Thats cool. I am new on Nexus equipment and believw slowly I will get to understand them better

This widget could not be displayed.