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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Setup DHCP on Novell OES for Avaya 5610 phones

Status
Not open for further replies.

JesusMC

MIS
Joined
Aug 28, 2008
Messages
35
Location
US
I'm trying to setup DHCP on a Novell OES Linux server and can't seem to get the phones working. The phones will boot and get an IP for the data vlan. Then it will reboot and freeze/lock up on DHCP.

My network is as follows:

10.10.1.x(vlan=101) = data
10.10.2.x(vlan=102) = voice
10.1.10.x = servers

Novell servers running on SLES 10 SP2 x64 with OES2 SP 3 x64

I've created a dhcp service (dhcpsrvs) and 2 subnets (10.10.1.0 and 10.10.2.0) and a pool in each subnet (datapool and voicepool). In the global options I created a string option called SSON176. In the options for subnet 10.10.1.0 I've added option 176 with params L2Q=1,L2QVLAN=102. In the options for subnet 10.10.2.0 I've added 176 with params L2Q=1,L2QVLAN=102,MCIPADD=10.10.2.1,MCPORT=1719.

I've been able to get it working on a Win2k3 server but need to bring that server down soon and would like to get it working on my Novell server.

Can someone help me figure out what I've done wrong or left out?
 
is the options for subnet 10.10.2.0 take out this L2Q=1,L2QVLAN=102 and change your sting to be

MCIPADD=10.10.2.1,MCPORT=1719,TFTPsrvr=x.x.x.x, where the x.x.x.x is your file server

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries
 
I don't have a file server so I left the TFTPsrvr=x.x.x.x out but I did take out L2Q=1,L2QVLAN=102 and the phone still froze. And by freezing I mean the lights stopped flashing and

DHCP: 4 secs
VLAN ID=102

was stuck on the screen. Have to unplug and replug to get it to reboot.

Is there another option that might be causing a conflict? I'm using options 3, 4, 6, 78, and 79 as well as 176. Do I have to name 176 something specific?
 
You need a file server, the system can be file server (if 500v2/v1 with card in), add that and try again :-)

Untitled-1.png
 
do you have a boot relay on your switches so that the voice VLAN can get DHCP from the server?you could also use the IPO to provide DHCP to the phones and make it easier or just for testing.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries
 
I've seen a doc for the IPO on this somewhere, can't find it now.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
kwing112000 said:
do you have a boot relay on your switches so that the voice VLAN can get DHCP from the server?

DHCP works fine when I use my Win2k3 server. I have a cisco 2600 router pointing the server (ip helper-address 10.1.10.x)

amriddle01 said:
the system can be file server

I didn't know you could use the ip500 as the file server. I'm going to try to add that option on my Win2k3 server that is working and see if it works there. Tired of phones telling me "no file server address"

I am running phones on IP500 version 4.1(15)

But, I try adding TFTPSRVR=10.10.2.1 to option 176 on my novell server and it still froze the phone.

Bas1234 said:
I've seen a doc for the IPO on this somewhere, can't find it now.
Hate when that happens. Never can find things when you need them.


The freezing really bothers me. If it just sat there trying to find an address I would be happier. But I can't tell why it just locks up.
 
On the linux server, make sure the network port is on in the untagged data vlan, and that it has a route to the routing switch.

So no VLAN need to be tagged on the linux port.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
Might be worth asking some Novell experts (wherever they hang out) as us IP Office dudes may not be best placed to help here, it seems to be an issue with that server as oppose the system/handsets :-)

Untitled-1.png
 
Bas1234 said:
On the linux server, make sure the network port is on in the untagged data vlan, and that it has a route to the routing switch. So no VLAN need to be tagged on the linux port.

The switch the server is connected to is a HP Procurve. There are 3 vlans DEFAULT_VLAN, Data and Voice. The server is "untagged" on DEFAULT_VLAN and set to "No" for both Data and Voice.

amriddle01 said:
Might be worth asking some Novell experts

I will do. I posted here first because I thought I remembered seeing a post where someone said that had gotten it to work. I post if I find a solution elsewhere.

Thanks to all for the help
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top