12-19-2014 06:28 AM - edited 03-07-2019 09:57 PM
I have Vlan 198, that works for some users and not for others. This Vlan on a 2811 Router, connected to a 6509 (Router 1) via port Gi8/1. I feel part of the issue in that Router 1 should be the root and not Router 2. I have tried to making router 1 the Root using "spanning-tree vlan 198 root primary.
Any assistance is greatly appreciated...
Router 1
spanning-tree vlan 1,4-7,12,16-17,57-58,128,130-131,198-199,261 priority 4096
VLAN0198
Spanning tree enabled protocol ieee
Root ID Priority 4294
Address 0025.b4ce.cb40
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 4294 (priority 4096 sys-id-ext 198)
Address 0025.b4ce.cb40
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Gi3/4 Desg FWD 4 128.260 P2p
Gi3/6 Desg FWD 4 128.262 P2p
Gi3/7 Desg FWD 4 128.263 P2p
Gi7/47 Desg FWD 4 128.815 P2p
Gi8/1 Desg FWD 4 128.897 P2p
Po1 Desg FWD 1 128.1665 P2p
Router 2
spanning-tree vlan 1,7,12,16,57-58,128,130-131,197-199,263,300 priority 8192
VLAN0198
Spanning tree enabled protocol ieee
Root ID Priority 4294
Address 0025.b4ce.cb40
Cost 1
Port 1665 (Port-channel1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 8390 (priority 8192 sys-id-ext 198)
Address 0025.b4ce.d700
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Po1 Root FWD 1 128.1665 P2p
Po23 Desg FWD 3 128.1670 P2p
12-19-2014 06:39 AM
Hi
Setting the root can optimise your topology, but not normally resolve connectivity issues. You have succesfully made R1 the root.
Can you detail your topology, i.e. what is connected to what, and where the VLAN is not working?
Maybe post your configs as well.
Aaron
12-19-2014 06:51 AM
12-19-2014 07:19 AM
Hi
VLAN 198 looks OK on R2; in that it can see that R1 is the root bridge.
It looks like only po1/po23 are active in the VLAN - have you configured the ports as access ports in VLAN198?
What cards/hardware/config is on R2?
Aaron
12-19-2014 08:08 AM
interface Port-channel1
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 998
switchport trunk allowed vlan 2-4094
switchport mode trunk
logging event trunk-status
logging event bundle-status
mls qos trust dscp
interface Port-channel23
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 998
switchport trunk allowed vlan 4,16,129,130,154,198,282,285,302,404
switchport mode trunk
switchport nonegotiate
logging event link-status
logging event trunk-status
logging event bundle-status
mls qos trust dscp
12-19-2014 11:01 AM
Hello
When you say it work for others can you elaborate- On the same switch or both switch or just on of them?
Also do these switches have vlans defined in there vtp database assuming they are cisco switches?
res
Paul
12-19-2014 11:12 AM
Users connect to R1 have no issues, some users on R2 can connect using Vlan 198. The vlan is defined in the vtp database located on R1. R2 is a client.
12-19-2014 11:33 AM
Hello
So can you confirm
- The vlans is populated in either switch?
- Po1 is between the rtrs
- P23 is between each rtr and switch
lastly have you made any changes to the physical interfaces for the portchannels
I can also see the native vlan not being allowed over the P23
sh etherchannel summary
sh int trunk
Also post the physical interfaces of each etherchannel.
res
Paul
12-19-2014 11:47 AM
Vlans are populated. Po1 connects R1 and R2. Po23 connects switch to R2.
#sh 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: 8
Number of aggregators: 8
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
1 Po1(SU) LACP Te1/1(P) Te2/1(P)
2 Po2(SU) LACP Te1/2(P) Te2/2(D)
3 Po3(SU) LACP Te1/3(P) Te2/3(D)
4 Po4(SD) LACP Te2/4(D)
10 Po10(SU) LACP Gi7/46(P) Gi8/46(P)
22 Po22(RD) -
23 Po23(SU) LACP Gi3/7(P) Gi4/7(P)
24 Po24(SU) LACP Gi3/8(P) Gi4/8(P)
interface GigabitEthernet3/7
description
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 998
switchport trunk allowed vlan 4,16,129,130,154,198,282,285,302,404
switchport mode trunk
switchport nonegotiate
logging event link-status
udld port aggressive
mls qos trust dscp
channel-group 23 mode active
end
interface GigabitEthernet4/7
description
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 998
switchport trunk allowed vlan 4,16,129,130,154,198,282,285,302,404
switchport mode trunk
switchport nonegotiate
logging event link-status
udld port aggressive
mls qos trust dscp
channel-group 23 mode active
end
Port Mode Encapsulation Status Native vlan
Po1 on 802.1q trunking 998
Po23 on 802.1q trunking 998
Port Vlans allowed and active in management domain
Po23 4,16,129-130,154,198,282,285,302,404
Port Vlans in spanning tree forwarding state and not pruned
Po1 2-7,12,15-18,20,22,24,32-33,44,46,48,56-58,72-80,96-109,128-131,135-136,138-144,146,148,152-167,194-195,197-199,205-208,212-214,231,244,256-257,260-281,293-309,340,401-407,409-412,464-466,495,528,560-564,592,624-625,656-658,662-666,668-671,673-678,682-688,998-999
Po23 4,16,129-130,154,198,282,285,302,404
12-19-2014 12:03 PM
Hello
The physical interfaces of PC23 don't look the same as its L2 PC.23 - Did you manually create this portchannel?
What connects to these PC's? and its here where the users who are having issue reside and is so just PC23 or others
res
Paul
12-19-2014 12:12 PM
The port-channel was created after the physical interfaces. It's just user computers that are connected to the switch that uses po23.
12-19-2014 12:24 PM
Hello
So you have another switch connected to switch 2 via pc23?
I am assuming this is a cisco switch also and is also acting as a host switch with man IP and D/G
Can you try re-creating the port--channels between these two switches and allow the native vlan across the trunk
1) delete the old PC and default physical interfaces and shut them down (if possible)
2) configure port-channel in physical interfaces
-- port-channel will be created automatically
3)create trunking encapsulation or access port mode directly in port-channel interface (NOT on the physical interfaces)
4)enable physical interfaces "no shut"
res
Paul
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide