I have a new Powerconnect 3048 Switch. I need each port (from port 1 to 30) as independent vlan. That is... total 30 VLans I have done like so, but i am not able to access the common gateway which is connected to port number 45. or in other words... i need port 45 to be used by all the VLANS where the router is connected.
The technology you are attempting to configure is commonly referred to "Port Overlapping". Implementing this technology is not a recommended configuration due to the consumption of the networking device's resources unnecessarily.
The configuration requires that each interface is configured as an untagged member for (2) VLANs -- the individual VLAN and a "shared" VLAN. The PVID will correspond to the individual VLAN ID as outlined in the following table:
This configuration results in a significant impact on performance due to the nature of Layer 2 switching. Ultimately, ALL frames from any interface are flooded to every active interface. Thus, the unit will no longer switch traffic, but instead flood each frame -- converting the PowerConnect switch into a hub.
The recommended method to implement inter-VLAN routing is to utilize a Layer 3 device capable of receiving IEEE 802.1Q tagged frames. As such, each interface would be configured in only a single VLAN and the Layer 3 device would be responsible for routing each VLAN to the internet and also prohibiting inter-VLAN communication. However, it is understood that with additional hardware comes additional cost, which is not always a viable option.
Sorry for bringing back an old post, but I'm interested to know how the Layer 3 switch (6024) will be configured. Will there be tagging and trunking involved?
Would anyone mind showing a quick outline of how Jojes would setup his network since I'm basically looking at the exact same setup with not much experience in Layer 3 routing.
Configuring a VLAN is quite simple. Basically you need to connect the switch to a desktop using the console cable. Provide an IP address, Subnet and Gateway. Then enable the SNMP with a community string. By default, all the ports are aggregated to VLAN1. Once an IP is assigned to the switch, the simple way is you can go to the internet explorer and type the Address of the switch.
Take the VLAN configuration -> add new VLAN. Give the VLAN name and Vlan ID. Before adding the ports to the VLAN Group, remove that port from other group, also change the VLAN ID too.
DELL-Randy
132 Posts
328
0
Posted January 30th, 2006 20:00
The technology you are attempting to configure is commonly referred to "Port Overlapping". Implementing this technology is not a recommended configuration due to the consumption of the networking device's resources unnecessarily.
The configuration requires that each interface is configured as an untagged member for (2) VLANs -- the individual VLAN and a "shared" VLAN. The PVID will correspond to the individual VLAN ID as outlined in the following table:
Int VLAN ID PVID
1 1,45 1
2 2,45 2
3 3,45 3
4 4,45 4
5 5,45 5
...
43 43,45 43
44 44,45 44
45 45 45
This configuration results in a significant impact on performance due to the nature of Layer 2 switching. Ultimately, ALL frames from any interface are flooded to every active interface. Thus, the unit will no longer switch traffic, but instead flood each frame -- converting the PowerConnect switch into a hub.
The recommended method to implement inter-VLAN routing is to utilize a Layer 3 device capable of receiving IEEE 802.1Q tagged frames. As such, each interface would be configured in only a single VLAN and the Layer 3 device would be responsible for routing each VLAN to the internet and also prohibiting inter-VLAN communication. However, it is understood that with additional hardware comes additional cost, which is not always a viable option.