02-21-2012 05:23 AM - edited 03-07-2019 05:04 AM
I am getting this error from Nexus 7K. What could it be?
2012 Feb 21 15:17:14 NX1-DataCenter %ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface Ethernet10/46 is down (
Administratively down)
2012 Feb 21 15:17:17 NX1-DataCenter %ETHPORT-5-IF_ADMIN_UP: Interface Ethernet10/46 is admin up .
2012 Feb 21 15:17:17 NX1-DataCenter %ETHPORT-5-IF_SEQ_ERROR: Error ("Connection timed out") communic
ating with MTS_SAP_PORT_CLIENT for opcode MTS_OPC_ETHPM_LCP_SET_PORT_CFG (RID_PORT: Ethernet10/46)
2012 Feb 21 15:17:17 NX1-DataCenter %ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet10/46 is do
wn (Error disabled. Reason:Connection timed out)
02-21-2012 05:34 AM
I also have this output:
Ethernet10/46 is down (Internal-Fail errDisable, (null): Connection timed out)
Dedicated Interface
Hardware: 1000 Ethernet, address: 4055.3924.2d42 (bia 30e4.dbef.b10d)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
auto-duplex, 1000 Mb/s, media type is 1G
Beacon is turned off
Auto-Negotiation is turned on
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
Last link flapped 00:06:00
Last clearing of "show interface" counters never
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 0 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
L3 in Switched:
ucast: 0 pkts, 0 bytes - mcast: 0 pkts, 0 bytes
L3 out Switched:
ucast: 0 pkts, 0 bytes - mcast: 0 pkts, 0 bytes
RX
54814594 unicast packets 197 multicast packets 594676 broadcast packets
55409467 input packets 9764736478 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
54175799 unicast packets 5020446 multicast packets 2696855 broadcast packets
61893100 output packets 21446629890 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
6 interface resets
02-22-2012 11:32 AM
Mohammed
I'd suggest you to contact TAC team. Message means that internal service "port-client" cannot reach the port for some reason.
HTH,
Alex
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide