Nortel I2004 with on Cisco 3560 Switch

[tex52]

I have Nortel I2004 VoIP phones that I connected to a Cisco 3560 switch. I am running the voice on VLAN 200, in the phone config I have VLAN configuration set to Manual and to use VLAN 200. However the phone is also communicating on VLAN 10 which is my data network, I know this because it is recieving an IP address from my data network DHCP server which is on a seperate subnet. Any help is greatly appreciated! I have placed my switchport config below.

interface FastEthernet0/1
switchport trunk encapsulation dot1q
switchport trunk native vlan 10
switchport mode trunk
no ip address
mls qos trust cos
no mdix auto
spanning-tree portfast

 

[johnpoole]

i agree that it can reach the desired network, after all that's how you set it up, but for some reason it can reach the other vlan also. i wish i could help more,i just thought maybe a network tech could help way more then a voice tech. i sent your post to our network guy (jerk) and he said he couldn't add any thing that wasn't posted. but if i ask him anything he just walks off like he's way to sharp to speak.. pls do let us know what you find

john poole
bellsouth business
columbia,sc

 

[I2007]

Is the config posted above what you have on all ports?

Here is what I have on my cicso switch.

[COLOR=red]This is my trunk to other switches[/color]
interface FastEthernet0/1
 switchport trunk allowed vlan 223,230-234,254
 switchport mode trunk
 no ip address
 mls qos trust cos
!
[COLOR=red]Below is the ports where phone and pc are connected[/color]
interface FastEthernet0/2
 switchport trunk native vlan 230
 switchport trunk allowed vlan 223,230
 switchport mode trunk
 switchport voice vlan dot1p
 no ip address
 mls qos trust cos
 spanning-tree portfast
!
interface FastEthernet0/3
 switchport trunk native vlan 230
 switchport trunk allowed vlan 223,230
 switchport mode trunk
 switchport voice vlan dot1p
 no ip address
 mls qos trust cos
 spanning-tree portfast
!
interface FastEthernet0/4
 switchport trunk native vlan 230
 switchport trunk allowed vlan 223,230
 switchport mode trunk
 switchport voice vlan dot1p
 no ip address
 mls qos trust cos
 spanning-tree portfast
!
interface FastEthernet0/5
 switchport trunk native vlan 230
 switchport trunk allowed vlan 223,230
 switchport mode trunk
 switchport voice vlan dot1p
 no ip address
 mls qos trust cos
 spanning-tree portfast

hope this helps. We had to do it like this as you can see on port 0/1 we allow more than one data VLAN's so we had to give the ports special trunks so they don't allow more then one pr.port

i2007

 

[mtxpert]

OK I've recently started working on a Nortel/Cisco convergence project here at work. I followed the first configuration and it works successfully. The phone get's the voice vlan IP and the computer get's the data vlan IP. SWEET!
OK the next part is, how can I use the auto setting in the phone for the VLAN config and somehow configure the switch to feed that informaton to it?

Some comments on the above configs:
This is a 2950 configuration - will not work on 3550/3560's - notice the missing trunk encapsulation command:
interface FastEthernet0/5
switchport trunk native vlan 230
switchport trunk allowed vlan 223,230 (this command will limit the vlans allowed through this port - optional)
switchport mode trunk
switchport voice vlan dot1p
no ip address
mls qos trust cos
spanning-tree portfast
As stated above, this is a 3550/3560 configuration:
interface FastEthernet0/1
switchport trunk encapsulation dot1q
switchport trunk native vlan 10 (native vlan = data vlan)
switchport mode trunk
no ip address
mls qos trust cos
no mdix auto
spanning-tree portfast


Also if anybody else went through the utter frustration I went through with the 3560 and the i2004 phones (any revision) you MUST have the "switchport voice vlan dot1p" statement on the port these phones are attached to to work. The 2950 and 3550 DO NOT and the phone will fire up and work on the data vlan with the phone configured for partial DHCP or full with a properly configured DHCP server. Cisco is not aware of this when I opened a TAC case and worked for several hours on the phone with a tech. Nortel doesn't mention this anywhere either. HOPEFULLY someone will find this article when googling for a fix so I can save them HOURS of work...
Hopefully somebody has done this.
Mike