CBS350 incinsistency port type after restart

[IvanZabaluyev]

Dear community,

I have a minor problem, but, I'd like to solve that problem, and understand how to configure my Cisco Business 350 switches.

In a few words, I have a bunch of access  Cisco Business 350 switches, with trunks connected to core switch 9200 using Link Aggregation ports. I am not using PAGP or LACP. I just turn on link aggregation for some ports on the access switch and core switch.

Each time CBS350 restarts, it became inaccessible. And as I found in logs, blocking happening on the CBS350 side with the error:

%STP-W-ENTERINCONSIST: Blocking Po2 on vlan 1. Inconsistency port type.

I am fixing it by just disconnecting and connecting back ports, that are used by my Link Aggregation port.

Ande in logs I have:

%STP-I-EXITINCONSIST: Unblocking Po2 on vlan 1. Port consistency type restored.

But I just disconnect and connect back my cables.

Could you please help me to solve that issue. It is not critical, but it is inconvenient to replug trunk ports each time cbs350 restarts.

[marce1000]

            - What's in the logs of the 9200 when this happens ?

 M.

[IvanZabaluyev]

Nothing on the 9200. No errors at all.

[marce1000]

           - Check firmware version on the cbs350   , use the latest.

 M.

[IvanZabaluyev]

Thank you for your reply.
I have the latest 3.1.1.7
Could someone recommend what to debug to try to find the root of the problem?
Thank you for your attention.

[marce1000]

       - Could you show the running configuration of the involved-ports on the cbs350 and the 9200 ?

 M.

[IvanZabaluyev]

Hello. I totally forgot that I run 2 X 9200 in the stack.

Mezzanine is my cbs350 switch.

So, procedure. step by step.

I just repower cbs350, and here are logs from 9200:

Jan  4 19:49:28.187: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/15, changed state to down

Jan  4 19:49:28.254: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/15, changed state to down

Jan  4 19:49:28.261: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel15, changed state to down

Jan  4 19:49:29.195: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/15, changed state to down

Jan  4 19:49:29.273: %LINK-3-UPDOWN: Interface Port-channel15, changed state to down

Jan  4 19:49:29.276: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/15, changed state to down

Jan  4 19:51:51.790: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/15, changed state to up

Jan  4 19:51:51.818: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/15, changed state to up

Jan  4 19:51:53.807: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/15, changed state to up

Jan  4 19:51:53.827: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/15, changed state to up

Jan  4 19:51:54.798: %LINK-3-UPDOWN: Interface Port-channel15, changed state to up

Jan  4 19:51:55.798: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel15, changed state to up

I can discover that switch with cdp and lldp:
Here is  sh lldp neighb:

Mezzanine           Gi2/0/15       120        B,R             gi24

Mezzanine           Gi1/0/15       120        B,R             gi23

But I can't still access that vi aping or any other ways.

Next, unplugging one of the ports from the Channel-group.

Here is 9200 stack output:

Jan  4 20:00:11.986: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/15, changed state to down

Jan  4 20:00:12.994: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/15, changed state to down

and now I can access that Mezzanine cbs350 switch with ping or ssh, or anything.
So, situation changed, when I just unplug one member of the channel-group.

Here are logs of the cbs350 after restart. I put not all lines, and cbs350 shows logs from bottom to top:

04-Jan-2022 11:52:13 :%STP-W-ENTERINCONSIST: Blocking Po2 on vlan 1. Inconsistency port type.

04-Jan-2022 11:52:12 :%STP-W-PORTSTATUS: gi11 of vlan 212: STP status Forwarding

04-Jan-2022 11:52:12 :%LINK-I-Up:  Vlan 212           

04-Jan-2022 11:52:12 :%LINK-I-Up:  gi11

04-Jan-2022 11:52:10 :%LINK-I-Up:  Vlan 1

04-Jan-2022 11:52:10 :%LINK-I-Up:  Po2

04-Jan-2022 11:52:10 :%LINK-I-Up:  gi24

04-Jan-2022 11:52:10 :%TRUNK-I-PORTADDED: Port gi24 added to Po2

04-Jan-2022 11:52:10 :%LINK-I-Up:  gi23

04-Jan-2022 11:52:10 :%TRUNK-I-PORTADDED: Port gi23 added to Po2

04-Jan-2022 11:52:10 :%LINK-I-Up:  gi18

