DHCP Issues

[mdoyle]

I am a new Admin here at this company that has an exisiting Shoretel system. From what I understand the Shoretel server was installed on an existing DHCP scope in a Class C subnet. With the addition of several companys being aquired, and the Shoretel phones the first and only scope filled up fast (x.x.1.x). They added a second scope to alleviate the problem (x.x.10.x), which has for computers, but any Shoretel phone that picks up an address on that second scope will never correctly connect to the Shoretel server.

I have read a few different threads on here talking about using the 156 option in DHCP. Since we are in a production environment, I don't want to go changing anything that will put us down for any large amount of time.

The major thing is just trying to get the Shoretel phones working correctly coming off the x.x.10.x scope.

I would like to eventually go to a proper VLAN, and if that is do-able in a short amount of time with minimal down time I would like to do that now.

Any help would be appreciated, and if you would like to know any other information about how the network is setup just let me know and I will offer what I can.

Thanks

[cburgy]

I am a new Admin here at this company that has an exisiting Shoretel system. From what I understand the Shoretel server was installed on an existing DHCP scope in a Class C subnet. With the addition of several companys being aquired, and the Shoretel phones the first and only scope filled up fast (x.x.1.x). They added a second scope to alleviate the problem (x.x.10.x), which has for computers, but any Shoretel phone that picks up an address on that second scope will never correctly connect to the Shoretel server.

I have read a few different threads on here talking about using the 156 option in DHCP. Since we are in a production environment, I don't want to go changing anything that will put us down for any large amount of time.

The major thing is just trying to get the Shoretel phones working correctly coming off the x.x.10.x scope.

I would like to eventually go to a proper VLAN, and if that is do-able in a short amount of time with minimal down time I would like to do that now.

Any help would be appreciated, and if you would like to know any other information about how the network is setup just let me know and I will offer what I can.

Thanks

Are you statically assigning phones to that vlan? Is the new vlan tagged or untagged?

If it is tagged, the phones come on the default untagged (PVID) first and look at the DHCP server for op 156

It should have ftpservers=SW_Server_IP,Layer2Tagging=1,VlanID=10

Also on the VLAN 10 scope, you should have the same thing.

If you are configuring the ports to be untagged vlan 10 (no phone behind on a different vlan), then tagging = 0 and vlanid=0.

[mdoyle]

Both scopes are untagged at the moment. When scope 1 (x.x.1.x) is full clients fail over to scope 2 (x.x.10.x). When any phone fails over and pulls an address from scope 2 they get hung up and the phone shows "No service". So before I can force all phones to only pull from scope 2 I need to make sure that they will work properly.

[cardguy44]

Did you add the new range of addresses in the shorewaredirector under IP Phones...IP phone address map?

[mdoyle]

It wasn't there, it is now.

The phone boots up, gets an address from scope 2, then goes looking for the FTP server (it does show the correct IP address for the Shoretel server). It sits there for about 10 seconds then comes back with "FTP Server Unreachable".

It keeps going on it's boot until it gets to "No Service".

I should also mention that the Shoretel server resides on the same subnet as scope 1.

[cdunn]

It wasn't there, it is now.

The phone boots up, gets an address from scope 2, then goes looking for the FTP server (it does show the correct IP address for the Shoretel server). It sits there for about 10 seconds then comes back with "FTP Server Unreachable".

It keeps going on it's boot until it gets to "No Service".

I should also mention that the Shoretel server resides on the same subnet as scope 1.

Is the subnet information correct on the ShoreTel server? Can it talk with IP's on both subnets? The reason I ask is I have a complicated setup here in our office as I put the voice equipment on a seperate network and had to setup our firewall to allow communication between the Personal Call Manager and the ShoreTel Server.

[RMcCollum]

Option 33 use - may be a solution.

Is the subnet information correct on the ShoreTel server? Can it talk with IP's on both subnets? The reason I ask is I have a complicated setup here in our office as I put the voice equipment on a seperate network and had to setup our firewall to allow communication between the Personal Call Manager and the ShoreTel Server.

