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!

Register Log in
  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya phones suddenly rebooted and now several of them show "Bad File Sv Addr" 1

Status
Not open for further replies.
CorbinMyMan

CorbinMyMan

Technical User
Feb 4, 2005
267
US
We have about 25 Avaya IP phones (some S4625SW, some 5610SW) on an IP Office 500. I've had no problems for a decade from these and they've always worked wonderfully.

Last week I moved our Voicemail Pro role to a new server. It was on an old physical server and I migrated everything to a new virtual machine. Everything has been working flawlessly for a week without a problem.

Yesterday I was doing some unrelated work (moving our domain controller role to another server). In the middle of my DNS migration and testing, my desk phone suddenly rebooted for no reason at all. Turns out everyone's did. When they all came back up I had 3 phones that didn't fully boot. They said "BAD FILE SVR ADDR". It just says "* to program". When I press star it has all the settings they were configured with. Since we have such a small number of phones, when I installed them I just manually set their IP's as I was installing them. All these settings are still in the phones but no matter how many times I power cycle I still get the "BAD FILE SVR ADDR" on 3 of the phones. All the other phones are fine. The FILE SERVER address is correct in the phone (pointing to my new Voicemail Pro server thats been working fine since last week). CALL SERVER is pointing to IP office.

Is there a way to reset the phones completely from the "BAD FILE SVR ADDR" screen? I can't figure out for the life of me why this would have happened during a DNS migration.

A quick note: 802.1Q has always been OFF. Our lan they were on originally didn't do vlan tagging. As of last month it now does but they are on the same vlan they were on previously (same subnet as my IP Office) except now the vlan is tagged at the switch. Not sure if this needs to be ON or not considering they are still on the same vlan as my ip office.
 
Sort by date Sort by votes
That was the first thing I checked on new server. It is off completely. The majority of my phones have no problem connecting to it.
 
Upvote 0 Downvote
Is TFTP built into Voicemail Pro? Or the avaya tools? I didn't' install any type of TFTP server to the new server. Just the AVAYA IP OFFICE ADMIN SUITE and IP OFFICE VOICEMAIL PRO
 
Upvote 0 Downvote
The 46xx en 56xx phones can be rebooted by green-green-red then type 'reset' #

But, did you use the 'old' vm server as a fileserver as well (IP office manager)?

Is there a new fileserver available? Is the IP Address of this new fileserver set in the option 176 (not 242) in the DHCP server?

Also note that these phones use ftp rather then http..

 
Upvote 0 Downvote
TFTP server is built into manager not VM Pro
it used to be common practice to install a seedeater TFTP or HTTP server to supply firmware to handsets but that has not been necessary since the introduction of the IP 500V2 which stores all of this information on the SD Card.




Do things on the cheap & it will cost you dear
 
Upvote 0 Downvote
Okkie, There is a new file server, but the IP address is manually configured, and matches the old file server (which has been put to rest). Do I still need to set the option on my dhcp server?
 
Upvote 0 Downvote
Okkie, and yes the old server was VM and File server.
 
Upvote 0 Downvote
Thats what I said IPGuru (hence the IP Office manager in my post)...

I talked about the VM Pro server, not the service...


 
Upvote 0 Downvote
drpcken.

as long as IP Office manager is available. and the option 'enable BootP and file servers' is ticked (File > preferences) then you only need to set the IP address of the fileserver in the phone.

This can be done manually, or via option 176 in the DHCP server.

But as suggested above by mforrence, make also sure that the firewall on the fileserver has the right ports opened.
 
Upvote 0 Downvote
They are working now once I reset them. It's very strange. It must have been the firewall or something with my dns changes. Now when I plug them up, reset, then reconfigure (I actually add the vlan tag, not sure if it helps, no other phones are configured this way) they download the image and work perfectly. Weird that it only happened to 3 our of about 25 though. Thank you guys for the help.
 
Upvote 0 Downvote
There is a maximum number of how many extensions can be upgraded at the same time.

But I can't remember how much that was using manager is fileserver.
 
Upvote 0 Downvote
I take that back... one of them is still giving me a bad file svr addr error even after I reset and reconfigure... The other 2 are working fine
 
Upvote 0 Downvote
Sounds like a network issue more than an ipoffice issue TBH
Set the file server to the IP Office address instead of the voicemail

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
 
Upvote 0 Downvote
Westi, I tried setting file server to IP office address and it just sits at the upgrade screen and then restarts, over and over.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

R
  • Question
calls unable to reject on avaya j series phones for IPO 1
Replies
10
Views
601
derfloh
derfloh
BernPed
  • Locked
  • Question
Ring Central and Avaya 9
Replies
8
Views
886
telecomtekperson
T
Scuzzie2k
  • Locked
  • Question
IP Office 500 and Avaya Workplace 1
Replies
6
Views
596
derfloh
derfloh
pontim
  • Locked
  • Question
Avaya SBC delivering Certificate to j129 phones over port 443
Replies
5
Views
438
derfloh
derfloh
Raff-Tech
  • Locked
  • Question
Avaya IP Office Management API: how set "Unique Identity"
Replies
4
Views
501
Raff-Tech
Raff-Tech

Part and Inventory Search

Sponsor

Back
Top