Connect VNX 5400 Data Movers to Nexus 7k Trouble

172.16.147.1 is your default gateway ? In the ping command Is the interface name correct, shouldn't it be VNX2_INT_147 ?

Are you sure MTU is correct with 1500 ?

In order to see if the physical connection is ok run a “server_log server_2 –f” and then unplug and replug the cable

You should see messages about the device going down and up

can you post output from this command:

server_sysconfig server_2 -virtual -info VNX2_LA

I will try that as soon as i get a chance Rainer.

Yes, 172.16.147.1 is the gateway.  I only get the option for 172.16.147.9 as the interface, it doesn't show the name of the interface.

you links are down and of course port-channel is offline too. Did your vCP configuration take those ports offline, until you get a link light nothing will work. Safe to assume you are using optical with multi-mode fiber or active twinax ?

Using 10Gb Duplex Multimode 50/125 OM3 Fiber Patch Cables.  I don't think the ports have ever had a link light.  I first tried connecting just one port without the vpc and that didn't work either.

Rainer:

The ports are set at MTU 1500.  Here is the show int for the port.

I ran the server_log server_2 -f  then unplugged and replugged the ports and there were no entries in the log for it.

Ethernet1/20 is up

  Dedicated Interface

  Belongs to Po120

  Hardware: 10000 Ethernet, address: ccef.4806.b857 (bia ccef.4806.b857)

  Description: to VNX2 for File A0

  MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec

  reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA

  Port mode is trunk

  full-duplex, 10 Gb/s, media type is 10G

  Beacon is turned off

  Auto-Negotiation is turned off

  Input flow-control is off, output flow-control is off

  Rate mode is shared

  Switchport monitor is off

  EtherType is 0x8100

  Last link flapped 00:22:35

  Last clearing of "show interface" counters 4d16h

  30 seconds input rate 0 bits/sec, 0 packets/sec

  30 seconds output rate 160304 bits/sec, 182 packets/sec

  Load-Interval #2: 5 minute (300 seconds)

    input rate 0 bps, 0 pps; output rate 140.66 Kbps, 102 pps

  RX

    0 unicast packets  0 multicast packets  0 broadcast packets

    0 input packets  0 bytes

    0 jumbo packets  0 storm suppression packets

    0 runts  0 giants  0 CRC  0 no buffer

    0 input error  0 short frame  0 overrun   0 underrun  0 ignored

    0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop

    0 input with dribble  0 input discard

    0 Rx pause

  TX

    1465896 unicast packets  45022709 multicast packets  17816334 broadcast packets

    64304939 output packets  6874971365 bytes

    0 jumbo packets

    0 output error  0 collision  0 deferred  0 late collision

    0 lost carrier  0 no carrier  0 babble  0 output discard

    0 Tx pause

  24 interface resets

dynamox, here is the output:

[nasadmin@NWT-VNX-cs0 ~]$ server_sysconfig server_2 -virtual -info VNX2_LA

server_2 :

*** Trunk VNX2_LA: Link is Down ***

*** Trunk VNX2_LA: Timeout is Short ***

*** Trunk VNX2_LA: Statistical Load Balancing is IP ***

Device     Local Grp   Remote Grp Link  LACP Duplex Speed    

------------------------------------------------------------------------

fxg-1-0    10001       0          Down  Down N/A         0 Mbs

fxg-1-1    10001       0          Down  Down N/A         0 Mbs

something with physical layer/switch, did you try to move this cable to standby datamover ? This will rule out datamover NIC being the issue. Are you going through any patch panels ? If yes you might have to swap RX/TX on the cable.

If you have the interface configured and up on the VNX you need to get a ink light and en entry in the server log

If not its most likely not a problem on the VNX side

The cables go directly from the data mover to the nexus, no patch panels.  I moved both cables to the other data mover and still didn't get link lights.  Do i need to fail over to the other data mover before it would get a link?  The nexus shows a link light on both ports when they are connected.

standby interfaces are up all the time, should get link light as well.

Thanks for the help Guys.  The problem was the GBICs in the nexus and the VNX had different wavelengths.  I fixed that and changed the port-channel mode to active instead of on and now i am able to ping the interface.

Yes – wrong GbiCs would be a problem