cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5223
Views
0
Helpful
13
Replies

Trunk between 4500-X and 4507R not working

T.Ratschkowski
Level 1
Level 1

Hi all,

i have got a new switch (4500-X) which i would like to connect to our existing 4507R switch. So i configured trunk ports on each of them, like i do this with all of my other access switches. I tried so many things, but i cant reach vlans from the new switch and iam totaly out of ideas

Iam quite sure that i make a verry dump config issue, but i cant fine the fault in my config...hopyfully someone could please help me? I hope this is the right information you need.

Many many Thanks!

The "OLD" Switch (4507R):

OLD#sh ver

Cisco IOS Software, Catalyst 4500 L3 Switch Software (cat4500-IPBASEK9-M), Version 12.2(54)SG, RELEASE SOFTWARE (fc3)

OLD#sh run int gi3/6

Building configuration...

Current configuration : 149 bytes

!

interface GigabitEthernet3/6

switchport trunk encapsulation dot1q

switchport mode trunk

switchport nonegotiate

end

OLD#sh int gi3/6 switch

Name: Gi3/6

Switchport: Enabled

Administrative Mode: trunk

Operational Mode: trunk

Administrative Trunking Encapsulation: dot1q

Operational Trunking Encapsulation: dot1q

Negotiation of Trunking: Off

Access Mode VLAN: 1 (default)

Trunking Native Mode VLAN: 1 (default)

Administrative Native VLAN tagging: enabled

Voice VLAN: none

Administrative private-vlan host-association: none

Administrative private-vlan mapping: none

Administrative private-vlan trunk native VLAN: none

Administrative private-vlan trunk Native VLAN tagging: enabled

Administrative private-vlan trunk encapsulation: dot1q

Administrative private-vlan trunk normal VLANs: none

Administrative private-vlan trunk associations: none

Administrative private-vlan trunk mappings: none

Operational private-vlan: none

Trunking VLANs Enabled: ALL

Pruning VLANs Enabled: 2-1001

Capture Mode Disabled

Capture VLANs Allowed: ALL

Unknown unicast blocked: disabled

Unknown multicast blocked: disabled

Appliance trust: none

OLD#sh int gi3/6 trunk

Port        Mode             Encapsulation  Status        Native vlan

Gi3/6       on               802.1q         trunking      1

Port        Vlans allowed on trunk

Gi3/6       1-4094

Port        Vlans allowed and active in management domain

Gi3/6       1-3,9-10,20,23-24,26,32-40,66-68,95-101,110-111,120,200,500-501,510,995-999

Port        Vlans in spanning tree forwarding state and not pruned

Gi3/6       1

The "NEW" Switch (4500-X):

NEW#sh ver

Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSALK9-M), Version 03.04.00.SG RELEASE SOFTWARE (fc3)

NEW#sh run int te1/32

Building configuration...

Current configuration : 94 bytes

!

interface TenGigabitEthernet1/32

switchport mode trunk

end

NEW#sh int te1/32 switchport

Name: Te1/32

Switchport: Enabled

Administrative Mode: trunk

Operational Mode: trunk

Administrative Trunking Encapsulation: dot1q

Operational Trunking Encapsulation: dot1q

Negotiation of Trunking: On

Access Mode VLAN: 1 (default)

Trunking Native Mode VLAN: 1 (default)

Administrative Native VLAN tagging: enabled

Voice VLAN: none

Administrative private-vlan host-association: none

Administrative private-vlan mapping: none

Administrative private-vlan trunk native VLAN: none

Administrative private-vlan trunk Native VLAN tagging: enabled

Administrative private-vlan trunk encapsulation: dot1q

Administrative private-vlan trunk normal VLANs: none

Administrative private-vlan trunk associations: none

Administrative private-vlan trunk mappings: none

Operational private-vlan: none

Trunking VLANs Enabled: ALL

Pruning VLANs Enabled: 2-1001

Capture Mode Disabled

Capture VLANs Allowed: ALL

Unknown unicast blocked: disabled

Unknown multicast blocked: disabled

Appliance trust: none

NEW#sh int te1/32 trun

Port        Mode             Encapsulation  Status        Native vlan

Te1/32      on               802.1q         trunking      1

Port        Vlans allowed on trunk

Te1/32      1-4094