I have a server with 2 NICs, NIC 1 is 192.168.1.h network the other is 192.168.100.h network (static and reserved in DHCP_. The n.n.1.h network is where the PCs reside and also is where the DHCP server resides. The n.n.100.h network is where the ShoreTel Phones reside and is also defined as such in the IP Phone Address range within the ShoreTel server OS.

The server acts as router between the 2 networks (both NICs are conencted to the Primary MfDF switch) and routing occures there. I had a problem of some of the routines within PCM on the computers not connecting to the server. They are getting the .100.h network address of NIC2 on the server (ShoreTel are you listening) instead of the IP address of NIC1 (the .1.h network).

So in my scope options at the DHCP server for my PCs to find the .100.h network had to be modified with option 33 to present a route to the PCs to find the .100.h (ShoreTel server's NIC2).

So having said all this, check on option 33 as a way to present route inforation to your PCM PC devices. Not sure if ShreTel phones recognize it but your PCs will if that's part of your issue.

Roy

[eazeaz]

Using a Server as a Router

Ewwwwww :-(

[mdoyle]

I have a server with 2 NICs, NIC 1 is 192.168.1.h network the other is 192.168.100.h network (static and reserved in DHCP_. The n.n.1.h network is where the PCs reside and also is where the DHCP server resides. The n.n.100.h network is where the ShoreTel Phones reside and is also defined as such in the IP Phone Address range within the ShoreTel server OS.

The server acts as router between the 2 networks (both NICs are conencted to the Primary MfDF switch) and routing occures there. I had a problem of some of the routines within PCM on the computers not connecting to the server. They are getting the .100.h network address of NIC2 on the server (ShoreTel are you listening) instead of the IP address of NIC1 (the .1.h network).

So in my scope options at the DHCP server for my PCs to find the .100.h network had to be modified with option 33 to present a route to the PCs to find the .100.h (ShoreTel server's NIC2).

So having said all this, check on option 33 as a way to present route inforation to your PCM PC devices. Not sure if ShreTel phones recognize it but your PCs will if that's part of your issue.

Roy

My PC's don't have a problem if they are on scope 1 or 2. It's just the phone's looking for the FTP Server that fails.

Our Shoretel server does have two nics and both addresses are in scope 1. I tried moving one of them out to scope 2 yesterday and all phones in the company went down even though I changed the address on the nic that isn't bound in Shoretel server or set as the FTP server in DHCP.

Option 33 in scope 2 didn't help the Shoretel phone find the correct FTP Server either.

[cdunn]

My PC's don't have a problem if they are on scope 1 or 2. It's just the phone's looking for the FTP Server that fails.

Our Shoretel server does have two nics and both addresses are in scope 1. I tried moving one of them out to scope 2 yesterday and all phones in the company went down even though I changed the address on the nic that isn't bound in Shoretel server or set as the FTP server in DHCP.

Option 33 in scope 2 didn't help the Shoretel phone find the correct FTP Server either.

I was looking at doing something like this at 1st, but I was told the ShoreTel server does not support dual NIC's.

[RMcCollum]

I was looking at doing something like this at 1st, but I was told the ShoreTel server does not support dual NIC's.

As a side bar - pay attention to your route table (i.e. route print) on the dual NIC ShoreTel server. You may want to force persistent routes so that both networks can be found if you're leveraging a server as a router as I do. Such as; Two IP networks serviced by two NICs onto a single physical network, one NIC for the phone network and one NIC for the PC network.

About the ftp not being discovered - we had to get a ShoreTel rep on remotely to fix that problem, not real sure what was done, but the phones did start hitting the ftp server.

!!!!NOTE: Backup you database first,
By the way backups are worthless - it the restore that is valuable, so make sure you have good copies of your database before major adjustments...

[mdoyle]

Did they change something with your Shoretel server or with DHCP?

[RMcCollum]

Did they change something with your Shoretel server or with DHCP?

On the the ShoreTel Server. Did not every get a defined answer about what they did.

Have not had time poke into the details of what may have caused the issue.

[mdoyle]

Damn. I might just have to give Shoretel a call then and see if they can do the same for me.

[RMcCollum]

Damn. I might just have to give Shoretel a call then and see if they can do the same for me.

What are your option 156 settings?