• February 09, 2012, 12:33:39 PM
Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic: DATA and Voice VLANS  (Read 1546 times)

0 Members and 1 Guest are viewing this topic.

Offline Akhan

  • Rookie
  • **
  • Posts: 2
DATA and Voice VLANS
« on: June 09, 2010, 09:40:16 AM »

Hi

 
switch 3650g - 24 ports

 
configuration

port 1 is data VLAN uplink from HP3500 router

port 2 is voice VLAN uplink from HP3500 router

 
 
ports 3-23 access ports with data 301 vlan  and voice 310 vlan respectively.

 
dhcp scope options set to get voice vlan 310 info from dhcp for the nortel ip phone

 
Nortel IP phone 1140E gets the correct ip address from 192.168.6.0 subnet

when using ip phone data port to connect a PC, PC is also getting the correct ip address from 172.16.8.0 subnet.

 
on cisco 3650 switch

when i run show int status

 
Nortel IP phone is connected to int 11 it shows VLAN 301 against that 

 
Gi0/1     DATA VLAN UPLINK   connected    301        a-full a-1000 10/100/1000BaseTX
Gi0/2     VOICE VLAN UPLINK  connected    310        a-full a-1000 10/100/1000BaseTX
Gi0/3     User Access Ports  notconnect   301          auto   auto 10/100/1000BaseTX
Gi0/4     User Access Ports  notconnect   301          auto   auto 10/100/1000BaseTX
Gi0/5     User Access Ports  notconnect   301          auto   auto 10/100/1000BaseTX
Gi0/6     User Access Ports  notconnect   301          auto   auto 10/100/1000BaseTX
Gi0/7     User Access Ports  notconnect   301          auto   auto 10/100/1000BaseTX
Gi0/8     User Access Ports  notconnect   301          auto   auto 10/100/1000BaseTX
Gi0/9     User Access Ports  notconnect   301          auto   auto 10/100/1000BaseTX
Gi0/10    User Access Ports  notconnect   301          auto   auto 10/100/1000BaseTX
Gi0/11    User Access Ports  connected    301        a-full a-1000 10/100/1000BaseTX

 
 
is this correct or it should be VLAN 310 on int 11

 
Please advise

 
Thanks

Asif


Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 2157
    • Michael McNamara
Re: DATA and Voice VLANS
« Reply #1 on: June 11, 2010, 09:37:08 PM »
Hi Akhan,

There's a little background necessary here to difference Nortel/Avaya and Cisco terminology.

On a Nortel/Avaya switch I would tell you that you need to set the port to Trunk/UnTagPVIDOnly and you need to set the PVID to the data VLAN (310 in your case).

On a Cisco switch I would tell you that you need to set the port to Trunk and set the native VLAN to the data VLAN (310 in your case).

I'm not exactly sure about the output you reference below because I don't have a Cisco switch accessible right now from home.

Let me know if that helps.

Good Luck!
If you've found this site useful and helpful, please help me spread the word. Link to us in your blog or homepage or Tweet about us! - Thanks!

Offline Matt

  • Rookie
  • **
  • Posts: 13
Re: DATA and Voice VLANS
« Reply #2 on: June 24, 2010, 04:44:59 PM »
Hi

The output from the show int status is correct in that it will show the data vlan for all access ports.

I would expect your access port config to have two statements such as the following:
switchport access vlan 301
switchport voice vlan 310

The data vlan is considered the native vlan - by default - for the port and that is what shows in the output. The voice vlan will still work of course, which is what you are seeing. For ports where you have only a phone plugged in you could set the native vlan to 310. Its not something I have ever tried

Offline NET-GURU

  • Rookie
  • **
  • Posts: 1
Re: DATA and Voice VLANS
« Reply #3 on: August 29, 2011, 03:13:19 PM »
Hi

What I would have done is this :

Set up your management vlan(MGMT-VLAN) first of all

Then on your uplink ports 1 and 2

interface FastEthernet0/1
 switchport access vlan 301
 switchport mode access 

interface FastEthernet0/3-23
 switchport trunk encapsulation dot1q
 switchport trunk native vlan (MGMT-VLAN)
 switchport trunk allowed vlan  310,310
 switchport mode trunk

Give that a go, and do a "show mac address-table infa0/3-23" to see what the devices are coming through on.

cheers

 

Offline gplante

  • Rookie
  • **
  • Posts: 3
Re: DATA and Voice VLANS
« Reply #4 on: September 15, 2011, 03:33:32 PM »
I have worked with a similar situation, Cisco switches with Notrel/Avaya IP Phones.

We commonly use IP Phone 1220's.  We found that relying on the the DHCP scope options to get the voice vlan number was not reliable. Could fat finger the scope options.

Depending on the IOS on your 3560 it may support LLDP, the IEEE version of CDP. The Nortel/Avaya phone are capable of talking LLDP and can get the voice vlan information from the switch.

Switch port config we are using:
 switchport access vlan 500
 switchport mode access
 switchport voice vlan 700

to enable LLDP add the following to Global config:
lldp run

it works just like CDP:

3560-a#sh lldp nei
Capability codes:
    (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
    (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other

Device ID           Local Intf     Hold-time  Capability      Port ID
10.11.1.43          Fa0/9          180        B,T             0024.b564.675c
10.11.1.44          Fa0/10         180        B,T             0024.b564.7c2d
10.11.1.42          Fa0/11         180        B,T             0024.b564.6794


Hope that helps,

Greg

Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 2157
    • Michael McNamara
Re: DATA and Voice VLANS
« Reply #5 on: September 15, 2011, 07:35:27 PM »
Hi Greg and welcome to the forums!

Thanks for sharing that information!

I believe you need to be running UNIStim 4.1 (062AC7J)  or later on the Avaya/Nortel IP phones for them to support LLDP VLAN assignment.

Cheers!
If you've found this site useful and helpful, please help me spread the word. Link to us in your blog or homepage or Tweet about us! - Thanks!

Offline gplante

  • Rookie
  • **
  • Posts: 3
Re: DATA and Voice VLANS
« Reply #6 on: September 19, 2011, 10:01:28 AM »
Thanks,

You are correct on that one, most of our phone are less than 2 years old. But we did have to go thur and upgrade some of our older phones.

Greg