Port        Vlans allowed and active in management domain

Te1/32      1-3,9-10,20,23-24,26,32-40,66-68,95-101,110-111,120,200,500-501,510,995-999

Port        Vlans in spanning tree forwarding state and not pruned

Te1/32      1-3,9-10,20,23-24,26,32-40,66-68,95-101,110-111,120,200,500-501,510,995-999

1 Accepted Solution

Accepted Solutions

Tobias

The ip default-gateway command on the new switch should allow it to talk to the old switch L3 vlan interfaces. The docs for the 4500-X however are a little vague in terms of when you need to use a static route. Can you add this to your new switch and see if it changes anything -

ip route 0.0.0.0 0.0.0.0 10.98.0.254

Jon

View solution in original post

13 Replies 13

Mark Yeates
Level 7
Level 7

Tobias,

The reason the trunk is not coming up is becasue you have a 1G interface connecting to a 10G. Try connecting a 1G to 1G or 10G to 10G. You cannot connect these interfaces at different speeds.

HTH,

Mark

Mark,

in both ports are only 1G gbics..i thought that should work?

Thanks,

tobias

Hi Tobias,

If you want to set up the link , try to set speed of the Te interface manually to 1000:

Int te1/32

Speed 1000

Switchport nonegotiate

And if would be necessary, do the dame on interface gi3/6:

Int gi3/6

Speed 1000

Be sure that the TenGigaEthernet module is 1G/10G compliant.

Good luck.

Best regards.

Hello

1. The 4500x has dual purpose UPLINKS, they can be either 10gig or 1gig, the speed is auto-detected.

Tobias.

Either the interface is down, down; Or there is a problem with spanning-tree.

- The problem is spanning-tree, vlans in forwarding state: vlan 1 only. So even when other vlans are allowed to cross the trunk STP is forwarding in that instance.

OLD#sh int gi3/6 trunk

Port        Mode             Encapsulation  Status        Native vlan

Gi3/6       on               802.1q         trunking      1

Port        Vlans allowed on trunk

Gi3/6       1-4094

Port        Vlans allowed and active in management domain

Gi3/6       1-3,9-10,20,23-24,26,32-40,66-68,95-101,110-111,120,200,500-501,510,995-999

Port        Vlans in spanning tree forwarding state and not pruned

Gi3/6       1

- Now in the new switch, all vlans are allowed and forwarding.

NEW#sh int te1/32 trun

Port        Mode             Encapsulation  Status        Native vlan

Te1/32      on               802.1q         trunking      1

Port        Vlans allowed on trunk

Te1/32      1-4094

Port        Vlans allowed and active in management domain

Te1/32      1-3,9-10,20,23-24,26,32-40,66-68,95-101,110-111,120,200,500-501,510,995-999

Port        Vlans in spanning tree forwarding state and not pruned

Te1/32      1-3,9-10,20,23-24,26,32-40,66-68,95-101,110-111,120,200,500-501,510,995-999

I have seen this issue before, when one switch is in vtp transparent and the other is either client or server. Can you share the output of the command show vtp status for both switches.

Regards.

Wilson B.

!Please rate useful post.    

Hello Wilson,

sorry for the late reply. Following are the two outputs:

OLD#sh vtp stat

VTP Version capable             : 1 to 3

VTP version running             : 1

VTP Domain Name                 : domain99

VTP Pruning Mode                : Enabled

VTP Traps Generation            : Disabled

Device ID                       : 000c.30b1.7540

Configuration last modified by 10.98.0.254 at 6-17-13 11:52:16

Local updater ID is 10.98.0.254 on interface Vl1 (lowest numbered VLAN interface found)

Feature VLAN:

--------------

VTP Operating Mode                : Server

Maximum VLANs supported locally   : 1005

Number of existing VLANs          : 44

Configuration Revision            : 59

MD5 digest                        : 0xAF 0xE7 0xA6 0x16 0xA3 0xED 0xFE 0xBC

                                    0x5C 0xF6 0x51 0xE4 0x23 0x5C 0xF8 0x9F

NEW#sh vtp stat

VTP Version capable             : 1 to 3

VTP version running             : 1

VTP Domain Name                 : domain99

VTP Pruning Mode                : Enabled

VTP Traps Generation            : Disabled

