cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
23086
Views
9
Helpful
17
Replies

Avaya phones connected to Cisco switch is not getting DHCP leases and phones not working

gkchakravarthy
Level 1
Level 1

                   All,

The below is the configuration on our router and we are using Avaya phones on the network .

The phones are not receiving dhcp leases and not working ,can anybody suggest what is causing this issue.

Building configuration...

Current configuration : 7871 bytes
!
! Last configuration change at 13:34:44 UTC Thu Mar 21 2013 by phadmin
version 15.1
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname ESBRBARMPLS5MB
!
boot-start-marker
boot-end-marker
!
!

no aaa new-model
!
no ipv6 cef
ip source-route
ip cef
--More--                           !
!
!
ip dhcp excluded-address 192.168.5.1 192.168.5.5
ip dhcp excluded-address 172.25.18.1 172.25.18.50
ip dhcp excluded-address 172.25.19.1 172.25.19.20
ip dhcp excluded-address 192.168.5.199 192.168.5.254
!
ip dhcp pool guest
network 192.168.5.0 255.255.255.0
default-router 192.168.5.1
lease 24
!
ip dhcp pool LAN
network 172.25.18.0 255.255.255.0
dns-server 172.26.1.5 172.26.1.125
default-router 172.25.18.1
domain-name xxxxxx.com
netbios-name-server 172.26.1.125 172.26.2.22
option 242 ascii L2Q=1,L2QVLAN=60
lease 3
!
ip dhcp pool VOICE
network 172.25.19.0 255.255.255.0
dns-server 172.26.1.5 172.26.1.125
default-router 172.25.19.1
option 242 ascii MCIPADD=172.25.19.4, MCPORT=1719, HTTPSRVR=172.25.19.5, VLANTEST=0
!
!
ip domain name xxxxxxx.com
ip name-server 172.xx.xx.xx
ip name-server 172.xx.xx.xx
multilink bundle-name authenticated
!
!

!
vtp interface gi0/0.1

!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
ip address 192.168.0.26 255.255.255.252
duplex auto
speed auto
!
interface GigabitEthernet0/1
description #Connected to Active LAN#
no ip address
no ip route-cache
duplex auto
speed auto
!
interface GigabitEthernet0/1.1
  encapsulation dot1Q 1 native
ip address 172.25.18.1 255.255.255.0
no ip route-cache
!
interface GigabitEthernet0/1.50
encapsulation dot1Q 50
ip address 192.168.5.1 255.255.255.0
ip access-group 51 out
no ip route-cache
!
interface GigabitEthernet0/1.60
description Voice Vlan
encapsulation dot1Q 60
ip address 172.25.19.1 255.255.255.0
no ip route-cache
!
interface GigabitEthernet0/2
ip address 10.1.100.2 255.255.255.252
duplex auto
speed auto
!
router bgp 65000
synchronization
bgp log-neighbor-changes
network 172.25.18.0 mask 255.255.255.0
network 172.25.19.0 mask 255.255.255.0
neighbor 192.168.0.25 remote-as xxxx
neighbor 192.168.0.25 soft-reconfiguration inbound
neighbor 192.168.0.25 prefix-list deny-route in
!
ip forward-protocol nd
!
no ip http server
ip http access-class 23
ip http authentication local
no ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
!
ip route 0.0.0.0 0.0.0.0 10.1.100.1
!
!
ip prefix-list deny-route seq 5 deny 0.0.0.0/0
ip prefix-list deny-route seq 10 permit 0.0.0.0/0 le 32
access-list 23 permit 10.10.10.0 0.0.0.7
access-list 23 permit 172.26.0.0 0.0.255.255
access-list 23 permit 192.168.0.0 0.0.255.255
access-list 51 deny   172.16.0.0 0.15.255.255
access-list 51 deny   10.4.0.0 0.0.255.255
access-list 51 permit any
!
route-map guest_traffic permit 10
match ip address 51
set ip default next-hop 192.168.1.2

!

17 Replies 17

Hello Alex ,

We have tried all the options and finally opened a ticket with Avaya and they moved the dhcp to CM and now the phones start receiving ip's .what went wrong with the router config we have no clue.

Thank You All for the wonderful support and advice on the issue.

Hi,

I see this thread for the last 2 weeks to check if it is solved or not.

it seems your issue is solved, kindly summerize the solution if you can

thanks in advance

Anas

Hello,

just for a record, we had the same issue here, Cisco 4500 switch does not need LLDP enabled and Avaya phone gets IP address. However, with Cisco 3750 and same port configuration DHCP packets were dropped (or maybe encapsulated using old VLAN ID) until LLDP was enabled. Our conclusion was that Avaya IP phone uses LLDP information to properly attach to the voice VLAN configured on the port.

K