VLAN trunk interface goes down after seconds

[seb1303]

Hello,

I currently try to get a couple of Cisco Catalyst 9500 switches running.

I would like to connect two StackWise Virtual stacks via VLAN trunking to each other.
See this basic image of the network:

After enabling one side get the VLAN trunk inferface up my whole network is not working for a few seconds until the link of the VLAN trunk interface goes down again. But the only thing I can see (on both StackWise switches) in logging is:

Jan 21 11:19:56.755: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to down

Where can I dig deeper to get a more meaningful information? 

The interface state is simply down. No errdisabled or something like that...

[seb1303]

"Show lacp port-channel x" is not working... I do only have this options:

show lacp 1 ?
  counters  Traffic information
  internal  Internal information
  neighbor  Neighbor information

Where 1 is the port-channel number. 

[MHM Cisco World]

show lacp internal 
MHM

[seb1303]

# SVL#1
# show lacp 1 internal
Flags:  S - Device is requesting Slow LACPDUs
        F - Device is requesting Fast LACPDUs
        A - Device is in Active mode       P - Device is in Passive mode

Channel group 1
                                LACP port    Admin     Oper    Port        Port
Port          Flags   State     Priority     Key       Key     Number      State
Hu1/0/28      FA      down      32768        0x1       0x1     0x31D       0xF
Hu2/0/28      FA      down      32768        0x1       0x1     0x51D       0xF

# SVL#2
# show lacp 1 internal
Flags:  S - Device is requesting Slow LACPDUs
        F - Device is requesting Fast LACPDUs
        A - Device is in Active mode       P - Device is in Passive mode

Channel group 1
                                LACP port    Admin     Oper    Port        Port
Port          Flags   State     Priority     Key       Key     Number      State
Hu1/0/28      FA      down      32768        0x1       0x1     0x31D       0xF
Hu2/0/28      FA      down      32768        0x1       0x1     0x51D       0xF

I also got some logging output via syslog. These are the loglines when activating the port-channel:

# SVL#1
Jan 27 18:04:08 svl1 25342: svl1: 12w6d: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to up
Jan 27 18:04:08 svl1 25343: svl1: 12w6d: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to up
Jan 27 18:04:10 svl1 25344: svl1: .Jan 27 18:04:10.187: RSTP(1): initializing port Po1
Jan 27 18:04:10 svl1 25345: svl1: .Jan 27 18:04:10.187: RSTP(1): Po1 is now designated
Jan 27 18:04:10 svl1 25346: svl1: .Jan 27 18:04:10.187: RSTP(2): initializing port Po1
Jan 27 18:04:10 svl1 25347: svl1: .Jan 27 18:04:10.187: RSTP(2): Po1 is now designated
Jan 27 18:04:10 svl1 25348: svl1: .Jan 27 18:04:10.187: RSTP(10): initializing port Po1
Jan 27 18:04:10 svl1 25349: svl1: .Jan 27 18:04:10.187: RSTP(10): Po1 is now designated
Jan 27 18:04:10 svl1 25350: svl1: .Jan 27 18:04:10.187: RSTP(20): initializing port Po1
Jan 27 18:04:10 svl1 25351: svl1: .Jan 27 18:04:10.187: RSTP(20): Po1 is now designated
Jan 27 18:04:10 svl1 25352: svl1: .Jan 27 18:04:10.187: RSTP(21): initializing port Po1
Jan 27 18:04:10 svl1 25353: svl1: .Jan 27 18:04:10.187: RSTP(21): Po1 is now designated
Jan 27 18:04:10 svl1 25354: svl1: .Jan 27 18:04:10.188: RSTP(22): initializing port Po1
Jan 27 18:04:10 svl1 25355: svl1: .Jan 27 18:04:10.188: RSTP(22): Po1 is now designated
Jan 27 18:04:10 svl1 25356: svl1: .Jan 27 18:04:10.188: RSTP(23): initializing port Po1
...
Jan 27 18:04:40 svl1 33371: svl1: 12w6d: %LINEPROTO-5-UPDOWN: Line protocol on Interface HundredGigE2/0/28, changed state to down
Jan 27 18:04:40 svl1 33372: svl1: .Jan 27 18:04:40.215: RSTP(1): Twe1/0/5 fdwhile Expired
Jan 27 18:04:40 svl1 33373: svl1: .Jan 27 18:04:40.215: RSTP(1): Twe1/0/7 fdwhile Expired
Jan 27 18:04:40 svl1 33374: svl1: .Jan 27 18:04:40.215: RSTP(1): Twe2/0/5 fdwhile Expired
Jan 27 18:04:40 svl1 33375: svl1: .Jan 27 18:04:40.215: RSTP(1): Twe2/0/7 fdwhile Expired
Jan 27 18:04:40 svl1 33376: svl1: .Jan 27 18:04:40.215: RSTP(1): Po2 fdwhile Expired
Jan 27 18:04:40 svl1 33377: svl1: .Jan 27 18:04:40.215: RSTP(1): Po3 fdwhile Expired
Jan 27 18:04:40 svl1 33378: svl1: .Jan 27 18:04:40.215: RSTP(2): Twe1/0/5 fdwhile Expired
Jan 27 18:04:40 svl1 33379: svl1: .Jan 27 18:04:40.215: RSTP(2): Twe1/0/7 fdwhile Expired
Jan 27 18:04:40 svl1 33380: svl1: .Jan 27 18:04:40.215: RSTP(2): Twe2/0/5 fdwhile Expired
Jan 27 18:04:40 svl1 33381: svl1: .Jan 27 18:04:40.215: RSTP(2): Twe2/0/7 fdwhile Expired
Jan 27 18:04:40 svl1 33382: svl1: .Jan 27 18:04:40.215: RSTP(2): Po2 fdwhile Expired
Jan 27 18:04:40 svl1 33383: svl1: .Jan 27 18:04:40.215: RSTP(2): Po3 fdwhile Expired
Jan 27 18:04:40 svl1 33384: svl1: .Jan 27 18:04:40.215: RSTP(10): Twe1/0/5 fdwhile Expired
...
Jan 27 18:04:41 svl1 33704: svl1: 12w6d: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to down
Jan 27 18:04:45 svl1 33705: svl1: .Jan 27 18:04:45.261: RSTP(1): stopping topology change timer
Jan 27 18:04:45 svl1 33706: svl1: .Jan 27 18:04:45.261: RSTP(2): stopping topology change timer
Jan 27 18:04:45 svl1 33707: svl1: .Jan 27 18:04:45.261: RSTP(10): stopping topology change timer
Jan 27 18:04:45 svl1 33708: svl1: .Jan 27 18:04:45.261: RSTP(20): stopping topology change timer
Jan 27 18:04:45 svl1 33709: svl1: .Jan 27 18:04:45.261: RSTP(21): stopping topology change timer
Jan 27 18:04:45 svl1 33710: svl1: .Jan 27 18:04:45.261: RSTP(22): stopping topology change timer
...
Jan 27 18:04:51 svl1 33760: svl1: .Jan 27 18:04:51.625: RSTP(1): updt roles, non-tracked event
Jan 27 18:04:51 svl1 33761: svl1: .Jan 27 18:04:51.625: RSTP(2): updt roles, non-tracked event
Jan 27 18:04:51 svl1 33762: svl1: .Jan 27 18:04:51.626: RSTP(10): updt roles, non-tracked event
Jan 27 18:04:51 svl1 33763: svl1: .Jan 27 18:04:51.626: RSTP(20): updt roles, non-tracked event
Jan 27 18:04:51 svl1 33764: svl1: .Jan 27 18:04:51.626: RSTP(21): updt roles, non-tracked event
Jan 27 18:04:51 svl1 33765: svl1: .Jan 27 18:04:51.626: RSTP(22): updt roles, non-tracked event
Jan 27 18:04:51 svl1 33766: svl1: .Jan 27 18:04:51.626: RSTP(23): updt roles, non-tracked event
...
Jan 27 18:04:51 svl1 33815: svl1: .Jan 27 18:04:51.632: RSTP(1): updt roles, root port Po1 going down
Jan 27 18:04:51 svl1 33816: svl1: .Jan 27 18:04:51.632: RSTP(1): we become the root bridge
Jan 27 18:04:51 svl1 33817: svl1: .Jan 27 18:04:51.632: RSTP(1): Po1 not in sync
Jan 27 18:04:51 svl1 33818: svl1: .Jan 27 18:04:51.632: RSTP(2): updt roles, root port Po1 going down
Jan 27 18:04:51 svl1 33819: svl1: .Jan 27 18:04:51.632: RSTP(2): we become the root bridge
Jan 27 18:04:51 svl1 33820: svl1: .Jan 27 18:04:51.632: RSTP(2): Po1 not in sync
Jan 27 18:04:51 svl1 33821: svl1: .Jan 27 18:04:51.632: RSTP(10): updt roles, root port Po1 going down
Jan 27 18:04:51 svl1 33822: svl1: .Jan 27 18:04:51.632: RSTP(10): we become the root bridge
Jan 27 18:04:51 svl1 33823: svl1: .Jan 27 18:04:51.632: RSTP(10): Po1 not in sync
Jan 27 18:04:51 svl1 33824: svl1: .Jan 27 18:04:51.632: RSTP(20): updt roles, root port Po1 going down
...
Jan 27 18:04:53 svl1 33980: svl1: 12w6d: %LINEPROTO-5-UPDOWN: Line protocol on Interface HundredGigE1/0/28, changed state to down
Jan 27 18:04:53 svl1 33981: svl1: 12w6d: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to down
Jan 27 18:04:54 svl1 33982: svl1: 12w6d: %LINK-3-UPDOWN: Interface Port-channel1, changed state to down
Jan 27 18:04:54 svl1 33983: svl1: 12w6d: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to down
Jan 27 18:04:58 svl1 33984: svl1: 12w6d: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to up
Jan 27 18:05:01 svl1 33985: svl1: .Jan 27 18:05:01.285: RSTP(1): initializing port Po1
Jan 27 18:05:01 svl1 33986: svl1: .Jan 27 18:05:01.285: RSTP(1): Po1 is now designated
Jan 27 18:05:01 svl1 33987: svl1: .Jan 27 18:05:01.285: RSTP(2): initializing port Po1
Jan 27 18:05:01 svl1 33988: svl1: .Jan 27 18:05:01.285: RSTP(2): Po1 is now designated
Jan 27 18:05:01 svl1 33989: svl1: .Jan 27 18:05:01.285: RSTP(10): initializing port Po1
Jan 27 18:05:01 svl1 33990: svl1: .Jan 27 18:05:01.285: RSTP(10): Po1 is now designated
...
Jan 27 18:05:01 svl1 34095: svl1: .Jan 27 18:05:01.297: RSTP(1): transmitting a proposal on Po1
Jan 27 18:05:01 svl1 34096: svl1: .Jan 27 18:05:01.298: RSTP(2): transmitting a proposal on Po1
Jan 27 18:05:01 svl1 34097: svl1: .Jan 27 18:05:01.298: RSTP(10): transmitting a proposal on Po1
Jan 27 18:05:01 svl1 34098: svl1: .Jan 27 18:05:01.298: RSTP(20): transmitting a proposal on Po1
Jan 27 18:05:01 svl1 34099: svl1: .Jan 27 18:05:01.298: RSTP(21): transmitting a proposal on Po1
Jan 27 18:05:01 svl1 34100: svl1: .Jan 27 18:05:01.298: RSTP(22): transmitting a proposal on Po1

