cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4332
Views
14
Helpful
27
Replies

Attempting to trunk a 2924xl to a 3550

acameron12
Level 1
Level 1

I have a 3550 and 2924xl switch I want to trunk together but am unsuccefule thus far:

The 3550 is as follows:

Model number: WS-C3550-24-EMI

System image file is "flash:c3550-i5q3l2-mz.121-14.EA1a/c3550-i5q3l2-mz.121-14.EA1a.bin

cisco WS-C3550-24 (PowerPC) processor (revision K0) with 65526K/8192K bytes of memory.

The 2924 is as follows:

Model number: WS-C2924-XL-A

System image file is "flash:c2900XL-h2-mz-112.8.2-SA6.bin", booted via administrator on vty0 (172.16.204.213)

cisco WS-C2924-XL (PowerPC403GA) processor (revision 0x11) with 8192K/1024K bytes of memory.

With the 2924XL access port set to access, I can access it. Setup in multi mode with vlans permitted from the 3550, I cannot.

My objective is to offload a Nortel switch currenlty trunked from my 3550 and shit the hosts on the Nortel to the 2924 XL on a similarly trunked port.

Is what I am attempting even possible with these two versions of Catalysts?

9 Accepted Solutions

Accepted Solutions

Giuseppe Larosa
Hall of Fame
Hall of Fame

Hello Acameron12,

>> With the 2924XL access port set to  access, I can access it. Setup in multi mode with vlans permitted from  the 3550, I cannot.

this does not mean that the two devices are not building a trunk correctly but it may mean there is a problem with the vlan where the management interface of 2924XL exists.

you should take on both devices (if you can reach the C2924XL with a console connection)

sh interface type 0/y switchport

where type 0/y stands for the port name for example fas 0/23

in this way it is possible to see some of the trunk parameters including encapsulation protocol and native vlan settings

Connecting two ports configured as access ports may solve a native vlan mismatch, or it can join two different broadcast domains

Once a trunk is setup frames sent to C2924 XL management IP address are tagged with a vlan number that may be different from that expected on the C2924 XL making it unreachable.

Hope to help

Giuseppe

View solution in original post

Hello Acameron12,

the key message is:

>> Received 802.1Q BPDU on  non 802.1Q trunk FastEthernet0/24 on vlan 300.

the C2924XL may be supporting only ISL trunks, try to use encapsulation isl on the C3550 side

as noted in first post

sh interface fas0/24 switchport should confirm this.

some of older low end switches support only ISL, other ones like C2950 support only 802.1Q

Hope to help

Giuseppe

View solution in original post

Hello Acameron12,

do you see that the list of permitted vlans is different on the two sides?

>>switchport multi vlan  1,300,302,303,396-398

>> switchport trunk allowed vlan  300,302,303,396-398

on C3550 do:

int fas0/4

switchport trunk allowed vlan add 1

Hope to help

Giuseppe

View solution in original post

Can you post the configuration of VLAN 302 of both 2900 and 3550?

Try the following commands on the trunk links for both switches:

switchport mode trunk
switchport trunk encap dot1q
switchport trunk allowed vlan 1,300,302,303,396-398

Get rid of the storm control statement on a trunk link.  Put the this statement on access ports.

Can you also post the output of the "sh ip int brief" on the 2900?  Maybe you have multiple VLANs and, because the 2900 will only allow ONE active VLAN, VLAN 302 is shutdown in favour of other VLAN.

View solution in original post

"no such file or directory"

The file "c2900XL-h2-mz-112.8.2-SA6.bin" is missing.  Do the following at the "switch:" prompt:

1.  flash_init
2.  load_helper
3.  dir flash:

You should see a file with a .bin filename.  If you do, type the command "boot .bin".

When you have successfully loaded the IOS, go into configuration mode and type the following command "no boo system" and save the config. 

I am suspecting that you have loaded a new IOS but forgot to change the boot parameters.

View solution in original post

Yes, that's the image mine had on it.

System image file is "flash:c2900xl-c3h2s-mz.120-5.WC17.bin"

If you have console access, I'd just set up a tftp server on your laptop and grab the new image from there.  You'll probably have to delete the current image from flash before doing so due to space restrictions.

View solution in original post

The 2900Xl will only allow ONE IOS.  There's not enough flash space for two.

