ableseaman
Technical User
Afternoon
Bit longwinded this one........
We have an issue where IP sets on a ‘Secondary’ site won’t boot up – the set simply just continues to display ‘restarting’.
'Voice VLAN' (VLAN 2): 192.168.38.0/24
'Data VLAN 1'(VLAN 1): 192.168.8.0/24
'Data VLAN 2'(VLAN 5): 192.168.67.128/25
We have an IPO located on the 'Voice VLAN' (192.168.38.9).
We have our PC running as the HTTP/HTTPS IPO 'Server' (192.168.38.10)
The IP Handsets (1608) are provided with IP Addresses from the 'Voice VLAN' subnet.
'Data VLAN 1' is used for our primary site to serve the PC estate.
The IP Sets (1608 & 1616) serve the connection of the PC through the built-in Ethernet switch - 1 LAN switch port is a member of 'Data VLAN 1' (PVID) and 'Voice VLAN'.
We have a DHCP Server (192.168.8.10) to serve out PC estate on 'Data VLAN 1' and our 'Voice VLAN'
DHCP Server (192.168.8.10) is set-up as follows;
'Data VLAN 1' Scope
Scope Option 242
L2Q=1,L2QVLAN=2,VLANTEST=0
'Voice VLAN' Scope
Scope Option 242
MCIPADD=192.168.38.10,MCPORT=1719,HTTPSRVR=192.168.38.10,VLANTEST=0
Now this set-up works fine. The 1608 is plugged into the LAN switch. DHCP request sent on Data VLAN 1. Scope option 242 provides the Voice VLAN ID and the 802.1q to On. The 1608 then requests an IP Address from the Voice VLAN which also on Scope Option 242 provides the IP Address of the IPO, etc. The handset then updates its firmware and we configure with the extension number and password. Simple and one-step process.
We now have a secondary site which is part of the same LAN but has been served with its own IP/subnet and DHCP server. We need to provide IP Handsets via the IPO to this secondary site.
DHCP Server has an IP Address of 192.168.67.200.
Each LAN switch port to serve the IP Handsets and PCs are a member of VLAN 2 and VLAN 5 (PVID).
We initially setup the DHCP Server with the following ;
'Data VLAN 2' Scope
Scope Option 242
L2Q=1,L2QVLAN=2,VLANTEST=0
The thought was that the IP Handset would boot and obtain an IP Address from DHCP Server 192.168.67.200. It would then receive the Scope option 'L2Q=1,L2QVLAN=2,VLANTEST=0 which would tell the IP Set that 802.1Q would be set to On and the Voice VLAN is on VLAN 2. I then thought it would broadcast for an IP Address on VLAN 2 which means it would then look to DHCP Server 192.168.8.10 to be provided with its 'Voice VLAN' IP Address.
The IP Set seems to pick up the Data VLAN IP Address with the VLAN ID=2. However the set then displays 'restarting' before following the same process. This process seems to loop over and over and never boots – it never seems to receive an IP Address within the ‘Voice VLAN’.
Rather than using DHCP Server 192.168.8.10 to provide 'Voice VLAN' IP Addresses for the secondary site we have then built a 'Voice VLAN' scope on DHCP Server 192.168.67.200. The 'Voice VLAN' scope on DHCP Server 192.168.67.200 provides addresses from 192.168.38.200 - 192.168.38.250.
DHCP Server (192.168.67.200) is now set-up as follows;
'Data VLAN 2' Scope
Scope Option 242
L2Q=1,L2QVLAN=2,VLANTEST=0
'Voice VLAN' Scope
Scope Option 242
MCIPADD=192.168.38.10,MCPORT=1719,HTTPSRVR=192.168.38.10,VLANTEST=0
However this hasn't changed anything - still seems to pickup the fact it needs to broadcast on VLAN 2 but then just keeps restarting over and over again.
The only manual way we have found to get this to work is to manually change the 802.1Q setting within the IP Handset to 'On'. The handset will then boot normally. However even with changing this setting to 'On' it can take a number of restarts of the IP sets before it boots to enable the entry of the extension number and password.
I'm pretty sure this is a LAN switch issue but can't quite figure out the problem.
We simply want to plug the IP sets into the LAN switch on the Secondary site without any manual or convoluted process – basically to match the process on the Primary Site (Plug and Play – with just the extension number and password being entered).
Our LAN estate is as follows;
Avaya ERS 5632 – Layer 3 Core Switch (Primary Site) – Sanitised
*** IP ***
ip default-gateway 192.168.8.1
ip address switch 192.168.8.2
ip address netmask 255.255.255.0
spanning-tree port-mode auto
*** VLAN ***
vlan create 2,5 type port 1
vlan name 1 "Data VLAN 1"
vlan name 2 "Voice VLAN"
vlan name 5 "Data VLAN 2"
vlan ports 1 tagging tagAll filter-untagged-frame enable ####Uplink to ERS4550 for our Primary Site####
vlan ports 2-6 tagging tagAll
vlan ports 7 tagging tagAll filter-untagged-frame enable ####Uplink to ERS4550 for our Secondary Site####
###Port 23 connects to DHCP Server 192.168.8.10#####
vlan configcontrol flexible
vlan members 1 1-6,23-24
vlan members 2 1-7
vlan members 5 7
vlan ports 7 pvid 5
vlan configcontrol
autopvid
! *** L3 ***
ip routing interface
vlan 2 ip address 192.168.38.1 255.255.255.0 3 exit
interface vlan 5 ip address 192.168.67.129 255.255.255.128 2 exit
ip route 0.0.0.0 0.0.0.0 192.168.8.1 10
! *** DHCP Relay ***
ip dhcp-relay fwd-path 192.168.38.1 192.168.8.10
ip dhcp-relay fwd-path 192.168.38.1 192.168.8.10 mode dhcp
ip dhcp-relay fwd-path 192.168.38.1 192.168.67.200
ip dhcp-relay fwd-path 192.168.38.1 192.168.67.200 mode dhcp
! --- OSPF ---
router ospf enable
router ospf router-id 192.168.8.2 exit
enable configure terminal interface vlan 1 ip ospf enable exit
interface vlan 5 ip ospf network passive ip ospf enable exit
interface vlan 2 ip ospf network passive ip ospf enable exit
Avaya ERS 4550 – Layer 2 Edge Switch (Primary Site) - Sanitised
! *** IP ***
ip default-gateway 192.168.8.1
ip address switch 192.168.8.3
ip address netmask 255.255.255.0
spanning-tree port-mode auto
! *** VLAN ***
vlan create 2,5 type port 1
vlan name 1 "Data VLAN 1"
vlan name 2 "Voice VLAN"
vlan name 5 "Data VLAN 2"
vlan ports 4-47 tagging unTagPvidOnly ####Ports 4-47 are used to connect the IP Handsets and PCs####
vlan ports 50 tagging tagAll filter-untagged-frame enable ####Uplink to ERS 5632#####
vlan configcontrol flexible vlan members 1 4-47,49-50
vlan members 2 2-47,50
vlan members 5 47
vlan ports 2-3 pvid 2 ####IPO and IPO PC connect to these ports###
####Port 47 connects to our MPLS/OSPF based WAN####
vlan igmp 1 snooping enable
vlan igmp 1 proxy enable
vlan igmp 1 v1-members 4-23,25-45,47,50
vlan configcontrol flexible
no auto-pvid
Avaya ERS 4550 – Layer 2 Edge Switch (Secondary Site) - Sanitised
*** IP ***
ip default-gateway 192.168.67.129
ip address switch 192.168.67.130
ip address netmask 255.255.255.128
ip address source configured-address
spanning-tree port-mode auto
! *** VLAN ***
vlan create 2,5 type port 1
vlan name 2 "Voice VLAN"
vlan name 5 "Data VLAN 2"
vlan ports 1,3-49 tagging unTagPvidOnly ####Ports 3-49 are used to connect the IP Handsets and PCs####
####Port 2 connects to DHCP Server 192.168.67.200#####
vlan ports 50 tagging tagAll filter-untagged-frame enable ####Uplink to ERS 5632#####
vlan configcontrol flexible
vlan members 1 NONE
vlan members 2 1,3-50
vlan members 5 ALL
vlan ports ALL pvid 5
vlan configcontrol autopvid
vlan mgmt
Any assistance would be gratefully appreciated.
Able
Bit longwinded this one........
We have an issue where IP sets on a ‘Secondary’ site won’t boot up – the set simply just continues to display ‘restarting’.
'Voice VLAN' (VLAN 2): 192.168.38.0/24
'Data VLAN 1'(VLAN 1): 192.168.8.0/24
'Data VLAN 2'(VLAN 5): 192.168.67.128/25
We have an IPO located on the 'Voice VLAN' (192.168.38.9).
We have our PC running as the HTTP/HTTPS IPO 'Server' (192.168.38.10)
The IP Handsets (1608) are provided with IP Addresses from the 'Voice VLAN' subnet.
'Data VLAN 1' is used for our primary site to serve the PC estate.
The IP Sets (1608 & 1616) serve the connection of the PC through the built-in Ethernet switch - 1 LAN switch port is a member of 'Data VLAN 1' (PVID) and 'Voice VLAN'.
We have a DHCP Server (192.168.8.10) to serve out PC estate on 'Data VLAN 1' and our 'Voice VLAN'
DHCP Server (192.168.8.10) is set-up as follows;
'Data VLAN 1' Scope
Scope Option 242
L2Q=1,L2QVLAN=2,VLANTEST=0
'Voice VLAN' Scope
Scope Option 242
MCIPADD=192.168.38.10,MCPORT=1719,HTTPSRVR=192.168.38.10,VLANTEST=0
Now this set-up works fine. The 1608 is plugged into the LAN switch. DHCP request sent on Data VLAN 1. Scope option 242 provides the Voice VLAN ID and the 802.1q to On. The 1608 then requests an IP Address from the Voice VLAN which also on Scope Option 242 provides the IP Address of the IPO, etc. The handset then updates its firmware and we configure with the extension number and password. Simple and one-step process.
We now have a secondary site which is part of the same LAN but has been served with its own IP/subnet and DHCP server. We need to provide IP Handsets via the IPO to this secondary site.
DHCP Server has an IP Address of 192.168.67.200.
Each LAN switch port to serve the IP Handsets and PCs are a member of VLAN 2 and VLAN 5 (PVID).
We initially setup the DHCP Server with the following ;
'Data VLAN 2' Scope
Scope Option 242
L2Q=1,L2QVLAN=2,VLANTEST=0
The thought was that the IP Handset would boot and obtain an IP Address from DHCP Server 192.168.67.200. It would then receive the Scope option 'L2Q=1,L2QVLAN=2,VLANTEST=0 which would tell the IP Set that 802.1Q would be set to On and the Voice VLAN is on VLAN 2. I then thought it would broadcast for an IP Address on VLAN 2 which means it would then look to DHCP Server 192.168.8.10 to be provided with its 'Voice VLAN' IP Address.
The IP Set seems to pick up the Data VLAN IP Address with the VLAN ID=2. However the set then displays 'restarting' before following the same process. This process seems to loop over and over and never boots – it never seems to receive an IP Address within the ‘Voice VLAN’.
Rather than using DHCP Server 192.168.8.10 to provide 'Voice VLAN' IP Addresses for the secondary site we have then built a 'Voice VLAN' scope on DHCP Server 192.168.67.200. The 'Voice VLAN' scope on DHCP Server 192.168.67.200 provides addresses from 192.168.38.200 - 192.168.38.250.
DHCP Server (192.168.67.200) is now set-up as follows;
'Data VLAN 2' Scope
Scope Option 242
L2Q=1,L2QVLAN=2,VLANTEST=0
'Voice VLAN' Scope
Scope Option 242
MCIPADD=192.168.38.10,MCPORT=1719,HTTPSRVR=192.168.38.10,VLANTEST=0
However this hasn't changed anything - still seems to pickup the fact it needs to broadcast on VLAN 2 but then just keeps restarting over and over again.
The only manual way we have found to get this to work is to manually change the 802.1Q setting within the IP Handset to 'On'. The handset will then boot normally. However even with changing this setting to 'On' it can take a number of restarts of the IP sets before it boots to enable the entry of the extension number and password.
I'm pretty sure this is a LAN switch issue but can't quite figure out the problem.
We simply want to plug the IP sets into the LAN switch on the Secondary site without any manual or convoluted process – basically to match the process on the Primary Site (Plug and Play – with just the extension number and password being entered).
Our LAN estate is as follows;
Avaya ERS 5632 – Layer 3 Core Switch (Primary Site) – Sanitised
*** IP ***
ip default-gateway 192.168.8.1
ip address switch 192.168.8.2
ip address netmask 255.255.255.0
spanning-tree port-mode auto
*** VLAN ***
vlan create 2,5 type port 1
vlan name 1 "Data VLAN 1"
vlan name 2 "Voice VLAN"
vlan name 5 "Data VLAN 2"
vlan ports 1 tagging tagAll filter-untagged-frame enable ####Uplink to ERS4550 for our Primary Site####
vlan ports 2-6 tagging tagAll
vlan ports 7 tagging tagAll filter-untagged-frame enable ####Uplink to ERS4550 for our Secondary Site####
###Port 23 connects to DHCP Server 192.168.8.10#####
vlan configcontrol flexible
vlan members 1 1-6,23-24
vlan members 2 1-7
vlan members 5 7
vlan ports 7 pvid 5
vlan configcontrol
autopvid
! *** L3 ***
ip routing interface
vlan 2 ip address 192.168.38.1 255.255.255.0 3 exit
interface vlan 5 ip address 192.168.67.129 255.255.255.128 2 exit
ip route 0.0.0.0 0.0.0.0 192.168.8.1 10
! *** DHCP Relay ***
ip dhcp-relay fwd-path 192.168.38.1 192.168.8.10
ip dhcp-relay fwd-path 192.168.38.1 192.168.8.10 mode dhcp
ip dhcp-relay fwd-path 192.168.38.1 192.168.67.200
ip dhcp-relay fwd-path 192.168.38.1 192.168.67.200 mode dhcp
! --- OSPF ---
router ospf enable
router ospf router-id 192.168.8.2 exit
enable configure terminal interface vlan 1 ip ospf enable exit
interface vlan 5 ip ospf network passive ip ospf enable exit
interface vlan 2 ip ospf network passive ip ospf enable exit
Avaya ERS 4550 – Layer 2 Edge Switch (Primary Site) - Sanitised
! *** IP ***
ip default-gateway 192.168.8.1
ip address switch 192.168.8.3
ip address netmask 255.255.255.0
spanning-tree port-mode auto
! *** VLAN ***
vlan create 2,5 type port 1
vlan name 1 "Data VLAN 1"
vlan name 2 "Voice VLAN"
vlan name 5 "Data VLAN 2"
vlan ports 4-47 tagging unTagPvidOnly ####Ports 4-47 are used to connect the IP Handsets and PCs####
vlan ports 50 tagging tagAll filter-untagged-frame enable ####Uplink to ERS 5632#####
vlan configcontrol flexible vlan members 1 4-47,49-50
vlan members 2 2-47,50
vlan members 5 47
vlan ports 2-3 pvid 2 ####IPO and IPO PC connect to these ports###
####Port 47 connects to our MPLS/OSPF based WAN####
vlan igmp 1 snooping enable
vlan igmp 1 proxy enable
vlan igmp 1 v1-members 4-23,25-45,47,50
vlan configcontrol flexible
no auto-pvid
Avaya ERS 4550 – Layer 2 Edge Switch (Secondary Site) - Sanitised
*** IP ***
ip default-gateway 192.168.67.129
ip address switch 192.168.67.130
ip address netmask 255.255.255.128
ip address source configured-address
spanning-tree port-mode auto
! *** VLAN ***
vlan create 2,5 type port 1
vlan name 2 "Voice VLAN"
vlan name 5 "Data VLAN 2"
vlan ports 1,3-49 tagging unTagPvidOnly ####Ports 3-49 are used to connect the IP Handsets and PCs####
####Port 2 connects to DHCP Server 192.168.67.200#####
vlan ports 50 tagging tagAll filter-untagged-frame enable ####Uplink to ERS 5632#####
vlan configcontrol flexible
vlan members 1 NONE
vlan members 2 1,3-50
vlan members 5 ALL
vlan ports ALL pvid 5
vlan configcontrol autopvid
vlan mgmt
Any assistance would be gratefully appreciated.
Able
