02-20-2016 05:00 PM - edited 03-08-2019 04:39 AM
Below is the config of 2xCore and 4x2960S stacking switch config. the Red colour indiciate the missing vlan and ip default gateway please advise by adding them will fix the stacking problem. as end clinets are unable to get connect to network.
Both CORES are running HSPR
THQ-4507#show run interface vlan 370
Building configuration...
Current configuration : 337 bytes
!
interface Vlan370
description C_Hub1_Stack_1
ip address 10.178.85.4 255.255.255.128
ip helper-address 10.178.5.152
ip helper-address 10.178.5.153
ip helper-address 10.178.1.60
ip helper-address 10.178.1.61
no ip redirects
standby 2 ip 10.178.85.1
standby 2 priority 101
standby 2 preempt
standby 2 track 2 decrement 10
THQ-4507#show run interface vlan 371
Building configuration...
Current configuration : 309 bytes
!
interface Vlan371
description C_Hub1_Stack_2
ip address 10.178.85.132 255.255.255.128
ip helper-address 10.178.5.152
ip helper-address 10.178.5.153
ip helper-address 10.178.1.60
ip helper-address 10.178.1.61
no ip redirects
standby 3 ip 10.178.85.129
standby 3 priority 101
standby 3 preempt
end
SW-CDH-C39-HUB1-C10-1-2-3-4#show spanning-tree active
VLAN0001
Spanning tree enabled protocol rstp
Root ID Priority 8193
Address 649e.f36a.f880
Cost 100
Port 50 (GigabitEthernet1/0/50)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
Address 5006.ab1b.2b80
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Gi1/0/50 Root FWD 100 128.50 P2p
Gi2/0/50 Altn BLK 100 128.106 P2p
Gi3/0/50 Altn BLK 200 128.162 P2p
Gi4/0/50 Altn BLK 200 128.218 P2p
W-CDH-C39-HUB1-C10-1-2-3-4#show run interface gigabitEthernet 1/0/50
Building configuration...
Current configuration : 188 bytes
!
interface GigabitEthernet1/0/50
description SX-Fibre-to-HUB1
switchport trunk allowed vlan 1,2,314,370,371,394
switchport mode trunk
mls qos trust dscp
spanning-tree cost 100
end
Hub1-4507#show run interface gigabitEthernet 1/9
Building configuration...
Current configuration : 168 bytes
!
interface GigabitEthernet1/9
description Hub-1_Stack-1_48-G_1
switchport trunk allowed vlan 1,2,200,370,394,395,397,1002-1005,1025-4094 (MISSING 371)
switchport mode trunk
end
W-CDH-C39-HUB1-C10-1-2-3-4#show run interface gigabitEthernet 2/0/50
Building configuration...
Current configuration : 174 bytes
!
interface GigabitEthernet2/0/50
description THQ
switchport trunk allowed vlan 1,2,314,370,371,394
switchport mode trunk
mls qos trust dscp
spanning-tree cost 100
end
THQ-4507#show run interface gigabitEthernet 1/7
Building configuration...
Current configuration : 155 bytes
!
interface GigabitEthernet1/7
description Hub1_Stack1_48G_2
switchport trunk allowed vlan 1,2,200,370,394,395,397,1002-1005 (MISSING 314,371
switchport mode trunk
end
W-CDH-C39-HUB1-C10-1-2-3-4#show run interface gigabitEthernet 3/0/50
Building configuration...
Current configuration : 175 bytes
!
interface GigabitEthernet3/0/50
description HUB1
switchport trunk allowed vlan 1,2,314,370,371,394
switchport mode trunk
mls qos trust dscp
spanning-tree cost 200
end
Hub1-4507#show run interface gigabitEthernet 2/9
Building configuration...
Current configuration : 168 bytes
!
interface GigabitEthernet2/9
description Hub_1_Stack_2_48-G_1
switchport trunk allowed vlan 1,2,200,371,394,395,397,1002-1005,1025-4094 Missing 370
switchport mode trunk
end
SW-CDH-C39-HUB1-C10-1-2-3-4#show run interface gigabitEthernet 4/0/50
Building configuration...
Current configuration : 174 bytes
!
interface GigabitEthernet4/0/50
description THQ
switchport trunk allowed vlan 1,2,314,370,371,394
switchport mode trunk
mls qos trust dscp
spanning-tree cost 200
end
THQ-4507#show run interface gigabitEthernet 1/17
Building configuration...
Current configuration : 157 bytes
!
interface GigabitEthernet1/17
description Hub1_Stack2_48-G_2
switchport trunk allowed vlan 1,2,200,371,394,395,397,1002-1005 Missing 370
switchport mode trunk
end
Interface vlan 370
Description Chorley-Management-VLANs
Ip address 10.178.85.7 255.255.255.128
Ip default-gateway 10.178.85.1
will only giving the command on stack switch (ip default-gateway 10.178.85.1) fix the issue or i re-config the trunk vlans. in spamming tree only one trunk is root rest are blocking so shall i only re-config the root trunk (spanning tree root) or all of them please advise.
02-20-2016 07:08 PM
Hello sherazrose,
The are some information that needs to be more clear.
Are the end users not even communicating with the access switches (2960s)?? Can you se their MAC addresses?
Are the 4 2960s stacked?
Allowing vlan 370 should be done in every trunk if those links are redundant to the CORE SW, and so if the root had a failure the redundant link would take place to forward vlan 370 frames.
02-21-2016 01:04 AM
Hello Cavillag,
Yes the 2960s are stack switch running in stack of 4 switches.
the end user are can communicate. i can see the mac addresses.
yes i agree the vlan 370 and 371 are missing on Core trunks.
also i tried to ping from stacking switch to google 8.8.8.8
command i gave ping 8.8.8.8 source vlan 370 is sucessful
but ping 8.8.8.8 source vlan 371 is not working. so i thing the vlan 371 need to be configured on trunk and also ip default gatway needs to be setup.
please share your thoughts
02-21-2016 02:15 AM
Hello
on the core switch as its performing L3 routing your specify a defaul route and NOT ip default gateways
On the access stacks you apply an management addressing and Default gateway of your mangement vlan created on the core switch - no other default-gateway is required of any other L3 svi applied on the core for any other vlans.
For any host port attached to a vlan in which that vlan is pruned off the switch interconnect trunks - Connection will be negated unless that vlan is allowed to cross the trunks and is also in the vtp database
res
paul
02-21-2016 04:13 AM
Hi Paul
I undersand Core is performing L3 routing. I am more focus on the stacking 2960s. i change the trunk on the stacking and make sure both 2xcore trunk and stacking 2960 are matching same. Now i also set a ip default-gateway on stacking switch.
as this is a production network and we are looking now if this will reslove the problem as some of the devices are unable to get connect. however, once we reload/reboot the windows PC they can connect to the new stacking. I am under the impression is do to some thing with arp caching on windows PC.
02-21-2016 05:00 AM
Hello
Do you have an addressing issue pertaining to dhcp leasing? - Before the pcs are rebooted can they ping any of the layer 3 addressing on the core switch -
Manually release and renew the addressing on the affected host pcs and see what results you get -
Check the arp table on the hosts also
arp -a
route print
res
Paul
02-21-2016 05:40 AM
Hi Paul.
at the moment things see to be ok. but as its sunday not many people around and we thing it will be fine. however we shall know more on this by monday when staff will come back and connect to the nework.
I mention the same to my technial guy to check and arp-a entries.
I shall get back on monday with any updates.
i thing putting the ip-default gateway command to one of vlan 370 hsrp at 4xstack switch will fix the problem and also the match of trunking.
my tech guy mention they 4xstack switch take around 30 second to go from amber to green. i thing its normal time. i have notice 15 second. but what you thing 30 second amber than going green okay?
02-22-2016 02:36 AM
Thank all for your support. the network is working good since we match the correct trunk vlan and giving 4xcisco stacks 2060s a ip default-gateway to the core.
thanks you.
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