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

Nexus 4k error disable

Anyone ever seen this before? Trying to understand why the port error disabled.

2011 Jan 18 11:53:09 MTWDAVDC1BLDB9001 %ETHPORT-2-IF_DOWN_ERROR_DISABLED: Interface Ethernet1/1 is down (Error disabled. Reason:requested by sap: MTS_SAP_DCX, req down_type: 2, req down_reason: 222 )

MTWDAVDC1BLDB9002# sh int eth1/1

Ethernet1/1 is down (DcxMultipleMSAPs)

  Hardware: 1000/10000 Ethernet, address: 0027.0d23.4d8d (bia 0027.0d23.4d8d)

  MTU 1500 bytes, BW 1000000 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

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

  Rate mode is dedicated

  Switchport monitor is off

  Last link flapped 1d03h

  Last clearing of "show interface" counters never

  1 minute input rate 0 bits/sec, 0 packets/sec

  1 minute output rate 0 bits/sec, 0 packets/sec

  Rx

    153349455 input packets 143221479 unicast packets 3730739 multicast packets

    6397237 broadcast packets 0 jumbo packets 0 storm suppression packets

    66448449173 bytes

  Tx

    328643307 output packets 90031378 multicast packets

    113132871 broadcast packets 12877361 jumbo packets

    62121338327 bytes

    0 input error 0 short frame 0 watchdog

    0 no buffer 0 runt 0 CRC 0 ecc

    0 overrun  0 underrun 0 ignored 0 bad etype drop

    0 bad proto drop 0 if down drop 0 input with dribble

    1416 input discard

    0 output error 0 collision 0 deferred

    0 late collision 0 lost carrier 0 no carrier

    0 babble

    0 Rx pause 0 Tx pause

  8 interface resets

2 REPLIES 2
Highlighted
Cisco Employee

I looked into the error and would suggest opening a TAC case so our engineering team can look into this error.  You can open a case using the supportforum as well to turn the thread into a case.

Sorry to not be able to help more, but looks like our internal team needs to look into this further.

Chad

Highlighted

I have seen the same error on occasion in a FCOE\ IBM blade chassis environment.