Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Moving 96xx and 46xx Accross VLAN's

Status
Not open for further replies.
Dec 1, 2004
57
0
0
US
I am wondering why we have to clear the values on 46xx and 96xx IP sets when we move these sets accross VLAN's. Perhaps we don't have to, so if anyone knows how we can just unplug these sets and move them accross VLAN's without clearing the values, it would be greatly appreciated.

S8730 duplicated servers
CM 5.2 SP3
G650/G450 Gateways
4600 and 9600 IP sets (latest firmware)
 
In DHCP, so you have 2 sperate scopes, one for voice and one for data? if you have a data one, that simply just has the VLAN tag and QoS settings, that would force any native VLANS to boot in the proper VLAN and then get the rest of the info from the voice scope.
 
If your vlantest=0 you will have issues moves phones from one vlan to another without cleaing first. Set vlantest=60 to fix this.
 
In terms of DCHP Scope Strings, here is what we have in place. The first and second 176 and 242 Strings are for the Data VLAN.

176 MCIPADD=10.241.5.23,10.241.5.24,10.241.5.25,MCPORT=1719,HTTPSRVR=10.240.5.149,L2QVLAN=2010,L2QAUD=5,L2QSIG=5,VLANTEST=0

242
MCIPADD=10.241.5.23,10.241.5.24,10.241.5.25,MCPORT=1719,HTTPSRVR=10.240.5.149,L2QVLAN=2010,L2QAUD=5,L2QSIG=5,VLANTEST=0


Here are the 176 and 242 Strings for the Voice VLAN.

176
MCIPADD=10.241.5.23,10.241.5.24,10.241.5.25,MCPORT=1719,HTTPSRVR=10.240.5.149,L2QAUD=5,L2QSIG=5,VLANTEST=0

242
MCIPADD=10.241.5.23,10.241.5.24,10.241.5.25,MCPORT=1719,HTTPSRVR=10.240.5.149,L2QAUD=5,L2QSIG=5,VLANTEST=0




 
set VLANTEST=60 or don't set it all and the problem will be solved.
 
Phoneguy, thank you for the VLAN= or VLAN=60 suggestion. We, at one point, had this setting in place but we noticed if there was an outage of any type, including CLAN firmware updates, the phones did not all come back up as we expected. We changed our VLANTEST setting to =0 and we saw a noticeable difference in the phones coming back up after outages planned or unplanned.
 
in the data scopes you should remove everything but VLAN tag and QoS settings. as well i typically dont put the QoS settings in the voice scope, the phone picks it up when it initially boots. also....maybe your 46xxsettings file is overriding a setting.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top