Guest

Preview Tool

Cisco Bug: CSCsz31035 - C2W2B: Peer keeps CTS link in OPEN state,when PO members cfg to default

Last Modified

Feb 15, 2017

Products (1)

  • Cisco IOS

Known Affected Releases

12.2(32.8.11)SX266

Description (partial)

Symptom:

Removing "cts dot1x" config from one of the members of a port channel fails to notify the peer that the member is gone.   This leaves the peer's CTS interface to remain OPEN even after "cts dot1x" has been removed on the other end.

Conditions:

1) Configure at least 2 CTS links using channel-group.

Example:  interface Gi3/3, Gi3/4

interface GigabitEthernet3/3
 no ip address
 cts dot1x 
 channel-group 201 mode active
end

interface GigabitEthernet3/4
 no ip address
 cts dot1x 
 channel-group 201 mode active
end

2) Bring up the CTS links to OPEN state

3) show etherchannel summary
Flags:  D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      N - not in use, no aggregation
        f - failed to allocate aggregator

        M - not in use, no aggregation due to minimum links not met
        m - not in use, port not aggregated due to minimum links not met
        u - unsuitable for bundling
        d - default port

        w - waiting to be aggregated
Number of channel-groups in use: 7
Number of aggregators:           7

Group  Port-channel  Protocol    Ports
------+-------------+-----------+-----------------------------------------------
99     Po99(RD)         -
201    Po201(RU)       LACP      Gi3/3(P)      Gi3/4(P)
202    Po202(SD)        -
203    Po203(RD)        -
205    Po205(RD)        -
206    Po206(SD)        -
215    Po215(RD)        -

4) Now unconfigure "cts dot1x" on int Gi3/4
Note that the CTS link on the local box goes to disconnect state
Note that the corresponding CTS interface on the peer is still in OPEN state

6) Now remove "cts dot1x" on the last member of the port channel Gi3/3
Note that the CTS link on the local box goes to disconnect state
Note that the corresponding CTS interface on the peer also goes to disconnect state
However, the corresponding CTS interfaces for the previous members Gi3/4 on the peer is still in OPEN state
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.