VLAN not populating but DOES appear in DHCP scope 3

[thar27]

Is there a way to add MUTE CRAFT # to the config files to be pulled when plugging in a 96XX phone? Phones are NOT automatically pulling the new VLAN when being moved to a new building. VLAN information has to be manually entered. Not optimal for large moves.

end of scope: L2Q=1,L2QVLAN=100,VLANTEST=60


Suggestions?

Thanks!

 

[Okkie26]

Is this scope available in the default vlan DHCP?

 

[thar27]

I'm not quite sure what that means.. my apologies.
I know that it's defined as Option 176 and Option 242.. is that what you're asking?
And thanks for the quick response!

 

[amriddle01]

This works fine when done correctly, you don't have it correct, or correct but in the wrong place or a combination of the two

 

[thar27]

176 MCIPADD=10.XX.XX.XX,MCPORT=1719,TFTPSRVR=10.XX.XX.102,L2Q=1,L2QVLAN=100,VLANTEST=60
242 MCIPADD=10.XX.XX.XX,10.XX.XX.XX,MCPORT=1719,HTTPSRVR=10.XX.XX.112,HTTPDIR=TFTP,L2Q=0,L2QVLAN=100,VLANTEST=60


Ok... closer look. For the 176 option, the 10. address after MCIPADD is the procr address.
For 242, the TWO 10. addresses following MCIPADD are CLAN addresses. This doesn't look correct.

I've never seen this either: HTTPDIR=TFTP

 

[Okkie26]

This option should be available in the DHCP server in the native data vlan.

So when a phone is plugged in, it will receive the scope option from the data DHCP server, and reboots in the voice vlan.

 

[kwing112000]

i see this a lot

in the default DHCP scope you should have a 242 and 176 with this
L2Q=1,L2QVLAN=100,VLANTEST=60

then in your voice DHCP scope you should have this.
176 MCIPADD=10.XX.XX.XX,MCPORT=1719,TFTPSRVR=10.XX.XX.102,
242 MCIPADD=10.XX.XX.XX,MCPORT=1719,httpSRVR=10.XX.XX.102,

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Vive Communications

 

[Okkie26]

That's what I meant..


Or, you could also setup LLDP in the switches...

 

[thar27]

Thanks folks!

 

[thar27]

One more thing, if I may

L2Q=1,L2QVLAN=100,VLANTEST=60

It was suggested that the string above ALSO be placed in the default data VLAN (along with the entire DHCP scope, of course - shortened here)


Should L2Q=1 in the voice VLAN, as well? Or should L2Q=0 in the voice VLAN?

Thank you

 

[amriddle01]

No need to tell the phone what VLAN it needs to be in when it's already there

 

[amriddle01]

So VLAN in native responses and the system and file server IP in the VLAN responses

 

[intrigrant]

When the phone once received a VLAN ID and succesfully connected to that VLAN it will remember this setting when rebooted.
So when the phone is moved to another network it will first try to connect using its known VLAN and after the VLANTEST time out it will do a new DHCP request in the native LAN.
There are three things you can do:
Lower the VLANTEST value to 1 and plug in the phone in the new network, after a minute or so it will do a new DHCP request
or
plug in the phone in the new network, after one hour or so it wil do a new DHCP request
or
manually clear the phone with the local program command CLEAR

 

[thar27]

*NOTE - 96XX phones require the CRAFT command. (I only know this 'cuz I tried CLEAR and - no workie)
Thanks intrigrant!

I appreciate all the great input. Happy Holidays!

 

[intrigrant]

CRAFT is the default local admin password, I always change it on all my installs.
I hate default passwords.