04-Jan-2022 11:52:10 :%STP-W-PORTSTATUS: gi18 of vlan 306: STP status Forwarding

04-Jan-2022 11:52:10 :%LINK-I-Up:  gi16

04-Jan-2022 11:52:10 :%STP-W-PORTSTATUS: gi16 of vlan 306: STP status Forwarding

04-Jan-2022 11:52:10 :%LINK-I-Up:  gi14

04-Jan-2022 11:52:10 :%STP-W-PORTSTATUS: gi14 of vlan 306: STP status Forwarding

04-Jan-2022 11:52:10 :%STP-W-PORTSTATUS: gi13 of vlan 306: STP status Forwarding

04-Jan-2022 11:52:10 :%LINK-I-Up:  Vlan 306

04-Jan-2022 11:52:10 :%LINK-I-Up:  gi13

04-Jan-2022 11:52:07 :%LINK-I-Up:  loopback1

04-Jan-2022 11:52:07 :%LINK-W-Down:  Po2

04-Jan-2022 11:52:07 :%LINK-W-Down:  Po1

And bellow logs continues showing what happening, when I unplug one of the members of the Group-channel. PO2. Also read from bottom to top:

04-Jan-2022 12:00:38 :%STP-W-PORTSTATUS: gi22 of vlan 338: STP status Forwarding

04-Jan-2022 12:00:38 :%STP-W-PORTSTATUS: gi22 of vlan 402: STP status Forwarding

04-Jan-2022 12:00:38 :%STP-W-PORTSTATUS: gi22 of vlan 403: STP status Forwarding

04-Jan-2022 12:00:38 :%STP-W-PORTSTATUS: gi22 of vlan 326: STP status Forwarding

04-Jan-2022 12:00:38 :%STP-W-PORTSTATUS: gi22 of vlan 336: STP status Forwarding

04-Jan-2022 12:00:38 :%STP-W-PORTSTATUS: gi22 of vlan 337: STP status Forwarding

04-Jan-2022 12:00:38 :%STP-W-PORTSTATUS: gi22 of vlan 303: STP status Forwarding

04-Jan-2022 12:00:38 :%STP-W-PORTSTATUS: gi22 of vlan 306: STP status Forwarding

04-Jan-2022 12:00:38 :%STP-W-PORTSTATUS: gi22 of vlan 311: STP status Forwarding

04-Jan-2022 12:00:38 :%STP-W-PORTSTATUS: gi22 of vlan 321: STP status Forwarding

04-Jan-2022 12:00:38 :%STP-W-PORTSTATUS: gi22 of vlan 212: STP status Forwarding

04-Jan-2022 12:00:38 :%STP-W-PORTSTATUS: gi22 of vlan 300: STP status Forwarding

04-Jan-2022 12:00:35 :%STP-W-PORTSTATUS: Po2 of vlan 1: STP status Forwarding

04-Jan-2022 12:00:35 :%STP-W-PORTSTATUS: Po2 of vlan 402: STP status Forwarding

04-Jan-2022 12:00:35 :%STP-W-PORTSTATUS: Po2 of vlan 403: STP status Forwarding

04-Jan-2022 12:00:34 :%STP-W-PORTSTATUS: Po2 of vlan 338: STP status Forwarding

04-Jan-2022 12:00:34 :%STP-W-PORTSTATUS: Po2 of vlan 336: STP status Forwarding

04-Jan-2022 12:00:34 :%STP-W-PORTSTATUS: Po2 of vlan 326: STP status Forwarding

04-Jan-2022 12:00:34 :%STP-W-PORTSTATUS: Po2 of vlan 321: STP status Forwarding

04-Jan-2022 12:00:34 :%STP-W-PORTSTATUS: Po2 of vlan 303: STP status Forwarding

04-Jan-2022 12:00:34 :%STP-W-PORTSTATUS: Po2 of vlan 300: STP status Forwarding

04-Jan-2022 12:00:33 :%STP-I-EXITINCONSIST: Unblocking Po2 on vlan 1. Port consistency type restored.

04-Jan-2022 12:00:33 :%STP-W-PORTSTATUS: Po2 of vlan 212: STP status Forwarding

04-Jan-2022 12:00:33 :%STP-W-PORTSTATUS: Po2 of vlan 337: STP status Forwarding