Device ID                       : f872.ead8.4400

Configuration last modified by 10.98.0.254 at 6-17-13 11:52:16

Feature VLAN:

--------------

VTP Operating Mode                : Client

Maximum VLANs supported locally   : 1005

Number of existing VLANs          : 44

Configuration Revision            : 59

MD5 digest                        : 0xAF 0xE7 0xA6 0x16 0xA3 0xED 0xFE 0xBC

                                    0x5C 0xF6 0x51 0xE4 0x23 0x5C 0xF8 0x9F

Tobias

Can you post "sh spanning-tree vlan 3" from each switch

Are both interfaces showing as up/up ?

Jon

Hi!

Yes, sure:

######### OLD ##########

OLD#sh spanning-tree vlan 3

VLAN0003

  Spanning tree enabled protocol ieee

  Root ID    Priority    32771

             Address     000c.30b1.7540

             This bridge is the root

             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec

  Bridge ID  Priority    32771  (priority 32768 sys-id-ext 3)

             Address     000c.30b1.7540

             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec

             Aging Time  300 sec

Interface           Role Sts Cost      Prio.Nbr Type

------------------- ---- --- --------- -------- --------------------------------

Gi3/5               Desg FWD 4         128.133  P2p

Gi3/6               Desg FWD 4         128.134  P2p

Gi4/2               Desg FWD 4         128.194  P2p

Gi4/3               Desg FWD 4         128.195  P2p

Gi5/1               Desg FWD 4         128.257  P2p

Gi5/3               Desg FWD 4         128.259  P2p

Gi5/4               Desg FWD 4         128.260  P2p

Gi5/5               Desg FWD 4         128.261  P2p

Gi5/6               Desg FWD 4         128.262  P2p

Gi6/1               Desg FWD 4         128.321  P2p

Gi6/2               Desg FWD 4         128.322  P2p

Gi6/3               Desg FWD 4         128.323  P2p

Gi6/5               Desg FWD 4         128.325  P2p

Gi6/6               Desg FWD 4         128.326  P2p

Gi7/1               Desg FWD 4         128.385  P2p

Gi7/2               Desg FWD 4         128.386  P2p

Gi7/4               Desg FWD 4         128.388  P2p

Gi7/5               Desg FWD 4         128.389  P2p

Gi7/6               Desg FWD 4         128.390  P2p

Po3                 Desg FWD 3         128.643  P2p

Po6                 Desg FWD 3         128.646  P2p

Po7                 Desg FWD 3         128.647  P2p

OLD#sh int gi3/6

GigabitEthernet3/6 is up, line protocol is up (connected)

  Hardware is Gigabit Ethernet Port, address is 0016.9dd4.1fe7 (bia 0016.9dd4.1fe7)

  Description: trunk core NEU

  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Full-duplex, 1000Mb/s, link type is auto, media type is 1000BaseSX

  Media-type configured as SFP connector

  input flow-control is on, output flow-control is off

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 00:00:04, output never, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 9000 bits/sec, 16 packets/sec

     809802 packets input, 156747108 bytes, 0 no buffer

     Received 809180 broadcasts (809157 multicasts)

     0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 input packets with dribble condition detected

     77368681 packets output, 5652973144 bytes, 0 underruns

     0 output errors, 0 collisions, 3 interface resets

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

######### NEW ##########

NEW#sh spanning-tree vlan 3

VLAN0003

  Spanning tree enabled protocol ieee

  Root ID    Priority    32771

             Address     000c.30b1.7540

             Cost        4

             Port        32 (TenGigabitEthernet1/32)

             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec

  Bridge ID  Priority    32771  (priority 32768 sys-id-ext 3)

             Address     f872.ead8.4400

             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec

             Aging Time  300 sec

Interface           Role Sts Cost      Prio.Nbr Type

------------------- ---- --- --------- -------- --------------------------------

Te1/32              Root FWD 4         128.32   P2p

NEW#sh int ten 1/32

