Posts: 10
Threads: 4
Joined: Aug 2019
Reputation:
0
The answer has the interfaces grouped into po11, and configured as trunk interfaces
no interface po11
interface range e0/0 - 2
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 11 mode active
However, don't we have to specifically configure int po11 as a trunk as well?
EX
Interface po11
switchport trunk encapsulation dot1q
switchport mode trunk
Switchport trunk allowed vlans x,x,x
?????
Posts: 233
Threads: 2
Joined: Jan 2023
Reputation:
9
On modern devices, when you configure the command "channel-group <number> mode <active|passive>" on interfaces, the configurations under the interfaces are copied to the Port-channel automatically.
Posts: 1
Threads: 0
Joined: Jan 2026
Reputation:
0
My question would be for Task #2. To ensure that Sw10 is always the root bridge. Wouldn't you use priority of 0? If you just use root primary then if another siwtch is added with a lower priority then it would take over. Setting root primary only calculates for existing switches in topology.
I should be able to find information to back this up if needed.
Posts: 233
Threads: 2
Joined: Jan 2023
Reputation:
9
You are correct that if another switch with a lower priority were added, it could take over as the root. But the task is for the current network, not what might happen later on.
The same logic applies even if we set SW10 to priority 0. If another switch with priority 0 shows up, the MAC address still decides the root, so that’s not an absolute guarantee either.
In real networks, the root primary command is the recommended and cleaner way to set the root bridge. It follows Cisco best practices, works with the existing topology, and meets the requirement without being overly aggressive.