# SVL#2
Jan 27 18:04:07 svl2 389: svl2: *Jan 27 18:02:10.197: %LINK-3-UPDOWN: Interface Port-channel1, changed state to down
Jan 27 18:04:07 svl2 390: svl2: *Jan 27 18:02:10.197: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to up
Jan 27 18:04:07 svl2 391: svl2: *Jan 27 18:02:10.199: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to up
Jan 27 18:04:10 svl2 392: svl2: *Jan 27 18:02:14.213: setting bridge id (which=3) prio 32769 prio cfg 32768 sysid 1 (on) id 8001.3c8b.7f57.30e0
Jan 27 18:04:10 svl2 393: svl2: *Jan 27 18:02:14.213: RSTP(1): initializing port Po1
Jan 27 18:04:10 svl2 394: svl2: *Jan 27 18:02:14.213: RSTP(1): Po1 is now designated
Jan 27 18:04:10 svl2 395: svl2: *Jan 27 18:02:14.213: setting bridge id (which=3) prio 32770 prio cfg 32768 sysid 2 (on) id 8002.3c8b.7f57.30e0
Jan 27 18:04:10 svl2 396: svl2: *Jan 27 18:02:14.213: RSTP(2): initializing port Po1
Jan 27 18:04:10 svl2 397: svl2: *Jan 27 18:02:14.213: RSTP(2): Po1 is now designated
Jan 27 18:04:10 svl2 398: svl2: *Jan 27 18:02:14.213: setting bridge id (which=3) prio 32778 prio cfg 32768 sysid 10 (on) id 800A.3c8b.7f57.30e0
Jan 27 18:04:10 svl2 399: svl2: *Jan 27 18:02:14.213: RSTP(10): initializing port Po1
Jan 27 18:04:10 svl2 400: svl2: *Jan 27 18:02:14.213: RSTP(10): Po1 is now designated
Jan 27 18:04:10 svl2 401: svl2: *Jan 27 18:02:14.213: setting bridge id (which=3) prio 32788 prio cfg 32768 sysid 20 (on) id 8014.3c8b.7f57.30e0
Jan 27 18:04:10 svl2 402: svl2: *Jan 27 18:02:14.213: RSTP(20): initializing port Po1
Jan 27 18:04:10 svl2 403: svl2: *Jan 27 18:02:14.213: RSTP(20): Po1 is now designated
Jan 27 18:04:10 svl2 404: svl2: *Jan 27 18:02:14.213: setting bridge id (which=3) prio 32789 prio cfg 32768 sysid 21 (on) id 8015.3c8b.7f57.30e0
Jan 27 18:04:10 svl2 405: svl2: *Jan 27 18:02:14.213: RSTP(21): initializing port Po1
Jan 27 18:04:10 svl2 406: svl2: *Jan 27 18:02:14.214: RSTP(21): Po1 is now designated
Jan 27 18:04:10 svl2 407: svl2: *Jan 27 18:02:14.214: setting bridge id (which=3) prio 32790 prio cfg 32768 sysid 22 (on) id 8016.3c8b.7f57.30e0
Jan 27 18:04:10 svl2 408: svl2: *Jan 27 18:02:14.214: RSTP(22): initializing port Po1
Jan 27 18:04:10 svl2 409: svl2: *Jan 27 18:02:14.214: RSTP(22): Po1 is now designated
Jan 27 18:04:10 svl2 410: svl2: *Jan 27 18:02:14.214: setting bridge id (which=3) prio 32791 prio cfg 32768 sysid 23 (on) id 8017.3c8b.7f57.30e0
Jan 27 18:04:10 svl2 411: svl2: *Jan 27 18:02:14.214: RSTP(23): initializing port Po1
Jan 27 18:04:10 svl2 412: svl2: *Jan 27 18:02:14.214: RSTP(23): Po1 is now designated
Jan 27 18:04:10 svl2 413: svl2: *Jan 27 18:02:14.214: setting bridge id (which=3) prio 32794 prio cfg 32768 sysid 26 (on) id 801A.3c8b.7f57.30e0
...
Jan 27 18:04:10 svl2 557: svl2: *Jan 27 18:02:14.237: RSTP(1): transmitting a proposal on Po1
Jan 27 18:04:10 svl2 558: svl2: *Jan 27 18:02:14.237: RSTP(2): transmitting a proposal on Po1
Jan 27 18:04:10 svl2 559: svl2: *Jan 27 18:02:14.237: RSTP(10): transmitting a proposal on Po1
Jan 27 18:04:10 svl2 560: svl2: *Jan 27 18:02:14.237: RSTP(20): transmitting a proposal on Po1
Jan 27 18:04:10 svl2 561: svl2: *Jan 27 18:02:14.237: RSTP(21): transmitting a proposal on Po1
Jan 27 18:04:10 svl2 562: svl2: *Jan 27 18:02:14.237: RSTP(22): transmitting a proposal on Po1
Jan 27 18:04:10 svl2 563: svl2: *Jan 27 18:02:14.237: RSTP(23): transmitting a proposal on Po1
Jan 27 18:04:10 svl2 564: svl2: *Jan 27 18:02:14.237: RSTP(26): transmitting a proposal on Po1
Jan 27 18:04:10 svl2 565: svl2: *Jan 27 18:02:14.237: RSTP(30): transmitting a proposal on Po1
Jan 27 18:04:10 svl2 566: svl2: *Jan 27 18:02:14.237: RSTP(40): transmitting a proposal on Po1
...
Jan 27 18:04:40 svl2 840: svl2: *Jan 27 18:02:43.408: %LINEPROTO-5-UPDOWN: Line protocol on Interface HundredGigE1/0/28, changed state to down
Jan 27 18:04:42 svl2 841: svl2: *Jan 27 18:02:45.364: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to down
Jan 27 18:04:45 svl2 842: svl2: *Jan 27 18:02:49.332: RSTP(1): stopping topology change timer
Jan 27 18:04:45 svl2 843: svl2: *Jan 27 18:02:49.334: RSTP(2): stopping topology change timer
Jan 27 18:04:45 svl2 844: svl2: *Jan 27 18:02:49.334: RSTP(10): stopping topology change timer
Jan 27 18:04:45 svl2 845: svl2: *Jan 27 18:02:49.334: RSTP(20): stopping topology change timer
Jan 27 18:04:45 svl2 846: svl2: *Jan 27 18:02:49.335: RSTP(21): stopping topology change timer
Jan 27 18:04:45 svl2 847: svl2: *Jan 27 18:02:49.336: RSTP(22): stopping topology change timer
...
Jan 27 18:04:53 svl2 952: svl2: *Jan 27 18:02:56.658: %LINEPROTO-5-UPDOWN: Line protocol on Interface HundredGigE2/0/28, changed state to down
Jan 27 18:04:53 svl2 953: svl2: *Jan 27 18:02:56.665: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to down
Jan 27 18:04:54 svl2 954: svl2: *Jan 27 18:02:57.670: %LINK-3-UPDOWN: Interface Port-channel1, changed state to down
Jan 27 18:04:54 svl2 955: svl2: *Jan 27 18:02:57.672: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to down
Jan 27 18:04:58 svl2 956: svl2: *Jan 27 18:03:01.365: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to up
Jan 27 18:05:01 svl2 957: svl2: *Jan 27 18:03:05.311: setting bridge id (which=3) prio 32769 prio cfg 32768 sysid 1 (on) id 8001.3c8b.7f57.30e0
Jan 27 18:05:01 svl2 958: svl2: *Jan 27 18:03:05.311: RSTP(1): initializing port Po1
Jan 27 18:05:01 svl2 959: svl2: *Jan 27 18:03:05.311: RSTP(1): Po1 is now designated
Jan 27 18:05:01 svl2 960: svl2: *Jan 27 18:03:05.311: setting bridge id (which=3) prio 32770 prio cfg 32768 sysid 2 (on) id 8002.3c8b.7f57.30e0
Jan 27 18:05:01 svl2 961: svl2: *Jan 27 18:03:05.311: RSTP(2): initializing port Po1
Jan 27 18:05:01 svl2 962: svl2: *Jan 27 18:03:05.311: RSTP(2): Po1 is now designated
Jan 27 18:05:01 svl2 963: svl2: *Jan 27 18:03:05.311: setting bridge id (which=3) prio 32778 prio cfg 32768 sysid 10 (on) id 800A.3c8b.7f57.30e0
Jan 27 18:05:01 svl2 964: svl2: *Jan 27 18:03:05.311: RSTP(10): initializing port Po1
Jan 27 18:05:01 svl2 965: svl2: *Jan 27 18:03:05.311: RSTP(10): Po1 is now designated
Jan 27 18:05:01 svl2 966: svl2: *Jan 27 18:03:05.311: setting bridge id (which=3) prio 32788 prio cfg 32768 sysid 20 (on) id 8014.3c8b.7f57.30e0
Jan 27 18:05:01 svl2 967: svl2: *Jan 27 18:03:05.311: RSTP(20): initializing port Po1
Jan 27 18:05:01 svl2 968: svl2: *Jan 27 18:03:05.311: RSTP(20): Po1 is now designated
Jan 27 18:05:01 svl2 969: svl2: *Jan 27 18:03:05.311: setting bridge id (which=3) prio 32789 prio cfg 32768 sysid 21 (on) id 8015.3c8b.7f57.30e0
Jan 27 18:05:01 svl2 970: svl2: *Jan 27 18:03:05.311: RSTP(21): initializing port Po1
...
Jan 27 18:05:01 svl2 1123: svl2: *Jan 27 18:03:05.328: RSTP(2): transmitting a proposal on Po1
Jan 27 18:05:01 svl2 1124: svl2: *Jan 27 18:03:05.328: RSTP(10): transmitting a proposal on Po1
Jan 27 18:05:01 svl2 1125: svl2: *Jan 27 18:03:05.328: RSTP(20): transmitting a proposal on Po1
Jan 27 18:05:01 svl2 1126: svl2: *Jan 27 18:03:05.328: RSTP(21): transmitting a proposal on Po1
Jan 27 18:05:01 svl2 1127: svl2: *Jan 27 18:03:05.328: RSTP(22): transmitting a proposal on Po1
Jan 27 18:05:01 svl2 1128: svl2: *Jan 27 18:03:05.328: RSTP(23): transmitting a proposal on Po1
...
Jan 27 18:05:52 svl2 1566: svl2: *Jan 27 18:03:55.584: %LINEPROTO-5-UPDOWN: Line protocol on Interface HundredGigE2/0/28, changed state to down
Jan 27 18:05:52 svl2 1567: svl2: *Jan 27 18:03:55.590: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to down
Jan 27 18:05:53 svl2 1568: svl2: *Jan 27 18:03:56.596: %LINK-3-UPDOWN: Interface Port-channel1, changed state to down
Jan 27 18:05:53 svl2 1569: svl2: *Jan 27 18:03:56.597: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to down
Jan 27 18:06:05 svl2 1570: svl2: *Jan 27 18:04:08.333: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to up
Jan 27 18:06:07 svl2 1571: svl2: *Jan 27 18:04:10.508: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to down

