Guest

Preview Tool

Cisco Bug: CSCul47417 - Port-Channel not working on Nexus 6004

Last Modified

Jun 18, 2014

Products (7)

  • Cisco Nexus 6000 Series Switches
  • Cisco Nexus 5596UP Switch
  • Cisco Nexus 5548P Switch
  • Cisco Nexus 6004 Switch
  • Cisco Nexus 6001 Switch
  • Cisco Nexus 5548UP Switch
  • Cisco Nexus 5596T Switch

Known Affected Releases

6.0(2)N2(2)

Description (partial)

Symptom:
CORE1-ATT_Storage# show lac counters 
                    LACPDUs         Marker      Marker Response    LACPDUs
Port              Sent   Recv     Sent   Recv     Sent   Recv      Pkts Err
---------------------------------------------------------------------
port-channel100
Ethernet1/9        40723  40715    0      0        0      0        0      

port-channel200
Ethernet1/13       40383  40374    0      0        0      0        0      
Ethernet1/17       40404  40379    0      0        0      0        0      

port-channel300
Ethernet1/21       486    178      0      0        0      0        0      
Ethernet1/25       361    0        0      0        0      0        0      
Ethernet1/29       439    131      0      0        0      0        0      
Ethernet1/33       439    140      0      0        0      0        0




2013 Nov  8 11:30:24 EOR-LEAF2 %ETHPORT-5-IF_ADMIN_UP: Interface port-channel250 is admin up .
2013 Nov  8 11:30:24 EOR-LEAF2 %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port-channel250 is down (No operational members)
2013 Nov  8 11:30:29 EOR-LEAF2 %ETHPORT-5-SPEED: Interface Ethernet1/3/1, operational speed changed to 10 Gbps
2013 Nov  8 11:30:29 EOR-LEAF2 %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/3/1, operational duplex mode changed to Full
2013 Nov  8 11:30:29 EOR-LEAF2 %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/3/1, operational Receive Flow Control state changed to off
2013 Nov  8 11:30:29 EOR-LEAF2 %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet1/3/1, operational Transmit Flow Control state changed to off
(((same message)))
2013 Nov  8 11:30:41 EOR-LEAF2 %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface port-channel250, operational Receive Flow Control state changed to off
2013 Nov  8 11:30:41 EOR-LEAF2 %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface port-channel250, operational Transmit Flow Control state changed to off
2013 Nov  8 11:30:43 EOR-LEAF2 %ETH_PORT_CHANNEL-4-PORT_INDIVIDUAL: port Ethernet1/3/4 is operationally individual
2013 Nov  8 11:30:43 EOR-LEAF2 %ETHPORT-5-IF_UP: Interface Ethernet1/3/4 is up in mode trunk
2013 Nov  8 11:30:54 EOR-LEAF2 %ETH_PORT_CHANNEL-5-PORT_SUSPENDED: Ethernet1/3/1: Ethernet1/3/1 is suspended
2013 Nov  8 11:30:56 EOR-LEAF2 %ETH_PORT_CHANNEL-5-PORT_SUSPENDED: Ethernet1/3/2: Ethernet1/3/2 is suspended
2013 Nov  8 11:30:57 EOR-LEAF2 %ETH_PORT_CHANNEL-5-PORT_SUSPENDED: Ethernet1/3/3: Ethernet1/3/3 is suspended
2013 Nov  8 11:31:02 EOR-LEAF2 %ETH_PORT_CHANNEL-5-PORT_SUSPENDED: Ethernet2/3/1: Ethernet2/3/1 is suspended
2013 Nov  8 11:31:05 EOR-LEAF2 %ETH_PORT_CHANNEL-5-PORT_SUSPENDED: Ethernet2/3/2: Ethernet2/3/2 is suspended
2013 Nov  8 11:31:05 EOR-LEAF2 %ETH_PORT_CHANNEL-5-PORT_SUSPENDED: Ethernet2/3/3: Ethernet2/3/3 is suspended
2013 Nov  8 11:31:06 EOR-LEAF2 %ETH_PORT_CHANNEL-5-PORT_SUSPENDED: Ethernet2/3/4: Ethernet2/3/4 is suspended


2013 Nov  8 01:45:59 EOR-LEAF2 %ETH_PORT_CHANNEL-5-PORT_UP: port-channel100: Ethernet1/1/4 is up
2013 Nov  8 01:45:59 EOR-LEAF2 %ETHPORT-5-IF_UP: Interface Ethernet1/1/4 is up in mode Fex Fabric
2013 Nov  8 01:46:03 EOR-LEAF2 %SYSMGR-FEX101-5-HEARTBEAT_LOSS: Service "satctrl" heartbeat loss 2 ,max 7 .
2013 Nov  8 01:46:18 EOR-LEAF2 %FEX-2-FEX_OFFLINE: FEX 100 has gone OFFLINE

Conditions:
Port Channel
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.