ProCurve / ProVision-Based
cancel
Showing results for 
Search instead for 
Did you mean: 

3500 Switch VLAN retagging or Translation

Branden23
Occasional Contributor

3500 Switch VLAN retagging or Translation

I am having an issue with my 3500 switch.   I have seen a few different configuration using access ports or whatever but I am not finding anything in the configuration of the 3500 that allows anything like this. 

I have a switch that I do not have access to.  I connected a network cable from the switch that I do not have access to, to my 3500 switch.  Everything that is coming across that switch is coming across as untagged VLAN1.  

The problem is that my regular network runs on VLAN1 and I need to isolate the traffic coming from the switch to a new VLAN that I have created.   Is there a way to retag or translate all the packets coming from the switch I don't have access to from VLAN1 - VLANXXX?

6 REPLIES
Vince-Whirlwind
Honored Contributor

Re: 3500 Switch VLAN retagging or Translation

Yes, on the 3500 switchport that is the uplink to the switch you don't have access to, configure that switchport to be untagged in VLANXXX.

Branden23
Occasional Contributor

Re: 3500 Switch VLAN retagging or Translation

And that is all I have to do to remove the VLAN1 tag?   That is what is causing the problem... it is making it all the way around the mesh network because it is part of  VLAN 1.

As I am writing this I am thinking I may be incorrect in my approach.   But basically I want to remove an way for the packet to traverse the network via VLAN 1 which is what my standard network traffic is on.  

It is working currently on untagged VLAN 1 tagged VLANXXX.   I want to make sure it is not accessible at all from any device on VLAN 1.

 

Thanks 

Vince-Whirlwind
Honored Contributor

Re: 3500 Switch VLAN retagging or Translation

I'm confused.

First you say, "Everything that is coming across that switch is coming across as untagged VLAN1. "

Now you say, "And that is all I have to do to remove the VLAN1 tag".

Please make your mind up: is it tagged or untagged?

Branden23
Occasional Contributor

Re: 3500 Switch VLAN retagging or Translation

Too many things going on all at once... Hopefully I can clarify.    Thank you for your time. 

I have attached a picture..... What I did was I pulled a computer from the switch I don't have access to (Switch A) and I moved the computer to a remote site.   I connected Switch A to the 3500 Switch (Switch B) and set it to Tagged VLAN 300 and by default it was untagged VLAN 1.  By virtue of Switch B being a MESH member it is tagged VLAN 1 and 300 through the MESH but I did not configure the HP 1500 Series switch (Switch C) at all and was a little surprised when I plugged the computer into Switch C and it just started working.   

My concern is that there is overlap between our regular network traffic and the traffic I was attempting to isolate to VLAN 300.  I set port 24 to be No VLAN 1 and that broke everything.   Thinking about it now I am wondering if it would just work it I went ahead and configured VLAN 300 through the rest of the network.   I am just making sure to do my due dilligence because this is part of a 911 system and I don't want ANYTHING else on that network.  

Switches.jpg

Vince-Whirlwind
Honored Contributor

Re: 3500 Switch VLAN retagging or Translation

OK, so port24 on Switch B needs to be untagged in VLAN300.

Then, if you have something on Switch C that needs to be in the same network as the things on Switch A, then configure its port to be untagged in VLAN300.

Then, you need to make sure you have VLAN300 tagged on the inter-switch links.

Branden23
Occasional Contributor

Re: 3500 Switch VLAN retagging or Translation

I will give that a try!  Thank you!