[MHM Cisco World]

show lacp neighbor (since you make PO up)
only show this copy it and then shut the PO 
thanks a lot 
MHM

[seb1303]

# SVL#1
# show lacp 1 neighbor
Flags:  S - Device is requesting Slow LACPDUs
        F - Device is requesting Fast LACPDUs
        A - Device is in Active mode       P - Device is in Passive mode

Channel group 1 neighbors

                     LACP port                      Admin  Oper   Port    Port
Port          Flags  Priority  Dev ID          Age  key    Key    Number  State
Hu1/0/28      SP     32768     3c8b.7f57.30e0 1688s  0x0    0x1    0x51D   0x0
Hu2/0/28      SA     32768     3c8b.7f57.30e0  17s  0x0    0x1    0x31D   0x3D

# SVL#2
# show lacp 1 neighbor
Flags:  S - Device is requesting Slow LACPDUs
        F - Device is requesting Fast LACPDUs
        A - Device is in Active mode       P - Device is in Passive mode

Channel group 1 neighbors

                     LACP port                      Admin  Oper   Port    Port
Port          Flags  Priority  Dev ID          Age  key    Key    Number  State
Hu1/0/28      SA     32768     3c8b.7f57.b2e0  16s  0x0    0x1    0x51D   0x3D
Hu2/0/28      SP     32768     3c8b.7f57.b2e0 1687s  0x0    0x1    0x31D   0x34

