B3nt
asked on
VLAN configuration on a SG 300-52
I am both new to these forums as well as new to VLANs, so please take it easy on me ;)
I am attempting to configure 4 SG 300-52 Gigabit switches to accommodate 4 VLANs, and attach 4 WAP4410N AP's to that network. I have been able to create separate VLANs, but I can seem to configure a single line to carry multiple VLANs. I need this, because the APs are VLAN capable, but they only have one ethernet port. From what I am reading, that single port is called a trunk. But every time I configure a port to say, VLAN 10, then the uplink I am trying to use (on the management VLAN 1) no longer gives connectivity to that port. I am a systems engineer and great with servers, but obviously networking is still a mystery to me :) Can someone describe to me in detail how to configure this new Cisco branded interface (I can only find screenshots/instructions for the old Linksys model, which has changed), or point me to a easy to follow document? A simple configuration model to use for an explanation would be this: a single SG 300-52 switch with 24 ports on VLAN 10 and 24 ports on VLAN 20. Port 49 and 50 for uplink connectivity to two different gateways (one for each VLAN, we are two different companies sharing the same network devices), Port 51 goes out to the next switch and needs to carry both VLAN 10 and 20, and port 52 needs to go to the WAP, and carry both VLANs as well. The WAP has support for 4 VLANs and 4 SSIDs, btw.
Is this even possible? Do I have to stick with separate VLANs, each with their own input from router and output to the next switches same VLAN?
Part of the problem is I have trouble understanding why a port configured as a PVID/trunk on VLAN 1, and either tagged or untagged on VLAN 10, will not allow connectivity to ports set as PVID on VLAN and either tagged or untagged on VLAN 1. Also to further complicate the mix, I am confused by the Access/General/Trunk nomenclature used for the whole setup. Please help, we are moving to the new building next week, and I am pulling my hair out!
I am attempting to configure 4 SG 300-52 Gigabit switches to accommodate 4 VLANs, and attach 4 WAP4410N AP's to that network. I have been able to create separate VLANs, but I can seem to configure a single line to carry multiple VLANs. I need this, because the APs are VLAN capable, but they only have one ethernet port. From what I am reading, that single port is called a trunk. But every time I configure a port to say, VLAN 10, then the uplink I am trying to use (on the management VLAN 1) no longer gives connectivity to that port. I am a systems engineer and great with servers, but obviously networking is still a mystery to me :) Can someone describe to me in detail how to configure this new Cisco branded interface (I can only find screenshots/instructions for the old Linksys model, which has changed), or point me to a easy to follow document? A simple configuration model to use for an explanation would be this: a single SG 300-52 switch with 24 ports on VLAN 10 and 24 ports on VLAN 20. Port 49 and 50 for uplink connectivity to two different gateways (one for each VLAN, we are two different companies sharing the same network devices), Port 51 goes out to the next switch and needs to carry both VLAN 10 and 20, and port 52 needs to go to the WAP, and carry both VLANs as well. The WAP has support for 4 VLANs and 4 SSIDs, btw.
Is this even possible? Do I have to stick with separate VLANs, each with their own input from router and output to the next switches same VLAN?
Part of the problem is I have trouble understanding why a port configured as a PVID/trunk on VLAN 1, and either tagged or untagged on VLAN 10, will not allow connectivity to ports set as PVID on VLAN and either tagged or untagged on VLAN 1. Also to further complicate the mix, I am confused by the Access/General/Trunk nomenclature used for the whole setup. Please help, we are moving to the new building next week, and I am pulling my hair out!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This was great, but just a little bit of a 10,000 feet perspective... I needed more of a walkthrough, the theory I mostly undderstood, it was the implementation. Thanks anyways though, as I didn't make that clear initially.
ASKER