View solution in original post

  You can get rid of the diag image , its just there for factory troubleshooting and has no function in everyday usage .  Use the 12.X image . It is the right image for the box , just verify the size in flash matches the size of the file you downloaded from CCO.   Then make sure you do the boot statement , "boot system flash:c2900xl-c3h2s-mz.120-5.WC17.bin .  Write mem the config and reload .   For your trunk setup make sure both are using dot1q for the encapsulation ,  early versions of the 2924 used ISL as a default I believe.

View solution in original post

If your troubles have been addressed, may I request if you can mark this post as "Answered" and rate our posts?  Thank you very much.

View solution in original post

27 Replies 27

Giuseppe Larosa
Hall of Fame
Hall of Fame

Hello Acameron12,

>> With the 2924XL access port set to  access, I can access it. Setup in multi mode with vlans permitted from  the 3550, I cannot.

this does not mean that the two devices are not building a trunk correctly but it may mean there is a problem with the vlan where the management interface of 2924XL exists.

you should take on both devices (if you can reach the C2924XL with a console connection)

sh interface type 0/y switchport

where type 0/y stands for the port name for example fas 0/23

in this way it is possible to see some of the trunk parameters including encapsulation protocol and native vlan settings

Connecting two ports configured as access ports may solve a native vlan mismatch, or it can join two different broadcast domains

Once a trunk is setup frames sent to C2924 XL management IP address are tagged with a vlan number that may be different from that expected on the C2924 XL making it unreachable.

Hope to help

Giuseppe

I do have console access to the 2924 to make configuration changes and IP access to the 3550.

To clarify, I made the following updates to my 2924:

interface FastEthernet0/24                                                     
switchport multi vlan 1,300,302,303,396-398                                   
switchport mode multi

On my 3550:

interface FastEthernet0/4
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300,302,303,396-398
switchport mode trunk
storm-control broadcast level 1.00

When I set the 3550 side of the connection, my 2924 reports:

%SPANTREE-2-RECV_1Q_NON_1QTRUNK:                                               
Received 802.1Q BPDU on non 802.1Q trunk FastEthernet0/24 on vlan 1.           
%SPANTREE-2-BLOCK_PORT_TYPE: Blocking FastEthernet0/24 on vlan 1.              
Inconsistent port type.                                                        
%SPANTREE-2-BLOCK_PVID_PEER: Blocking FastEthernet0/24 on vlan 302.            
Inconsistent peer vlan.                                                        
%SPANTREE-2-BLOCK_PVID_LOCAL: Blocking FastEthernet0/24 on vlan 1.             
Inconsistent local vlan.                                                       
%SPANTREE-2-RECV_1Q_NON_1QTRUNK:                                               
Received 802.1Q BPDU on non 802.1Q trunk FastEthernet0/24 on vlan 300.         
%SPANTREE-2-BLOCK_PORT_TYPE: Blocking FastEthernet0/24 on vlan 300.            
Inconsistent port type.                                                        
%SPANTREE-2-BLOCK_PVID_LOCAL: Blocking FastEthernet0/24 on vlan 300.           
Inconsistent local vlan.                                                       
%SPANTREE-2-BLOCK_PORT_TYPE: Blocking FastEthernet0/24 on vlan 302.            
Inconsistent port type.                                                        
%SPANTREE-2-RECV_1Q_NON_1QTRUNK:                                               
Received 802.1Q BPDU on non 802.1Q trunk FastEthernet0/24 on vlan 303.         
%SPANTREE-2-BLOCK_PORT_TYPE: Blocking FastEthernet0/24 on vlan 303.            
Inconsistent port type.                                                        
%SPANTREE-2-BLOCK_.PVID_LOCAL: Blocking FastEthernet0/24 on vlan 303.          
Inconsistent local vlan.                                                       
%SPANTREE-2-RECV_1Q_NON_1QTRUNK:                                               
Received 802.1Q BPDU on non 802.1Q trunk FastEthernet0/24 on vlan 396.         
%SPANTREE-2-BLOCK_PORT_TYPE: Blocking FastEthernet0/24 on vlan 396.            
Inconsistent port type.                                                        
%SPANTREE-2-BLOCK_PVID_LOCAL: Blocking FastEthernet0/24 on vlan 396.           
Inconsistent local vlan.                                                       
%SPANTREE-2-RECV_1Q_NON_1QTRUNK:                                               
Received 802.1Q BPDU on non 802.1Q trunk FastEthernet0/24 on vlan 397.         
%SPANTREE-2-BLOCK_PORT_TYPE: Blocking FastEthernet0/24 on vlan 397.            
Inconsistent port type.                                                        
%SPANTREE-2-BLOCK_PVID_LOCAL: Blocking FastEthernet0/24 on vlan 397.           
Inconsistent local vlan.                                                       
%SPANTREE-2-RECV_1Q_NON_1QTRUNK:                                               
Received 802.1Q BPDU on non 802.1Q trunk FastEthernet0/24 on vlan 398.         
%SPANTREE-2-BLOCK_PORT_TYPE: Blocking FastEthernet0/24 on vlan 398.            
Inconsistent port type.                                                        
%SPANTREE-2-BLOCK_PVID_LOCAL: Blocking FastEthernet0/24 on vlan 398.           
Inconsistent local vlan.....