[MHM Cisco World]

port flags is SP ans other is SA 
and one port Hu1/0/28 which meaning it not connect at all 
can you check cabling and config for each port member of PO
note:- mac address is successful change
thanks 
MHM

[MHM Cisco World]

0x3d is 00111101 then flip it 

10111100 

0x34 is 00110100 flip it

00101100

The First bit is if port config as active or passive' one is config as active and other is config as passive 

Forth bit is sync' the 1 in sync and 0 not in sync 

So did you check if you  cabling correct port or not?

MHM

[balaji.bandi]

After changing the domain - did you reload the SVL switches ?

May be there are many conversation happened  - missed some of them - where do we stand now ? 

[seb1303]

Yes I reloaded the stack on which I changed the domain... Do I need to reload the other one too?

[balaji.bandi]

One should good enough to reload - resolve the differences.

So for now SVL1 to SVL2 still have issue and the trunk go down no reason  right ?

what is the IOS XE code running on both :

show version 

show stackwise-virtual

you are using 100GB ports to connect each other - they are in same Place - they go via any patch panel or different comms room via ?

what mode of cable you using  to connect each other ?

[seb1303]

Yes, you are right.

But after changing the root bridge to be SVL#1 via spanning-tree vlan 1-4093 root command. The network itself (besides SVL#2) seems to be stable and without interruption. But the trunk still doesn't come up...

Version on both is Cisco IOS XE Software, Version 17.03.05

show stackwise-virtual output:

# SVL#1
# show stackwise-virtual
Stackwise Virtual Configuration:
--------------------------------
Stackwise Virtual : Enabled
Domain Number : 1

Switch  Stackwise Virtual Link  Ports
------  ----------------------  ------
1       1                       HundredGigE1/0/25
                                HundredGigE1/0/26
2       1                       HundredGigE2/0/25
                                HundredGigE2/0/26

# SVL#2
# show stackwise-virtual
Stackwise Virtual Configuration:
--------------------------------
Stackwise Virtual : Enabled
Domain Number : 2

