VLAN Configuration on HP Procurve Switch
STR1302
Posted messages
13
Status
Member
-
brupala Posted messages 111108 Registration date Status Member Last intervention -
brupala Posted messages 111108 Registration date Status Member Last intervention -
Hello,
actually, I am preparing a new VLAN architecture for my company; and right now I am stuck when configuring tagged ports on my HP Procurve 2510 switches (Layer 2). According to my knowledge, for Tagged VLANs to work, it is necessary to configure sub-interfaces (like on Cisco) on the cascading port of Layer 3 switches (to ensure routing between the different VLANs)
initially, in order to test the VLANs, I connected each VLAN from my Layer 2 switch to the Layer 3 switch and it worked perfectly. But when I wanted to replace those cables with a more technical solution (Trunk Port), everything got disconnected.
my problem is that I cannot configure sub-interfaces for the ports of the HP 2610 switch (Layer 3). Can you please help me with this???
I know that on Cisco equipment it's easier, but the problem is that these devices were purchased before I joined the company
Heeeelp me
actually, I am preparing a new VLAN architecture for my company; and right now I am stuck when configuring tagged ports on my HP Procurve 2510 switches (Layer 2). According to my knowledge, for Tagged VLANs to work, it is necessary to configure sub-interfaces (like on Cisco) on the cascading port of Layer 3 switches (to ensure routing between the different VLANs)
initially, in order to test the VLANs, I connected each VLAN from my Layer 2 switch to the Layer 3 switch and it worked perfectly. But when I wanted to replace those cables with a more technical solution (Trunk Port), everything got disconnected.
my problem is that I cannot configure sub-interfaces for the ports of the HP 2610 switch (Layer 3). Can you please help me with this???
I know that on Cisco equipment it's easier, but the problem is that these devices were purchased before I joined the company
Heeeelp me
4 answers
I'm not familiar with HP equipment... my field is Cisco ;-) ... however, I think the general operation is similar.
If inter-VLAN routing is provided by a Layer 3 switch, there is no need to create sub-interfaces. However, on the Layer 3 switch, VLAN interfaces (SVIs) need to be created, which serve as a virtual access point in the VLAN for the "router" part of the Layer 3 switch.
The VLANs must therefore also be present on the Layer 3 switch.
The connection between the Layer 3 switch and the Layer 2 switch(es) should be a trunk. (The data is tagged as it passes over so that the switch on the other end can send it back into the correct VLANs).
I hope this helps to clarify things. However, I assume here that the operating principle of HP is broadly the same as that of Cisco.
If inter-VLAN routing is provided by a Layer 3 switch, there is no need to create sub-interfaces. However, on the Layer 3 switch, VLAN interfaces (SVIs) need to be created, which serve as a virtual access point in the VLAN for the "router" part of the Layer 3 switch.
The VLANs must therefore also be present on the Layer 3 switch.
The connection between the Layer 3 switch and the Layer 2 switch(es) should be a trunk. (The data is tagged as it passes over so that the switch on the other end can send it back into the correct VLANs).
I hope this helps to clarify things. However, I assume here that the operating principle of HP is broadly the same as that of Cisco.
At Cisco, as sdj79 said, the connection between the switch and the router is called a "trunk link," which is something different in most other brands :/
In your case, if in the VLAN you have "tag"/"tagged," it's these links; trunk links are the ability to reduce 4 physical outputs into one. So be careful ;)
In your case, if in the VLAN you have "tag"/"tagged," it's these links; trunk links are the ability to reduce 4 physical outputs into one. So be careful ;)
Thank you very much. If I remember correctly, for Cisco routing, we need to create sub-interfaces like "interface 0/1.1, interface 0/1.2..." to define the IP addresses of the VLANs that the main interface 0/1 will receive. Then, we just need to set up trunks on both ends.
Regarding the HP Level 3 switch, I couldn't do this. So, it won't be possible to tag VLANs even if I set the ports to "tagged." In any case, I have tested all tagging possibilities, but it didn't work.
Ummmm, I'm stuck. Thank you for your help.
Regarding the HP Level 3 switch, I couldn't do this. So, it won't be possible to tag VLANs even if I set the ports to "tagged." In any case, I have tested all tagging possibilities, but it didn't work.
Ummmm, I'm stuck. Thank you for your help.