Hello Acameron12,

the key message is:

>> Received 802.1Q BPDU on  non 802.1Q trunk FastEthernet0/24 on vlan 300.

the C2924XL may be supporting only ISL trunks, try to use encapsulation isl on the C3550 side

as noted in first post

sh interface fas0/24 switchport should confirm this.

some of older low end switches support only ISL, other ones like C2950 support only 802.1Q

Hope to help

Giuseppe

I set the 2924 as:

interface FastEthernet0/24                                                     
switchport multi vlan 1,300,302,303,396-398                                   
switchport mode multi

I set my 3550 as:

interface FastEthernet0/4
switchport trunk encapsulation isl
switchport trunk allowed vlan 300,302,303,396-398
switchport mode trunk

storm-control broadcast level 1.00

Still no luck.

Although the 2924 reported no errors.

I can ping my local vlan interface on 2924, but cannot ping across to the 3550.

Hello Acameron12,

do you see that the list of permitted vlans is different on the two sides?

>>switchport multi vlan  1,300,302,303,396-398

>> switchport trunk allowed vlan  300,302,303,396-398

on C3550 do:

int fas0/4

switchport trunk allowed vlan add 1

Hope to help

Giuseppe

Hello Guiseppe,

          I updated the 3550 side as suggested:


!
interface FastEthernet0/4
switchport trunk encapsulation isl
switchport trunk allowed vlan 1,300,302,303,396-398
switchport mode trunk
storm-control broadcast level 1.00

Still no response frmo the 2924 on a ping request to the VLAN 302 interface:

ping 172.16.200.188

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.200.188, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

Can you post the configuration of VLAN 302 of both 2900 and 3550?

Try the following commands on the trunk links for both switches:

switchport mode trunk
switchport trunk encap dot1q
switchport trunk allowed vlan 1,300,302,303,396-398

Get rid of the storm control statement on a trunk link.  Put the this statement on access ports.

Can you also post the output of the "sh ip int brief" on the 2900?  Maybe you have multiple VLANs and, because the 2900 will only allow ONE active VLAN, VLAN 302 is shutdown in favour of other VLAN.

My 3550 port definition presently looks as follows:

interface FastEthernet0/4
switchport trunk encapsulation isl
switchport trunk allowed vlan 1,300,302,303,396-398
switchport mode trunk

Still no access to the address of the 2924 (172.16.200.188) from the 3550 or in the other direction to the 3550's VLAN 302 interface (172.16.200.129). Although I can still pnig the 2924's local port from the console.

See below:

BDC-UNI-INF-SW-G>sh ip int brief

Interface IP-Address OK? Method Status Protocol

VLAN1 unassigned YES unset up up

VLAN302 172.16.200.188 YES NVRAM up up

FastEthernet0/1 unassigned YES unset down down

FastEthernet0/2 unassigned YES unset down down

FastEthernet0/3 unassigned YES unset down down

FastEthernet0/4 unassigned YES unset down down

FastEthernet0/5 unassigned YES unset down down

FastEthernet0/6 unassigned YES unset down down

FastEthernet0/7 unassigned YES unset down down

FastEthernet0/8 unassigned YES unset down down