Switch  Stackwise Virtual Link  Ports
------  ----------------------  ------
1       1                       HundredGigE1/0/25
                                HundredGigE1/0/26
2       1                       HundredGigE2/0/25
                                HundredGigE2/0/26

[balaji.bandi]

 But the trunk still doesn't come up...

Port-channel not coming up between SVL1 and SVL2 - i take this as right now situation ?

You not mentioned that what cable type you are using ?

For testing -

Create a one test VLAN which not at all in the production (or not used at all  on both SVL switches)

Allow only that VLAN as Native VLAN and Allowed VLAN in the list and let us know is the Link up and stable ?

[seb1303]

Yes this is the current situation.

I am using cables with these specifications: 50/125µm OM3 with SC/LC connectors
The cables are going from the SVLs directly to a patchpannel (SC connectors) which interconnects two rooms. 

I just tested it with one VLAN which only exists on these two SVLs. Configured it as trunk and native VLAN but got the same problems. The port-channel is not coming up.

[balaji.bandi]

I am using cables with these specifications: 50/125µm OM3 with SC/LC connectors
The cables are going from the SVLs directly to a patchpannel (SC connectors) which interconnects two rooms. 

what is the distance of these ?

I just tested it with one VLAN which only exists on these two SVLs. Configured it as trunk and native VLAN but got the same problems. The port-channel is not coming up.

Can you share the configuration and what Logs you see on both the devices ?

I do remember one of the post you mentioned the Port-channel come and go down after sometime ?  Is this Interface come up and go down - or all the time down / down ?

Have you Tried single port as Layer 2 p2p - to confirm is the Fiber working ?

Have you tried crossing RX - TX patch leads ?

Do you see the Light on the Fibre and port ?

Have you tried Looping the Fibre  ?

[seb1303]

I need to measure the complete cable length. I am currently not on site. Will add this informationen...

The interfaces come up. See logs for more details.

Tried it without port-channel, only point to point between two interfaces. Doesn't work...

This is the configuration:

# SVL#1
# show running-config interface port-channel 1
interface Port-channel1
 switchport trunk native vlan 3
 switchport trunk allowed vlan 3
 switchport mode trunk
end

# show running-config interface hundredGigE 1/0/28
interface HundredGigE1/0/28
 switchport trunk native vlan 3
 switchport trunk allowed vlan 3
 switchport mode trunk
 channel-group 1 mode active
end

# show running-config interface hundredGigE 2/0/28
interface HundredGigE2/0/28
 switchport trunk native vlan 3
 switchport trunk allowed vlan 3
 switchport mode trunk
 channel-group 1 mode active
end

# SVL#2
# show running-config interface port-channel 1
interface Port-channel1
 switchport trunk native vlan 3
 switchport trunk allowed vlan 3
 switchport mode trunk
end

# show running-config interface hundredGigE 1/0/28
interface HundredGigE1/0/28
 switchport trunk native vlan 3
 switchport trunk allowed vlan 3
 switchport mode trunk
 channel-group 1 mode active
end

# show running-config interface hundredGigE 2/0/28
interface HundredGigE2/0/28
 switchport trunk native vlan 3
 switchport trunk allowed vlan 3
 switchport mode trunk
 channel-group 1 mode active
end

Here are the logfiles:

# SVL#1
Jan 28 18:30:31 svl1 45388: svl1: 13w0d: %LINK-3-UPDOWN: Interface Port-channel1, changed state to down
Jan 28 18:30:31 svl1 45389: svl1: 13w0d: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to down
Jan 28 18:30:31 svl1 45390: svl1: 13w0d: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to down
Jan 28 18:30:35 svl1 45391: svl1: 13w0d: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to up
Jan 28 18:30:38 svl1 45392: svl1: 13w0d: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to up
Jan 28 18:30:40 svl1 45393: svl1: 13w0d: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to down
Jan 28 18:30:40 svl1 45394: svl1: 13w0d: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to down
Jan 28 18:30:46 svl1 45395: svl1: 13w0d: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to up
Jan 28 18:30:52 svl1 45396: svl1: .Jan 28 18:30:51.516: RSTP(3): initializing port Po1
Jan 28 18:30:52 svl1 45397: svl1: .Jan 28 18:30:51.516: RSTP(3): Po1 is now designated
Jan 28 18:30:52 svl1 45398: svl1: .Jan 28 18:30:51.518: RSTP(3): transmitting a proposal on Po1
Jan 28 18:30:58 svl1 45399: svl1: 13w0d: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to down
Jan 28 18:31:01 svl1 45400: svl1: 13w0d: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to up
Jan 28 18:31:05 svl1 45401: svl1: .Jan 28 18:31:04.360: RSTP(3): initializing port Po1
Jan 28 18:31:05 svl1 45402: svl1: .Jan 28 18:31:04.360: RSTP(3): Po1 is now designated
Jan 28 18:31:05 svl1 45403: svl1: .Jan 28 18:31:04.362: RSTP(3): transmitting a proposal on Po1
Jan 28 18:31:05 svl1 45404: svl1: 13w0d: %LINEPROTO-5-UPDOWN: Line protocol on Interface HundredGigE2/0/28, changed state to up
Jan 28 18:31:06 svl1 45405: svl1: .Jan 28 18:31:05.506: RSTP(3): transmitting a proposal on Po1
Jan 28 18:31:06 svl1 45406: svl1: .Jan 28 18:31:05.508: RSTP(3): received an agreement on Po1
Jan 28 18:31:06 svl1 45407: svl1: .Jan 28 18:31:05.508: RSTP(3): starting topology change timer for 35 seconds
Jan 28 18:31:06 svl1 45408: svl1: .Jan 28 18:31:05.508: RSTP(3): starting topology change timer for 35 seconds
Jan 28 18:31:06 svl1 45409: svl1: .Jan 28 18:31:05.508: STP[3]: Generating TC trap for port Port-channel1
Jan 28 18:31:07 svl1 45410: svl1: 13w0d: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
Jan 28 18:31:07 svl1 45411: svl1: 13w0d: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up
Jan 28 18:31:35 svl1 45412: svl1: 13w0d: %LINEPROTO-5-UPDOWN: Line protocol on Interface HundredGigE2/0/28, changed state to down
Jan 28 18:31:35 svl1 45413: svl1: 13w0d: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to down
Jan 28 18:31:36 svl1 45414: svl1: 13w0d: %LINK-3-UPDOWN: Interface Port-channel1, changed state to down
Jan 28 18:31:36 svl1 45415: svl1: 13w0d: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to down
Jan 28 18:31:41 svl1 45416: svl1: .Jan 28 18:31:40.508: RSTP(3): stopping topology change timer
Jan 28 18:32:47 svl1 45417: svl1: 13w0d: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to up
Jan 28 18:32:50 svl1 45418: svl1: .Jan 28 18:32:49.824: RSTP(3): initializing port Po1
Jan 28 18:32:50 svl1 45419: svl1: .Jan 28 18:32:49.824: RSTP(3): Po1 is now designated
Jan 28 18:32:50 svl1 45420: svl1: .Jan 28 18:32:49.826: RSTP(3): transmitting a proposal on Po1
Jan 28 18:32:51 svl1 45421: svl1: 13w0d: %LINEPROTO-5-UPDOWN: Line protocol on Interface HundredGigE2/0/28, changed state to up
Jan 28 18:32:51 svl1 45422: svl1: .Jan 28 18:32:51.518: RSTP(3): transmitting a proposal on Po1
Jan 28 18:32:51 svl1 45423: svl1: .Jan 28 18:32:51.520: RSTP(3): received an agreement on Po1
Jan 28 18:32:51 svl1 45424: svl1: .Jan 28 18:32:51.521: RSTP(3): starting topology change timer for 35 seconds
Jan 28 18:32:51 svl1 45425: svl1: .Jan 28 18:32:51.521: RSTP(3): starting topology change timer for 35 seconds
Jan 28 18:32:51 svl1 45426: svl1: .Jan 28 18:32:51.521: STP[3]: Generating TC trap for port Port-channel1
Jan 28 18:32:52 svl1 45427: svl1: 13w0d: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
Jan 28 18:32:52 svl1 45428: svl1: 13w0d: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up
Jan 28 18:33:27 svl1 45429: svl1: .Jan 28 18:33:26.521: RSTP(3): stopping topology change timer

