Lets look at some definitions about the different switchport modes available on the switch.
Trunk
Trunk Links attach two VLAN aware switches (or other VLAN aware devices) together and allows for multiple VLAN frames to cross one link. On VLAN trunk links, all frames must be tagged with the respective VLAN ID’s. The native VLAN must match on all switches in the segment. (VLAN 1 is default Native VLAN). The native VLAN is NOT tagged.
Access
Access Links connect VLAN unaware devices to the port of a VLAN-aware switch. All frames on access links are untagged.
The VLAN switch adds tags to received frames, and removes tags when transmitting frames. End users and VLAN-unaware workstations commonly reside on access links. By Default all ports are in ACCESS mode assigned to the default VLAN (VLAN 1). Ports set to Access mode belong to one VLAN only.
General
General Links consist of a combination of VLAN Trunk and Access Links. General Links can have both tagged and untagged frames, However, all frames sent to a specific VLAN must be tagged. All untagged frames are sent to the native VLAN. The native VLAN still applies to the General LINK. While it is possible to have multiple untagged vlans on a General link, you can only have ONE (1) PVID. The PVID represents the native VLAN. While untagged traffic may be sent via several untagged VLANs, returning untagged traffic will only be received by the PVID and therefore will NOT be forwarded to a specific VLAN.
In your case where you want ports 25-48 on a VLAN you would set the configuration on the ports like this:
console# config
console(config)# interface range gi1/0/25-47
console(config-if)# switchport mode access
console(config-if)# switchport access vlan X
console(config-if)#exit
console(config)# interface range gi1/0/1-24
console(config-if)# switchport mode access
console(config-if)# switchport access vlan X
Then on a single port gi1/0/48 set up a trunk for both VLANs
console(config-if)# switchport trunk allowed vlan add X
I would suggest setting up a different VLAN instead of 1 for the other VLAN. Then keep VLAN 1 as the native default VLAN. This set up will allow traffic coming into to port 1-24 to be tagged for VLAN 10. Traffic coming into port 25-47 to be tagged with VLAN X (your choice). Then all the VLANs will move across port 48 on the trunk to the Cisco device. The Cisco will need to be set up with the same VLANs and trunk on the connection.
another thing this does is mandates phone priority not network isolation. If I am just trying to seperate my phones from my data i.e. one gig port from vlan ports on the switch to a router port for the voice and a primary vlan link to a different router port and thoes 2 router ports are routing to different subnets and gateways, I'm doing a lot of un needed work to just seperate the 2 streams to different carriers. the oui section is a qos solution I could implement in a mixed environment but not really what I was asking to do.
my confusion with this is why am I adding mac addresses of every polycomm phone to the vlan and what about other ip devices like edgemark phone routers, or phone workstation computers, are they added as well? Then we put in interface mode trunk? I assume all the stuff on the phone network is isolated from the data network I will read more on the mac address issues, but they are totally different ip address ranges so I dont understand why the macs are needed. Thanks...
The traffic is filtered by the Mac address that is in the packets sent from the phone. The switch sees the Mac address and then matches it as traffic from a phone and places it into the Voice VLAN that is separate from the data traffic.
All VLANs are segregated until you have a router that can route between the VLANs.
The Voice VLAN also has some built in features that give priority to the Voice traffic over the data. This increases the quality of your phone conversations.
DELL-Willy M
802 Posts
1
April 2nd, 2013 17:00
Here is an example:
Console(config)# vlan data
Console(config-vlan)# vlan 10
Console(config-vlan)# exit
Console(config)# voice vlan id 10
Console(config)# voice vlan oui add xx:xx:xx:xx:xx:xx
Console(config)# int gi 1/0/1
Console(config-if)# switchport mode trunk
Console(config-if)# switchport trunk allowed vlan remove 10
Console(config-if)# voice vlan enable
Console(config-if)# end
Here is a Whitepaper for Configuring Dell PowerConnect 55xx series switch voice VLAN:
en.community.dell.com/.../configuring-dell-powerconnect-55xx-series-switch-voice-vlan.aspx
Page 557 of the CLI Guide starts the discussion for the Voice VLAN Commands on the 5500 switch.
http://downloads.dell.com/Pages/Manuals/powerconnect-5548.html
DELL-Willy M
802 Posts
1
April 3rd, 2013 14:00
Lets look at some definitions about the different switchport modes available on the switch.
Trunk
Trunk Links attach two VLAN aware switches (or other VLAN aware devices) together and allows for multiple VLAN frames to cross one link. On VLAN trunk links, all frames must be tagged with the respective VLAN ID’s. The native VLAN must match on all switches in the segment. (VLAN 1 is default Native VLAN). The native VLAN is NOT tagged.
Access
Access Links connect VLAN unaware devices to the port of a VLAN-aware switch. All frames on access links are untagged.
The VLAN switch adds tags to received frames, and removes tags when transmitting frames. End users and VLAN-unaware workstations commonly reside on access links. By Default all ports are in ACCESS mode assigned to the default VLAN (VLAN 1). Ports set to Access mode belong to one VLAN only.
General
General Links consist of a combination of VLAN Trunk and Access Links. General Links can have both tagged and untagged frames, However, all frames sent to a specific VLAN must be tagged. All untagged frames are sent to the native VLAN. The native VLAN still applies to the General LINK. While it is possible to have multiple untagged vlans on a General link, you can only have ONE (1) PVID. The PVID represents the native VLAN. While untagged traffic may be sent via several untagged VLANs, returning untagged traffic will only be received by the PVID and therefore will NOT be forwarded to a specific VLAN.
In your case where you want ports 25-48 on a VLAN you would set the configuration on the ports like this:
console# config
console(config)# interface range gi1/0/25-47
console(config-if)# switchport mode access
console(config-if)# switchport access vlan X
console(config-if)#exit
console(config)# interface range gi1/0/1-24
console(config-if)# switchport mode access
console(config-if)# switchport access vlan X
Then on a single port gi1/0/48 set up a trunk for both VLANs
console(config)# interface gi1/0/48
console(config-if)# switchport mode trunk
console(config-if)# switchport trunk allowed vlan add 10
console(config-if)# switchport trunk allowed vlan add X
I would suggest setting up a different VLAN instead of 1 for the other VLAN. Then keep VLAN 1 as the native default VLAN. This set up will allow traffic coming into to port 1-24 to be tagged for VLAN 10. Traffic coming into port 25-47 to be tagged with VLAN X (your choice). Then all the VLANs will move across port 48 on the trunk to the Cisco device. The Cisco will need to be set up with the same VLANs and trunk on the connection.
dolson80301
4 Posts
0
April 3rd, 2013 10:00
another thing this does is mandates phone priority not network isolation. If I am just trying to seperate my phones from my data i.e. one gig port from vlan ports on the switch to a router port for the voice and a primary vlan link to a different router port and thoes 2 router ports are routing to different subnets and gateways, I'm doing a lot of un needed work to just seperate the 2 streams to different carriers. the oui section is a qos solution I could implement in a mixed environment but not really what I was asking to do.
dolson80301
4 Posts
0
April 3rd, 2013 10:00
my confusion with this is why am I adding mac addresses of every polycomm phone to the vlan and what about other ip devices like edgemark phone routers, or phone workstation computers, are they added as well? Then we put in interface mode trunk? I assume all the stuff on the phone network is isolated from the data network I will read more on the mac address issues, but they are totally different ip address ranges so I dont understand why the macs are needed. Thanks...
DELL-Willy M
802 Posts
1
April 3rd, 2013 11:00
The traffic is filtered by the Mac address that is in the packets sent from the phone. The switch sees the Mac address and then matches it as traffic from a phone and places it into the Voice VLAN that is separate from the data traffic.
All VLANs are segregated until you have a router that can route between the VLANs.
The Voice VLAN also has some built in features that give priority to the Voice traffic over the data. This increases the quality of your phone conversations.
dolson80301
4 Posts
0
April 3rd, 2013 13:00
I understand what you are saying but using phones I guess was a bad example so lets forget about phones.
I have switches witn 2 gig uplinks and 48 10/100/100 gig eithernet ports
I want one uplink to be the main vlan 1 and ports 25-48 to be on ip 172.16.4.x attached to cisco router port GE1/0/0
i want the other uplink port on vlan 10 with ports 1-24 to be on ip 172.16.14.x attached to cisco router port GE1/0/1
The router will decide where the traffic goes. this should be the very simplist configuration.
do I really need trunks oui etc.for this segragation?
I promise this is the last iteration of this question.