FastEthernet0/9 unassigned YES unset down down

FastEthernet0/10 unassigned YES unset down down

FastEthernet0/11 unassigned YES unset down down

FastEthernet0/12 unassigned YES unset down down

FastEthernet0/13 unassigned YES unset down down

FastEthernet0/14 unassigned YES unset down down

FastEthernet0/15 unassigned YES unset down down

FastEthernet0/16 unassigned YES unset down down

FastEthernet0/17 unassigned YES unset down down

FastEthernet0/18 unassigned YES unset down down

FastEthernet0/19 unassigned YES unset down down

FastEthernet0/20 unassigned YES unset down down

FastEthernet0/21 unassigned YES unset down down

FastEthernet0/22 unassigned YES unset down down

FastEthernet0/23 unassigned YES unset down down

FastEthernet0/24 unassigned YES unset up up

BDC-UNI-INF-SW-G>

jjalexander401
Level 1
Level 1

I  recently set up a trunk between a 2924xl and 2950.  here is my sample config:

2950:

interface FastEthernet0/24
description dot1q trunk link to Lamson (S2 2924) on port fa0/23
switchport trunk native vlan 70
switchport trunk allowed vlan 10,20,30,70
switchport mode trunk

2924:

interface FastEthernet0/23
description dot1q trunk link to Rio (S1 2950) on port fa0/24
switchport trunk encapsulation dot1q
switchport trunk native vlan 70
switchport trunk allowed vlan 1,10,20,30,70,1002-1005
switchport mode trunk

The 2924 automatically adds 1 and 1002-1005 vlans as allowed.  I couldn't remove them.  I also had to declare vlan 70 as management on the 2924xl, by going to the interface and typing 'management'

hope that helps.

   Follow jjalexander's config.  Switchport multi setup is not the same as a normal trunk .  It was something cisco used early on on the 2924's to  try and runn mutliple vlans  before  trunking became a standard . If your switch won't take the normal trunking configs then you may have to upgrade the code to 12.X code .   I know the 3550 does not support multi vlan mode.

http://www.cisco.com/en/US/partner/docs/switches/lan/catalyst2900xl_3500xl/release12.0_5_wc5/swg/swvlan.html#wp1030092

I was worried about that when I embarked on this task. I have a copy of the image:

c2900xl-c3h2s-mz.120-5.WC17.bin

Which I downloaded just in case.

I will revert to the original configuration via access rather than trunking from the 3550 and retry subsequent to an image upgrade.

Thanks for the insights.

I attempted a reload with a new image, but failed.

Xmodem file system is available.                                               
Initializing Flash...                                                          
flashfs[0]: 173 files, 4 directories                                           
flashfs[0]: 0 orphaned files, 0 orphaned directories                           
flashfs[0]: Total bytes: 3612672                                               
flashfs[0]: Bytes used: 3528704                                                
flashfs[0]: Bytes available: 83968                                             
flashfs[0]: flashfs fsck took 8 seconds.                                       
...done Initializing Flash.                                                    
Boot Sector Filesystem (bs:) installed, fsid: 3                                
Parameter Block Filesystem (pb:) installed, fsid: 4                            
Loading "flash:c2900XL-h2-mz-112.8.2-SA6.bin"...flash:c2900XL-h2-mz-112.8.2-SA6.
bin: no such file or directory                                                 
                                                                               
Error loading "flash:c2900XL-h2-mz-112.8.2-SA6.bin"                            
                                                                               
Interrupt within 5 seconds to abort boot process.                              
Boot process failed...                                                         
                                                                               
The system is unable to boot automatically.  The BOOT                          
environment variable needs to be set to a bootable                             
image.                                                                         
                                                                               
switch:

Perhasps I have exceeded the capabilities of this 2924 switch given the environment (paired with a 3550)?

"no such file or directory"

The file "c2900XL-h2-mz-112.8.2-SA6.bin" is missing.  Do the following at the "switch:" prompt:

1.  flash_init
2.  load_helper
3.  dir flash:

You should see a file with a .bin filename.  If you do, type the command "boot .bin".

When you have successfully loaded the IOS, go into configuration mode and type the following command "no boo system" and save the config. 

I am suspecting that you have loaded a new IOS but forgot to change the boot parameters.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: