Hunt groups disappear.....again! 2

[Telecomboy]

This happened a few releases back when connecting with a newer Manager than the IPO, but I just installed an R10.0.0.4.0.5 system and was using R10.0.0.4.0.5 to make a change and it deleted all hunt groups when merging the change. Easy enough to send over a backup, but figured I would warn others in case this happens to them.

 

[RodneyMcSnow]

Yep, there are strange issues with R10.x, recommend upgrade to 10.1 which is stable. Otherwise, not much can be done and you will have to deal with the issues. 10.1 DOES NOT require any additional licensing.

 

[Telecomboy]

Yeah, unfortunately I was nervous using R10.1 since it just came out and the 1st version usually has bugs as well. Can't win either way.

 

[janni78]

10.1 is highly unstable, I have a ticket since my IPO rebooted frequently after installing 10.1.

It isn't the DHCP issue that's been around for long? (when having IPO LAN set to DHCP client)

"Trying is the first step to failure..." - Homer

 

[Telecomboy]

Thanks janni. I guess disappearing hunt groups are better than a frequent reboot. Just need to check after making changes to make sure they are still there.

 

[amriddle01]

Dont use DHCP client on LAN1, This bug has been around since the 500v1 chassis was released, Avaya just can't be arsed to fix it ;-)

 

[Telecomboy]

You know I never use dhcp and I did for this client. That dhcp issue didn't even occur to me, but that is exactly what is going on. I'm going to need to change that.

 

[amriddle01]

If you need to do it use LAN2, it doesn't happen then

 

[DKThomas]

I just installed a new system with 10.0.0.3 and had both LAN and WAN set to fixed. When I changed WAN to DHCP to grab an address from my SIP provider's Adtran, it kicked me off the network on LAN (internal network). I had to go to the location, and verify the system was still connected to the LAN (it was) and I could get my PC on the same switch and I could open it with manager. Could not get into it remotely, and could not ping the address remotely. Once I got on site, changed WAN to fixed, LAN started behaving again. Very strange. Just an FYI.
DT

 

[amriddle01]

Nope, also known. I have mentioned it before, if you use DHCP client it always uses the gateway issued by the DHCP server and will ignore any IP routes manually entered.
Setting both to client means it uses whichever interface got its address issued last.

 

[IPGuru]

The DHCP client mode was only ever intended as a means to make initial setup easy (so it has a valid network address & can be seen on the network when it is first booted).
Just like any other Server on a network should be on a fixed IP address

DO NOT USE DHCP CLIENT ON A CONFIGURED SYSTEM.



Do things on the cheap & it will cost you dear

 

[critchey]

You would think once you connect once it would give a message to change from DHCP is suggested or something along those lines. Then if people had this issue they could simply say well we told you not to use DHCP.

The truth is just an excuse for lack of imagination.