Cisco VLan Implementation on Avaya IP Phone /PC

[kabudoy]

Hi All,

Need Help.

I have a problem with the our cisco vendor doing the vlan he insist that our avaya one-x phone had a problem or missed configuration.

this issue is with implementing VLan 1 for avaya one-x and VLan 6 for the PC connected at the back of avaya one-x switch port. the cisco Core Switch is 4507R this is were our medpro and clan were connected and the avaya one-x is connected to Edge Switch catalyst 3560G-48 PoE.

The default Vlan 1 which is currently working, but when he added vlan 6 and set the binding on the core switch the phone will disconnect and displayed discover.

I do need a sample or working configuration to compare.
Many thanks

 

[sjforcum]

My guess is you don't have your DHCP Server options on VLAN6 configured properly.

You need to configure the 220 SSO on the DHCP Server to specify to the phone that it belongs to VLAN1. Then the phone reboots, marks it's packets with VLAN1 which is sent to the correct DHCP Server scope (with the help of a properly configured IPHelper on the Switch).

SJF

 

[uzumaki]

add "ip cef" and "ip routing" on your catalyst switch, probably no routing definition was created on the switch. Be sure that you ping your medpro, clan and the IP phones. Make sure every subnetwork are properly routed.

Creat a voice vlan for all your One-X phones, and a normal data vlan (just like you created) to separate voice frames from data.

Do the following configuration: (this is a working config with security configuration)


interface FastEthernet1/0/14
switchport access vlan 21
switchport trunk native vlan 21
switchport mode access
switchport voice vlan 17
switchport port-security maximum 2
switchport port-security
mls qos trust cos
dot1x pae authenticator
dot1x port-control auto
dot1x host-mode multi-host
dot1x timeout reauth-period 15
dot1x timeout tx-period 3
dot1x reauthentication
no cdp enable
spanning-tree portfast
end

 

[granbb]

<In agreement with uzumaki make sure subnet are properly routedm, i have a vlan 44 is not routing for core catalyst 6506 but it´s work correctly, the catalyst Only it is the way , it checks that the vlan are correctly created and routed.

Do the following config.

interface GigabitEthernet1/0/11
switchport access vlan 23
switchport mode access
switchport voice vlan 44
switchport port-security maximum 3
switchport port-security
switchport port-security aging time 2
switchport port-security violation restrict
switchport port-security aging type inactivity
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
storm-control broadcast level 40.00
storm-control multicast level 40.00
spanning-tree portfast
spanning-tree bpduguard enable

 

[srmega41]

Your PC Vlan should be your native Vlan and the Avaya should be the secondary vlan. PC's cannot discern vlan tagging, and the switch in the Avaya phone is made to pass non-tagged vlan traffic to the PC port.

The configs above show it, as access for the PC's and voice for the Avaya vlan. In your example, you need to make vlan 6 your native vlan and 1 your voice, or secondary vlan.

 

[uzumaki]

One more thing, do not enable "mls qos" on the global configuration mode. Why? because any incoming packet that has layer 2 markings will be deleted once the packet arrived on the input buffer of the switch, the switch will tag it depending on its own recommendation --- and thats not correct.

Remember that Avaya IP phones can mark Layer 2 (COS) and Layer 3 (DSCP) Markings on its packets. This marking should never be removed so that it could be prioritize the way voice packet should be.

Enable QOS on a PER INTERFACE Basis only. Not in Global configuration mode.

 

[kabudoy]

we don't use DHCP, ip phone configured as static