04-08-2011 05:15 AM - edited 03-06-2019 04:30 PM
Hello people,
This is no doubt a simple one however cant work out whats wrong..
I have a c3750 switch to switch connection.. looks like this.. (attached..)
I cannot ping the standby ip 10.128.16.137/29 from the top switch...
Switch config as follows:
interface GigabitEthernet1/0/8
description ada
switchport access vlan 71
switchport mode access
interface Vlan71
description ada
ip address 10.128.16.140 255.255.255.248
sh ip route output:
C 10.128.16.136/29 is directly connected, Vlan71
I dont have control of the 2 bottom switches as they are client ones..
there will be a 2nd switch installed at my end(top of diagram) sometime soon so that a second connection can be made to the second switch.. I will then use hsrp too...
What can be wrong?
thanks in advance..
Solved! Go to Solution.
04-11-2011 07:58 AM
When I change from trunk port to access port the spanning tree blocks on that port.
This is my int conf now:
interface GigabitEthernet1/0/8
description Ada
switchport access vlan 712
switchport mode access
As soon as I put this config on the interface spanning tree blocks..
(Sorry for the vlan typo earlier guys) I have always made sure when configuring the vlan 712..
spanning tree output for vlan 712
VLAN0712
Spanning tree enabled protocol rstp
Root ID Priority 33480
Address ecc8.8290.4680
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33480 (priority 32768 sys-id-ext 712)
Address ecc8.8290.4680
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300
Interface Role Sts Cost Prio.Nbr Type
---------------- ---- --- --------- -------- --------------------------------
Gi1/0/1 Desg FWD 4 128.1 P2p
Gi1/0/2 Desg FWD 4 128.2 P2p
Gi1/0/7 Desg FWD 4 128.7 P2p
Gi1/0/8 Desg BKN*4 128.8 P2p *TYPE_Inc
VTP mode is transparent too
by the way, just want to say thanks for all the support you guys are giving its much appreciated!
what do you think? what else can I try ?
really annoying me as I have done this before ...
04-11-2011 08:04 AM
Set the switch back to VTP client.
04-11-2011 08:24 AM
int config:
interface GigabitEthernet1/0/8
description Ada
switchport access vlan 712
switchport mode access
(vtp mode client.)
spanning tree is blking on the above port now..
what do you rekon?
04-11-2011 08:32 AM
I'm thinking that the switch you're connecting to is using root guard. I'm assuming that it's forcing your switchport into 'root inconsistent' state, but I can confirm this once you post your output.
04-11-2011 08:25 AM
I notice that your switch is attempting to be root of vlan 712. This probably explains the Post the '*TYPE_Inc' output. Post the output of:
show spanning-tree inconsist
In the meantime, to get your switch to work while we work out the real cause of the issue, you can increase your bridge priority value so that it doesn't attempt to be root.
Switch(config)#spanning-tree vlan 712 priority 61440
04-11-2011 09:08 AM
changed the priority to the highest value and my switch is still root.
VLAN0712
Spanning tree enabled protocol rstp
Root ID Priority 62152
Address ecc8.8290.4680
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 62152 (priority 61440 sys-id-ext 712)
Address ecc8.8290.4680
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300
Interface Role Sts Cost Prio.Nbr Type
---------------- ---- --- --------- -------- --------------------------------
Gi1/0/1 Desg FWD 4 128.1 P2p
Gi1/0/2 Desg FWD 4 128.2 P2p
Gi1/0/7 Desg FWD 4 128.7 P2p
Gi1/0/8 Desg BKN*4 128.8 P2p *TYPE_Inc
sh spanning-tree inconsist output:
Name Interface Inconsistency
-------------------- ---------------------- ------------------
VLAN0712 GigabitEthernet1/0/8 Port Type Inconsistent
Number of inconsistent ports (segments) in the system : 1
I tried something else..
I changed the cost of forwarding interfaces Gi1,Gi2 and Gi7 to 5.
Gi8 still shows blocking??
Interface Role Sts Cost Prio.Nbr Type
---------------- ---- --- --------- -------- --------------------------------
Gi1/0/1 Desg FWD 5 128.1 P2p
Gi1/0/2 Desg FWD 5 128.2 P2p
Gi1/0/7 Desg FWD 5 128.7 P2p
Gi1/0/8 Desg BKN*4 128.8 P2p *TYPE_Inc
incomplete entry address in ARP table for 10.128.16.137 too..
can BPDU filter help to troubleshoot? If i enable it it will filter bpdu's right?
04-11-2011 09:23 AM
I'm going to assume that there is no root guard configuration on this switch. With that said, post the output of 'show run | i net1/0/8|spanning'. There seems to be some type of spanning tree configuration here that has this port going into a root inconsistent state when it receives a BPDU.
04-11-2011 09:38 AM
heres the output for: show run | i net1/0/8|spanning
spanning-tree mode rapid-pvst
spanning-tree extend system-id
spanning-tree vlan 1 priority 28672
spanning-tree vlan 712 priority 61440
spanning-tree vlan 712 cost 5
spanning-tree vlan 712 cost 5
spanning-tree vlan 712 cost 5
interface GigabitEthernet1/0/8
spanning-tree bpdufilter enable
As you can see I enabled bpdu filter and am now able to reach the gateway!!
is there anyway to configure this to work without bpdu filter?
another question I now have it when I connect the 2nd link to a 2nd switch with hsrp configured will I cause storms? (it will be trunked to my 1st switch)
guys can tell you how much i appreciate your responses!
thanks very much.....
04-11-2011 10:13 AM
It would really be interesting to see the log buffer of this switch to see what caused the inconsistency. I'd sort that out before connecting to the standby switch and potentially causing some issues. I'll help as much as I can with that if you'd like.
04-11-2011 09:27 AM
And to answer your question, you can use BPDU filter in this case, but I recommend this type of workaround only when necessary. If you can get the job done with a simpler configuration, then that's the way to go.
04-08-2011 10:41 AM
I'm surprised that no one has considered VTP as an issue. Try setting the VTP mode on the top switch to transparent. That should resolve your issue.
Please rate if helpful.
Edit: VTP transparent is only an option if the top switch isn't using any vlan besides 71. If it is, then the native vlan is probaly your issue as Ian stated.
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