04-Jan-2022 12:00:33 :%STP-W-PORTSTATUS: Po2 of vlan 311: STP status Forwarding

04-Jan-2022 12:00:33 :%STP-W-PORTSTATUS: Po2 of vlan 306: STP status Forwarding

04-Jan-2022 12:00:32 :%LINK-I-Up:  Vlan 403

04-Jan-2022 12:00:32 :%LINK-I-Up:  Vlan 402

04-Jan-2022 12:00:32 :%LINK-I-Up:  Vlan 338

04-Jan-2022 12:00:32 :%LINK-I-Up:  Vlan 337

04-Jan-2022 12:00:32 :%LINK-I-Up:  Vlan 336

04-Jan-2022 12:00:32 :%LINK-I-Up:  Vlan 326

04-Jan-2022 12:00:32 :%LINK-I-Up:  Vlan 321

04-Jan-2022 12:00:32 :%LINK-I-Up:  Vlan 311

04-Jan-2022 12:00:32 :%LINK-I-Up:  Vlan 303

04-Jan-2022 12:00:32 :%LINK-I-Up:  Vlan 300           

04-Jan-2022 12:00:31 :%STP-W-ENTERINCONSIST: Blocking Po2 on vlan 1. Inconsistency port type.

04-Jan-2022 12:00:31 :%LINK-W-Down:  gi23

04-Jan-2022 12:00:31 :%TRUNK-W-PORTDOWN: Port gi23 removed from Po2: port is down/notPresent  ''I removed g23 from the switch''

And here are sh config from 9200 stack:

....

interface Port-channel15

 switchport mode trunk

....

interface GigabitEthernet1/0/15

 switchport mode trunk

 channel-group 15 mode on

...

interface GigabitEthernet2/0/15

 switchport mode trunk

 channel-group 15 mode on

.....

Next, cbs350 port-configurations:

!

interface GigabitEthernet23

 no eee enable

 ip dhcp snooping trust

 no spanning-tree portfast

 channel-group 2 mode on

 switchport mode trunk

 no eee lldp enable

!

interface GigabitEthernet24

 no eee enable

 ip dhcp snooping trust

 no spanning-tree portfast

 channel-group 2 mode on

 switchport mode trunk

 no eee lldp enable

.....

!

interface Port-Channel2

 description TR2

 ip dhcp snooping trust

 spanning-tree link-type point-to-point

 switchport mode trunk

 macro description switch

 !next command is internal.

 macro auto smartport dynamic_type switch

!

That's it.


Thank you for your attention.

Best Regards,

Ivan Zabaluyev.

[marce1000]

               - Try channel-group 2 mode auto on both port configurations (Gi23 and Gi24) on the CBS350

 M.

[IvanZabaluyev]

Unfortunately, it did not help

I put first mode auto on 350. 

Everything is the same but additionally, I have negotiation messages on the 9200 stack side. Here they are:

TREE-2-BLOCK_PVID_LOCAL: Blocking Port-channel15 on VLAN0001. Inconsistent local vlan.

Jan  6 01:02:27.542: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/15, changed state to up

Jan  6 01:02:28.526: %LINK-3-UPDOWN: Interface Port-channel15, changed state to up

Jan  6 01:02:29.527: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel15, changed state to up

Jan  6 01:02:41.555: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking Port-channel15 on VLAN0001. Port consistency restored.

So, as you can see, spanning tree blocking, then unblocking. 

But on the 350 side it is blocking and not unblocking. 

When I unplug one of the members of Po2, everything starting to work with consistency restored. Putting back that member, and everything still working.

I put LACP negotiation on both sides.
Everything working the same way.

Thank you for your attention.

[marce1000]

 - For the port channel on the cbs350 remove the red-marked commands and check if that can help :

interface Port-Channel2

 description TR2

 ip dhcp snooping trust

 spanning-tree link-type point-to-point

 switchport mode trunk

 macro description switch

 !next command is internal.

 macro auto smartport dynamic_type switch

 M.

[IvanZabaluyev]

Did not help. 

After applying these changes, I made a broadcast storm. Now I was happy, that configuration was not stored after applying, and the repower of the device fixed the whole system. But, This did not help me to eliminate the first issue. Anyway, thank you for your help.

[marce1000]

 - You may want to create a TAC case : https://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html

 M.

[Georg Pauwen]

Hello,