TenGigabitEthernet1/32 is up, line protocol is up (connected)

  Hardware is Ten Gigabit Ethernet Port, address is f872.ead8.441f (bia f872.ead8.441f)

  Description: trunk sw99rz1-1-1

  MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Full-duplex, 1000Mb/s, link type is auto, media type is 1000BaseSX

  input flow-control is on, output flow-control is on

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 00:00:00, output never, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 13000 bits/sec, 18 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     365663 packets input, 26752705 bytes, 0 no buffer

     Received 365496 broadcasts (363520 multicasts)

     0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 input packets with dribble condition detected

     3843 packets output, 745065 bytes, 0 underruns

     0 output errors, 0 collisions, 3 interface resets

     0 unknown protocol drops

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

Thanks a lot!

tobias

Tobias

That looks fine, STP BPDUs are certainly going across the link because the new switch recognises the old switch as STP root for vlan 3.

When you say you can't reach vlans how exactly are you testing this ?

Can you post a "sh vlan brief" from the new switch ?

Jon

Hi and thanks for your time!

 

I cant reach non of the vlan interfaces configured on the OLD switch, only vlan1 interface.

 

I attach the config from OLD switch (NEW switch is connected to GI3/6) and NEW switch.

 

 

 

 

VLAN on NEW switch:

NEW#sh vlan brief

 

 

VLAN Name                             Status    Ports

---- -------------------------------- --------- -------------------------------

1    default                          active    Te1/1, Te1/2, Te1/3, Te1/4

                                                Te1/5, Te1/6, Te1/7, Te1/8

                                                Te1/9, Te1/10, Te1/11, Te1/12

                                                Te1/13, Te1/14, Te1/15, Te1/16

                                                Te1/17, Te1/18, Te1/19, Te1/20

                                                Te1/21, Te1/22, Te1/23, Te1/24

                                                Te1/25, Te1/26, Te1/27, Te1/28

                                                Te1/29, Te1/30, Te1/31, Te2/1

                                                Te2/2, Te2/3, Te2/4, Te2/5

                                                Te2/6, Te2/7, Te2/8

2    default_Data_Vlan                active

3    RZ1-nonServer_Vlan               active

9    snsmon                           active

10   VoIP                             active

20   DSL-ROUTER-EXTERN                active

23   Euras-RZ1                        active

24   Euras-Client-Transit             active

26   IP-Kameras                       active

32   Access_CC                        active

33   ACCESS_BUHA                      active

 

 

VLAN Name                             Status    Ports

---- -------------------------------- --------- -------------------------------

34   ACCESS_HALLE5                    active

35   Access_Halle4                    active

36   Access_Halle1                    active

37   Access_Halle3                    active

38   Access_RZ1                       active

39   Access_GM                        active

40   NH3+4                            active

66   Shop/Logistik                    active

67   Webfacing                        active

68   LotusMail                        active

95   DatabaseServer                   active

96   VMware-Netz                      active

97   Storage-Vlan                     active

98   Management-Vlan                  active

99   SERVER-RZ1                       active

100  bladetest                        active

101  WLAN_101_Scanner                 active

110  i5-HMC                           active

111  i5-HMC2                          active

120  Mysql_Replication                active

200  AP-WLC-Vlan                      active

500  DMZ                              active

501  Guest-Vlan                       active

 

 

VLAN Name                             Status    Ports

---- -------------------------------- --------- -------------------------------

510  DMZ2                             active

995  Shop_Cluster_Vlan                active

996  I-Series_Blade-Vlan              active

997  Blade_Management                 active

998  I5_SYNCLINK                      active

999  Euras_Transit                    active

1002 fddi-default                     act/unsup

1003 token-ring-default               act/unsup

1004 fddinet-default                  act/unsup

1005 trnet-default                    act/unsup

Tobias

The ip default-gateway command on the new switch should allow it to talk to the old switch L3 vlan interfaces. The docs for the 4500-X however are a little vague in terms of when you need to use a static route. Can you add this to your new switch and see if it changes anything -

ip route 0.0.0.0 0.0.0.0 10.98.0.254

Jon

YOU ARE MY HERO

It works now, all is working as it should be!

Many Thanks Jon!!

Hello

Would you please mark this discussion as correct and rate it so others may be able to benefit from the answer provided by JON

res

Please don't forget to rate any posts that have been helpful.

Thanks.


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Hi, 

You have seen an issue where the trunk will not form if one switch is in transparent and the other in Client? I am having an issue with a trunk forming across a metro ethernet connection. One of the switches is in transparent mode and the other client.

Review Cisco Networking for a $25 gift card