Unsolved
This post is more than 5 years old
2 Intern
•
126 Posts
0
27910
PowerConnect 2748 VLAN Routing
I have two 2748 switches. One sits in the server rack, one is connected to all the workstation connections.
I'm using 192.168.1.x internally on all workstations and servers.
I have defined VLAN 101 on both switches. on the workstation switch, ports 1-44 members and are marked untagged. ports 45-48 are assigned to LAG 1. LAG 1 is a member and marked untagged.
On the server switch, ports 1-38 are members of VLAN101 and marked untagged. ports 45-58 are assigned to LAG1, a member and marked untagged. ports 39-44 are assigned to VLAN 100 and marked untagged.
VLAN 101 handles all 192.168,1.x traffic.
LAG 1 connects the two switches to increase switch-to-switch bandwidth.
VLAN 100 on the server switch is used for internet traffic 173.10.121.xxx. Normally i'd go from wall to modem to firewall/router to switch. but due to lab geography, I"m connecting the modem and public side of the router ton the VLAN 100 set of ports. i keep the other ports available in case i need to connect a workstation/laptop outside the firewall (and assign it an IP address in the 137.10.122.xxx static range).
Here's the thing, when one of the users of such a workstation was finished, they set the configuration from static back to DHCP, but forgot to disconnect it from VLAN 100. Since the only DHCP server exists on the VLAN 101 (192.168.1.x) network, I would have expected workstation to fail to obtain an address, but to my dismay it did, in the 192.168.1.x range.
Is this something that i can simply solve by changing the interface ports from untagged to tagged? and would i need to do this on both switches, or just the one with the two VLAN's?
Or, based on some VLAN advice i've gotten, i need to turn off inter VLAN routing? but I don't know how to do that on a 2748. If this is the solution can someone help me out?
THanks
piotr_m
11 Posts
0
November 7th, 2011 04:00
PC2748 doesn't support inter vlan routing at all.
JSWhicker
31 Posts
1
November 7th, 2011 08:00
This makes me wonder what the PVID(vlan>port settings) is set to on the port that the DHCP server is connected to. I suspect that the PVID is set to 100 and not 101. If the port has a "U" for vlan 101 in the vlan membership but under the port setting the PVID is set to 100, Then for all practical purposes, The port is in vlan 100. PVID= the vlan that all untagged data packets go to.
beekerc
2 Intern
2 Intern
•
126 Posts
0
November 12th, 2011 02:00
if that's true, then I shouldn't have seen what I saw, there traffic on one VLAN was able to get onto another VLAN, the it's clear that both VLANs were visible via one port.
beekerc
2 Intern
2 Intern
•
126 Posts
0
November 12th, 2011 02:00
I see the pVID setting. does this mean that in order to truly isloate VLAN traffic I not only need to assign a port to a VLAN via VLAN membership, but also configure the matching PVID on the itnerface itself?
Does that also mean that i wanted to move a port from one VLAN to another, i not onlyh have to reassign it in VLAN membership, but also change the PVID directly on the port? kind of a pain it sounds like, but if that's the answer....
beekerc
2 Intern
2 Intern
•
126 Posts
0
February 21st, 2012 02:00
is there a way to do bulk PVID assignments?
I"m not keen on the idea of having to assign each interface by hand, especially after every 5th one or so, the "Apply Chagnes" button disappears and i have to logout then log back in again.
Thanks
studrick
1 Message
0
March 22nd, 2012 13:00
Ever get an answer to this??? I am needing some of the exact same things answered with PVID's and Tagging or Untagging.
beekerc
2 Intern
2 Intern
•
126 Posts
0
March 27th, 2024 19:30
@studrick no, can't say i ever got a clear answer