I guess this must have something to do with spanning tree. Is the core 9200 the root for your Vlans ? Can you post the output of:

shpw spanning tree

in order to check which switch is the root ?

[IvanZabaluyev]

Thank you for your reply.

I double-checked. 

9200 stack was and is a root primary for spanning tree for most of my VLANs. Now it is a root primary for all my vlans.

After assuring that 9200stack is a root for all VLANs, and setting LACP on both sides to active instead of on, I repeated repower of the CBS350, and here is outputs:

9200 stack:

# Shutdown:

Jan 12 21:03:42.305: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/15, changed state to down

Jan 12 21:03:42.327: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/15, changed state to down

Jan 12 21:03:42.333: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel15, changed state to down

Jan 12 21:03:43.315: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/15, changed state to down

Jan 12 21:03:43.341: %LINK-3-UPDOWN: Interface Port-channel15, changed state to down

Jan 12 21:03:43.360: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/15, changed state to down

# cbs350 got back after restart:

9200stack#

9200stack#

Jan 12 21:06:14.582: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/15, changed state to up

Jan 12 21:06:14.614: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/15, changed state to up

Jan 12 21:06:17.795: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking Port-channel15 on VLAN0001. Inconsistent local vlan.

Jan 12 21:06:18.774: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/15, changed state to up

Jan 12 21:06:18.782: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/15, changed state to up

Jan 12 21:06:19.758: %LINK-3-UPDOWN: Interface Port-channel15, changed state to up

Jan 12 21:06:20.758: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel15, changed state to up

Jan 12 21:06:32.795: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking Port-channel15 on VLAN0001. Port consistency restored.

and here is cbs350 log output during startup resulting PO2 on VLAN1 blocked, and removing one of the members of the group-channel make everything work again:

## unfortunately cbs 350 record everything from the bottom to top,. Please read sequence from the bottom.

12-Jan-2022 13:12:54 :%STP-W-PORTSTATUS: gi22 of vlan 311: STP status Forwarding

12-Jan-2022 13:12:54 :%STP-W-PORTSTATUS: gi22 of vlan 321: STP status Forwarding

12-Jan-2022 13:12:54 :%STP-W-PORTSTATUS: gi22 of vlan 300: STP status Forwarding

12-Jan-2022 13:12:54 :%STP-W-PORTSTATUS: gi22 of vlan 303: STP status Forwarding

12-Jan-2022 13:12:54 :%STP-W-PORTSTATUS: gi22 of vlan 306: STP status Forwarding

12-Jan-2022 13:12:54 :%STP-W-PORTSTATUS: gi22 of vlan 212: STP status Forwarding

12-Jan-2022 13:10:51 :%STP-W-PORTSTATUS: gi22 of vlan 1: STP status Forwarding

12-Jan-2022 13:10:46 :%LINK-I-Up:  gi22

12-Jan-2022 13:10:42 :%LINK-W-Down:  gi22

12-Jan-2022 13:10:25 :%STP-W-PORTSTATUS: gi18 of vlan 1: STP status Forwarding

12-Jan-2022 13:10:25 :%STP-W-PORTSTATUS: gi16 of vlan 1: STP status Forwarding

12-Jan-2022 13:10:25 :%STP-W-PORTSTATUS: gi14 of vlan 1: STP status Forwarding

12-Jan-2022 13:10:25 :%STP-W-PORTSTATUS: gi13 of vlan 1: STP status Forwarding

12-Jan-2022 13:10:25 :%STP-W-PORTSTATUS: gi11 of vlan 1: STP status Forwarding

12-Jan-2022 13:10:19 :%STP-W-PORTSTATUS: gi22 of vlan 1: STP status Forwarding

12-Jan-2022 13:10:14 :%LINK-I-Up:  gi22

12-Jan-2022 13:10:10 :%NT_poe-I-PowerNegStatusExpire: Port gi22 power negotiation moved to expire state, power protocol and allocation will remain at 25W (LLDP) until port down/up cycle

12-Jan-2022 13:10:10 :%LINK-W-Down:  gi22

12-Jan-2022 13:10:01 :%NT_poe-I-PowerNegStatus: Port gi22 power negotiation completed, LLDP resolved power is 25 watts

12-Jan-2022 13:09:59 :%TRUNK-I-PORTADDED: Port gi23 added to Po2

