DHCP setup for I2004-B

[a12ozbottle]

I have been trying to setup the new I2004-B string in my DHCP server. Here is an example of what I have tried

option 128 Nortel-i2004-B,s1ip=x.x.x.x;p1=4100;etc..

The phones are 1140E running C6E firmware. Is there anything I am missing?

 

[rjhermann]

What exactly is the problem?

 

[a12ozbottle]

The phone doesn't seem to be getting the DHCP string. When I check the settings everything is still default. I went through the phones local diagnostics to check the DHCP respond string and I see nothing. When I use the i2004-a setup it works fine, just can't get the i2004-b string to work.

 

[Avaya911PLM]

Post your exact DCHP 2004-B string.

--
Fletch

Nortel Emergency Services PLM

http://nortel.com/e911

Don't forget about the FREE E911 Webinar Oct. 30th!
Register online at

http://thevoicereport.com/E911

 

[a12ozbottle]

Voice vlan option 128 string: "Nortel-i2004-b,s1ip=10.253.4.10;p1=4100;a1=1;r1=10;"

I was just testing this string out the i2004-a string works fine but when I take the "a" string out and put this "b" string in the phones do not seem to take it. What I am trying to do is use the new auto config to configure all of my phone options.

 

[Avaya911PLM]

Use something other than 128 for the B string. Acceptable option numbers are in the UNIStim 3.0 Release bulletin.

The A phones will read the A string and ignore the B string
The B phones will get both but only use the B string.

--
Fletch

Nortel Emergency Services PLM

http://nortel.com/e911

Don't forget about the FREE E911 Webinar Oct. 30th!
Register online at

http://thevoicereport.com/E911

 

[a12ozbottle]

I found the information on how to do this in the IP phone fundementals book and set it up accordingly. Is there anyone who has this working that can show me how they have it setup?

 

[a12ozbottle]

I will give it a try on another option.

 

[Avaya911PLM]

I have it in my lab, and use 2 strings.
UNIStim 3.0 Product Bulletin is at:

http://support.nortel.com/go/main.jsp?cscat=BLTNDETAIL&DocumentOID=744298.000000&searched=UNIStim

3.0

--
Fletch

Nortel Emergency Services PLM

http://nortel.com/e911

Don't forget about the FREE E911 Webinar Oct. 30th!
Register online at

http://thevoicereport.com/E911

 

[a12ozbottle]

Thanks, I looked through this bulletin and the attachment before I tried to implement this.

 

[a12ozbottle]

So you have it working in your lab? What option are you using?

 

[Avaya911PLM]

I am using 131 for the B String.

Note that if you have the Phase 0 and Phase 1 phones, and use both strings, you must:

Ensure any option string that are defined are small enough that the DHCP message does not exceed 590 bytes, or

Service the Phase 0 and Phase 1 phones with a DHCP offer that excludes the Nortel-i2004-B option.

I am moving to TFTP for all my Phase 2 and 1100/1200 series sets and setting the parameters there. At that point, I won't need the Nortel-B string anymore. The Nortel -A string will deliver the basics, and TFPT .cfg files will deliver the rest. Once you have all Phase 2 or 1100/1200 series, you can rely on Option 66 and TFTP, even for Node and TN parameters on every phone.

--
Fletch

Nortel Emergency Services PLM

http://nortel.com/e911

Don't forget about the FREE E911 Webinar Oct. 30th!
Register online at

http://thevoicereport.com/E911

 

[a12ozbottle]

That is ultimately what I am trying to accomplish. I was wanting the string to just give my phones the provisioning server address and use the .PRV files to handle the rest. I might try your route if I cant get this to work.

 

[Avaya911PLM]

Thanks for the correction! I meant .PRV not .CFG! Doh!

This is the easiest way to go for certain.

--
Fletch

Nortel Emergency Services PLM

http://nortel.com/e911

Don't forget about the FREE E911 Webinar Oct. 30th!
Register online at

http://thevoicereport.com/E911

 

[a12ozbottle]

I have been able to get this to work using the TFTP serve and .PRV files. But, I had to manually enter the provisioning server IP address what I am looking for is a way to fill this field automatically.

 

[teekow]

Here is what I use in case it helps. I have had little luck with Option 66, but if your DHCP server assigns the TFTP address correctly, then that is probably best. I have always had to assign the TFTP address manually, but I do agree it should be able to be assigned with option 66. My example requires only the voice VLAN option to be set to DHCP, which will not be required eventually once the phones ship from the factory with UNISTIM 3.0. Pardon the formatting, I just copy/pasted from an email.


Example scenario includes:
• If IP phone is pre-UNISTIM 3.0 (from factory), then the Voice VLAN option needs to be manually set to DHCP
• 1000 is the native VLAN
• 2000 is the voice VLAN
• 10.1.100.254 is the Node IP


This is the option that goes in to the default (native) VLAN 1000
Option 128:
"VLAN-A:2000."

These are the 2 options that go into the Voice VLAN
Option 128 (used after the FW is updated to UNISTIM 3.0):
"Nortel-i2004-B,s1=10.1.100.254;p1=4100;a1=1;r1=7;
cachedip=y;menulock=p;igarp=y;pcuntag=y;lldp=n;"

Option 144 (only needed for pre-UNISTIM 3.0 IP phones):
"Nortel-i2004-A,10.1.100.254:4100,1,7."


Here is the summary of what happens in this example:
• Default VLAN assigns the VOICE VLAN ID to the IP phone
• IP phone releases the default VLAN IP address and requests a new address in the Voice VLAN
• Option 144 assigns the Node IP automatically to the phones (pre-UNISTIM 3.0)
• Phone registers to Node and updates firmware
• Option 128 assigns all of the other individual options that are available to the phone such as “Ignore GARP”, “Menu Lock”, “Cached IP”, etc.
o There are dozens of these individual settings that can be automatically configured in the new firmware and they are all listed the IP Phone Fundamentals NTP
• This process takes 13 minutes
o Firmware update to UNISTIM 3.0 takes 11 of 13 minutes

 

[rjhermann]

You can use option 128 for any release. Our phones came with 0625C39 which is very old. Looking at your string above the 'b' is not capitalized; don't know if that could be the problem but I would make it capitalized.

Another note, we are migrating from a 1000M to a 1000E system. On the old system and a phone's voice vlan is set to 'DHCP,' it will pick it up fine, when putting it on the new system, it will hang on 'starting DHCP.' When I change the voice vlan setting to 'LLDP MED' it picks it up right away.

Not really sure why this is, but will be asking our sales engineer about it.

 

[a12ozbottle]

Does anyone have an example for using DHCP option 66? How should this be input? All it says in documentation is to put in the TFTP server name. can I put in just the TFTP ip address, or does it need to be in a specific format?

 

[I2007]

It has to be an ip-address in option 66.
Also, make sure that you set the vlanf=y in the infoblock, if not it will ask for IP addresses and the nortel-i2004-b string in the untagged vlan, which in your case looks to be wrong...

I2007

 

[guycable2]

If the Option 66 doesn't work be sure to add option 67 for boot file name and leave it blank. I found this in an older document some time ago and had forgotten about it. Luckily taking a look at a working sites DHCP server refreshed my memory.