# SVL#2
Jan 28 18:30:35 svl2 9892: svl2: *Jan 28 18:28:38.854: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to up
Jan 28 18:30:38 svl2 9893: svl2: *Jan 28 18:28:41.648: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to up
Jan 28 18:30:40 svl2 9894: svl2: *Jan 28 18:28:43.893: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to down
Jan 28 18:30:40 svl2 9895: svl2: *Jan 28 18:28:44.183: %LINK-3-UPDOWN: Interface HundredGigE2/0/28, changed state to down
Jan 28 18:30:46 svl2 9896: svl2: *Jan 28 18:28:49.420: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to up
Jan 28 18:30:52 svl2 9897: svl2: *Jan 28 18:28:55.662: setting bridge id (which=3) prio 32771 prio cfg 32768 sysid 3 (on) id 8003.3c8b.7f57.30e0
Jan 28 18:30:52 svl2 9898: svl2: *Jan 28 18:28:55.662: RSTP(3): initializing port Po1
Jan 28 18:30:52 svl2 9899: svl2: *Jan 28 18:28:55.662: RSTP(3): Po1 is now designated
Jan 28 18:30:52 svl2 9900: svl2: *Jan 28 18:28:55.664: RSTP(3): transmitting a proposal on Po1
Jan 28 18:30:52 svl2 9901: svl2: *Jan 28 18:28:56.481: RSTP(3): stopping topology change timer
Jan 28 18:30:58 svl2 9902: svl2: *Jan 28 18:29:01.799: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to down
Jan 28 18:31:01 svl2 9903: svl2: *Jan 28 18:29:04.904: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to up
Jan 28 18:31:05 svl2 9904: svl2: *Jan 28 18:29:08.507: setting bridge id (which=3) prio 32771 prio cfg 32768 sysid 3 (on) id 8003.3c8b.7f57.30e0
Jan 28 18:31:05 svl2 9905: svl2: *Jan 28 18:29:08.507: RSTP(3): initializing port Po1
Jan 28 18:31:05 svl2 9906: svl2: *Jan 28 18:29:08.508: RSTP(3): Po1 is now designated
Jan 28 18:31:05 svl2 9907: svl2: *Jan 28 18:29:08.509: RSTP(3): transmitting a proposal on Po1
Jan 28 18:31:05 svl2 9908: svl2: *Jan 28 18:29:09.507: RSTP(3): transmitting a proposal on Po1
Jan 28 18:31:05 svl2 9909: svl2: *Jan 28 18:29:09.509: %LINEPROTO-5-UPDOWN: Line protocol on Interface HundredGigE1/0/28, changed state to up
Jan 28 18:31:06 svl2 9910: svl2: *Jan 28 18:29:09.654: RSTP(3): updt roles, received superior bpdu on Po1
Jan 28 18:31:06 svl2 9911: svl2: *Jan 28 18:29:09.654: RSTP(3): Po1 is now root port
Jan 28 18:31:06 svl2 9912: svl2: *Jan 28 18:29:09.654: RSTP(3): synced Po1
Jan 28 18:31:06 svl2 9913: svl2: *Jan 28 18:29:09.654: RSTP(3): starting topology change timer for 35 seconds
Jan 28 18:31:06 svl2 9914: svl2: *Jan 28 18:29:09.654: STP[3]: Generating TC trap for port Port-channel1
Jan 28 18:31:06 svl2 9915: svl2: *Jan 28 18:29:09.654: RSTP(3): transmitting an agreement on Po1 as a response to a proposal
Jan 28 18:31:07 svl2 9916: svl2: *Jan 28 18:29:10.507: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
Jan 28 18:31:07 svl2 9917: svl2: *Jan 28 18:29:11.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up
Jan 28 18:31:34 svl2 9918: svl2: *Jan 28 18:29:37.785: RSTP(3): updt roles, non-tracked event
Jan 28 18:31:34 svl2 9919: svl2: *Jan 28 18:29:37.786: RSTP(3): updt roles, root port Po1 going down
Jan 28 18:31:34 svl2 9920: svl2: *Jan 28 18:29:37.786: RSTP(3): we become the root bridge
Jan 28 18:31:34 svl2 9921: svl2: *Jan 28 18:29:37.786: RSTP(3): Po1 not in sync
Jan 28 18:31:34 svl2 9922: svl2: *Jan 28 18:29:37.786: RSTP(3): stopping topology change timer
Jan 28 18:31:35 svl2 9923: svl2: *Jan 28 18:29:38.785: %LINEPROTO-5-UPDOWN: Line protocol on Interface HundredGigE1/0/28, changed state to down
Jan 28 18:31:35 svl2 9924: svl2: *Jan 28 18:29:38.786: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to down
Jan 28 18:31:36 svl2 9925: svl2: *Jan 28 18:29:39.786: %LINK-3-UPDOWN: Interface Port-channel1, changed state to down
Jan 28 18:31:38 svl2 9926: svl2: *Jan 28 18:29:41.635: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to down
Jan 28 18:32:47 svl2 9927: svl2: *Jan 28 18:30:50.928: %LINK-3-UPDOWN: Interface HundredGigE1/0/28, changed state to up
Jan 28 18:32:50 svl2 9928: svl2: *Jan 28 18:30:53.972: setting bridge id (which=3) prio 32771 prio cfg 32768 sysid 3 (on) id 8003.3c8b.7f57.30e0
Jan 28 18:32:50 svl2 9929: svl2: *Jan 28 18:30:53.972: RSTP(3): initializing port Po1
Jan 28 18:32:50 svl2 9930: svl2: *Jan 28 18:30:53.972: RSTP(3): Po1 is now designated
Jan 28 18:32:50 svl2 9931: svl2: *Jan 28 18:30:53.974: RSTP(3): transmitting a proposal on Po1
Jan 28 18:32:50 svl2 9932: svl2: *Jan 28 18:30:54.972: %LINEPROTO-5-UPDOWN: Line protocol on Interface HundredGigE1/0/28, changed state to up
Jan 28 18:32:50 svl2 9933: svl2: *Jan 28 18:30:54.973: RSTP(3): transmitting a proposal on Po1
Jan 28 18:32:51 svl2 9934: svl2: *Jan 28 18:30:55.666: RSTP(3): updt roles, received superior bpdu on Po1
Jan 28 18:32:51 svl2 9935: svl2: *Jan 28 18:30:55.667: RSTP(3): Po1 is now root port
Jan 28 18:32:51 svl2 9936: svl2: *Jan 28 18:30:55.667: RSTP(3): synced Po1
Jan 28 18:32:51 svl2 9937: svl2: *Jan 28 18:30:55.667: RSTP(3): starting topology change timer for 35 seconds
Jan 28 18:32:51 svl2 9938: svl2: *Jan 28 18:30:55.667: STP[3]: Generating TC trap for port Port-channel1
Jan 28 18:32:51 svl2 9939: svl2: *Jan 28 18:30:55.667: RSTP(3): transmitting an agreement on Po1 as a response to a proposal
Jan 28 18:32:52 svl2 9940: svl2: *Jan 28 18:30:55.971: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
Jan 28 18:32:52 svl2 9941: svl2: *Jan 28 18:30:56.971: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up
Jan 28 18:33:27 svl2 9942: svl2: *Jan 28 18:31:30.668: RSTP(3): stopping topology change timer