PowerConnect 2724 trunking to PowerConnect 5324

There is no trunk mode on the 2724; you   place the port or ports in the trunk into all of the VLANs as tagged ports.

 

There is no CLI on the 27xx family of switches, its web managed only.

Once I set my trunk port on the 5324 to tagged, I can no longer communicate with the 2724.  Here is the config:

 

5324:

port 10 - vlan port mode is TRUNK

 

2724

port 3 - PVID is 1169 and set as TAGGED

 

when 5324 port 10 is set to UNTAGGED, I can communicate with the 2724

as soon as port 10 is set to TAGGED, I lose communication.

 

Any suggestions?  We have many 5324's and 3424's set up with trunks to each other as well as other Extreme Networks switches without issue.

 

I assume by communicate with the 2724 you are referring to the management interface? I think the reason you are seeing this problem is the management interface on the 2724 is bound to vlan 1, which you cant tag. So you would need to allow vlan 1 to pass over your trunk untagged and make sure your 5324 is setup for admit all on the trunk.

Well the issue really comes from the 2724 side of things. With the management interface being bound to vlan 1 you dont really have any other choice that to use vlan 1 for management. But since vlan 1 isnt allowed to be tagged on the switch the only means of passing it across a trunk is untagged. So you would have setup the switch on the otherside of the trunk to allow untagged packets and associate vlan 1 untagged on its port as well (PVID of 1). This may seem like an odd way to do things, but its one of the limitations of a web managed switch. Most of the other powerconnet switches with a console port allow you to specifiy the management vlan.

 

This odd setup can be made to work as long as you have all other traffic/ports on the switch's on  different vlan's (not 1).

 

 

Can you please explain that a bit more? I have the same issue

Thank you

Alex

i am pretty sure it can be done. You may have to run the port in hybrid mode to be able to assign a PVID.

 

Thank you for your reply. My other side is 3448. I think I know how to allow untagged packets on the trunk link, but I am not sure about associating port with PVID 1. Are you talking about trunk port on 3448? Can that be done?

Yes that worked. All I had to do is to pick management port on 2716 (VLAN1 untagged) and to set trunk on 2716 side to Admit All and PVID=1. Didn't need to do anything extra on 3448.

 

Because management VLAN has to be 1 on 2716, I am wondering if I should select VLAN1 as main data VLAN, so that I can do switches administration from any PC. What do you think about this?

 

Thank you

Alex

It all depends on the network. If you dont want the actual data users on the switch to even see the management interface(potential security risk) that you way your described will work. I personally always like locking down the GUI's to a specific vlan i control access to.