12-Jan-2022 13:09:55 :%STP-W-PORTSTATUS: Po2 of vlan 1: STP status Forwarding

12-Jan-2022 13:09:54 :%STP-W-PORTSTATUS: Po2 of vlan 311: STP status Forwarding

12-Jan-2022 13:09:54 :%STP-W-PORTSTATUS: Po2 of vlan 306: STP status Forwarding

12-Jan-2022 13:09:54 :%LINK-I-Up:  gi23

 # putting back member of the channel-group and everything continues to work.

12-Jan-2022 13:09:53 :%STP-W-PORTSTATUS: Po2 of vlan 321: STP status Forwarding

12-Jan-2022 13:09:53 :%STP-W-PORTSTATUS: Po2 of vlan 303: STP status Forwarding

12-Jan-2022 13:09:53 :%STP-W-PORTSTATUS: Po2 of vlan 300: STP status Forwarding

12-Jan-2022 13:09:53 :%STP-I-EXITINCONSIST: Unblocking Po2 on vlan 1. Port consistency type restored.

# and now everything restored!   

12-Jan-2022 13:09:53 :%STP-W-PORTSTATUS: Po2 of vlan 212: STP status Forwarding

12-Jan-2022 13:09:51 :%STP-W-ENTERINCONSIST: Blocking Po2 on vlan 1. Inconsistency port type.

  # blocking again 

12-Jan-2022 13:09:51 :%LINK-I-Up:  Vlan 321

12-Jan-2022 13:09:51 :%LINK-I-Up:  Vlan 311           

12-Jan-2022 13:09:51 :%LINK-I-Up:  Vlan 303

12-Jan-2022 13:09:51 :%LINK-I-Up:  Vlan 300

12-Jan-2022 13:09:50 :%LINK-W-Down:  gi23

12-Jan-2022 13:09:50 :%TRUNK-W-PORTREMOVED: Port gi23 removed from Po2

 # Now I disconnect one of the members of the channel-group  

12-Jan-2022 13:08:22 :%INIT-I-Startup: Cold Startup

12-Jan-2022 13:06:58 :%STP-W-PORTSTATUS: gi22 of vlan 1: STP status Forwarding

12-Jan-2022 13:06:58 :%SYSLOG-N-LOGGING: Logging started.

12-Jan-2022 13:06:53 :%LINK-I-Up:  gi22

12-Jan-2022 13:06:22 :%STP-W-ENTERINCONSIST: Blocking Po2 on vlan 1. Inconsistency port type.

  # at this point PO2 is blocked.

12-Jan-2022 13:06:22 :%LINK-I-Up:  Vlan 1

12-Jan-2022 13:06:22 :%LINK-I-Up:  Po2                

12-Jan-2022 13:06:22 :%TRUNK-I-PORTADDED: Port gi24 added to Po2

12-Jan-2022 13:06:22 :%TRUNK-I-PORTADDED: Port gi23 added to Po2

12-Jan-2022 13:06:19 :%STP-W-PORTSTATUS: gi11 of vlan 212: STP status Forwarding

12-Jan-2022 13:06:19 :%LINK-I-Up:  Vlan 212

12-Jan-2022 13:06:19 :%LINK-I-Up:  gi11

12-Jan-2022 13:06:17 :%LINK-I-Up:  gi24

12-Jan-2022 13:06:17 :%LINK-I-Up:  gi23

12-Jan-2022 13:06:17 :%LINK-I-Up:  gi18

12-Jan-2022 13:06:17 :%STP-W-PORTSTATUS: gi18 of vlan 306: STP status Forwarding

12-Jan-2022 13:06:17 :%LINK-I-Up:  gi16

12-Jan-2022 13:06:17 :%STP-W-PORTSTATUS: gi16 of vlan 306: STP status Forwarding

12-Jan-2022 13:06:17 :%LINK-I-Up:  gi14

12-Jan-2022 13:06:16 :%STP-W-PORTSTATUS: gi14 of vlan 306: STP status Forwarding

12-Jan-2022 13:06:16 :%STP-W-PORTSTATUS: gi13 of vlan 306: STP status Forwarding

12-Jan-2022 13:06:16 :%LINK-I-Up:  Vlan 306

12-Jan-2022 13:06:16 :%LINK-I-Up:  gi13

12-Jan-2022 13:06:14 :%LINK-I-Up:  loopback1

12-Jan-2022 13:06:14 :%LINK-W-Down:  Po2

12-Jan-2022 13:06:14 :%LINK-W-Down:  Po1

12-Jan-2022 13:06:14 :%2SWTRUNK-I-TRNKPORTPARAM: auto-negotiation/adv. capabilities of port gi28 differ from auto-negotiation/adv. capabilities of Po1

12-Jan-2022 13:06:14 :%2SWTRUNK-I-TRNKPORTPARAM: auto-negotiation/adv. capabilities of port gi27 differ from auto-negotiation/adv. capabilities of Po1

12-Jan-2022 13:06:14 :%LINK-W-Down:  gi28             

12-Jan-2022 13:06:14 :%2SWTRUNK-I-TRNKPORTPARAM: auto-negotiation/adv. capabilities of port gi28 differ from auto-negotiation/adv. capabilities of Po1

12-Jan-2022 13:06:14 :%2SWTRUNK-I-TRNKPORTPARAM: auto-negotiation/adv. capabilities of port gi28 differ from auto-negotiation/adv. capabilities of Po1

12-Jan-2022 13:06:14 :%2SWTRUNK-I-TRNKPORTPARAM: auto-negotiation/adv. capabilities of port gi28 differ from auto-negotiation/adv. capabilities of Po1

12-Jan-2022 13:06:14 :%LINK-W-Down:  gi27

12-Jan-2022 13:06:14 :%2SWTRUNK-I-TRNKPORTPARAM: auto-negotiation/adv. capabilities of port gi27 differ from auto-negotiation/adv. capabilities of Po1

12-Jan-2022 13:06:14 :%2SWTRUNK-I-TRNKPORTPARAM: auto-negotiation/adv. capabilities of port gi27 differ from auto-negotiation/adv. capabilities of Po1

12-Jan-2022 13:06:14 :%2SWTRUNK-I-TRNKPORTPARAM: auto-negotiation/adv. capabilities of port gi27 differ from auto-negotiation/adv. capabilities of Po1

12-Jan-2022 13:06:14 :%LINK-W-Down:  gi26

12-Jan-2022 13:06:14 :%LINK-W-Down:  gi25

12-Jan-2022 13:06:14 :%LINK-W-Down:  gi24

12-Jan-2022 13:06:14 :%LINK-W-Down:  gi23             

12-Jan-2022 13:06:14 :%LINK-W-Down:  gi22

12-Jan-2022 13:06:14 :%LINK-W-Down:  gi21

12-Jan-2022 13:06:14 :%LINK-W-Down:  gi20

12-Jan-2022 13:06:14 :%LINK-W-Down:  gi19

12-Jan-2022 13:06:14 :%LINK-W-Down:  gi18

12-Jan-2022 13:06:14 :%LINK-W-Down:  gi17

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi16

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi15

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi14

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi13

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi12             

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi11

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi10

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi9

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi8

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi7

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi6

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi5

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi4

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi3

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi2

12-Jan-2022 13:06:13 :%LINK-W-Down:  gi1              

12-Jan-2022 21:06:08 :%SNMP-I-CDBITEMSNUM: Number of startup configuration items loaded: 435

12-Jan-2022 21:06:08 :%SNMP-I-CDBITEMSNUM: Number of running configuration items loaded: 435

12-Jan-2022 21:06:07 :%TIMEMANAGE-N-RTCUPDATE: The system clock was updated to 12-Jan-2022 21:06:07 UTC by the RTC component of unit 1

12-Aug-2021 02:58:53 :%MLDP-I-CONTROLLER: Switching to the active mode.

12-Aug-2021 02:58:52 :%Entity-I-SEND-ENT-CONF-CHANGE-TRAP: entity configuration change trap.

12-Aug-2021 02:58:50 :%Environment-W-RPS-STAT-MSG: Power supply source changed to Main Power Supply.

12-Aug-2021 02:58:44 :%INIT-I-InitCompleted: Initialization task is completed

So, something is wrong, but what is wrong is still unclear.

Thank you for your attention.

Best Regards,

Ivan

[marce1000]

 - Actually as I now look on it and as George said ,it effectively means that the original problem has been resolved and that you need those removed settings. As George said you >then need to make sure that the network has a valid spanning-tree setup and a correct root-bridge configured (e.g.) - M.

 M.