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

R9.1 - VMPro Down Post Holiday MS Updates

Status
Not open for further replies.

cg11

MIS
Dec 8, 2004
160
US
All,

Guy,

Ip500 R9.1 matching VMPro, SIP Trunks, 180 mixed stations (54xx and 9600s).

Came in today 12/26 and VMPro is down. Been running vmpro on virtual server (2008) for 2 years without issues. MS updates (18 were installed)ran at 6am this morning and now it won't come up. All licenses are valid. IP500 can ping VM server. IP500 is working fine including SIP trunks. Manager and SSA is installed on same virtual server and work fine.

I am wondering if MS really broke vmpro this time.

Ideas? Thoughts?
 
One more thing, customer did upgrade our core cisco network switch from M9 to m10. This may or may not have something to do with vmpro not working. I do not think this is the culprit at this time but wanted to be complete as possible.
 
Problem Resolved. Solved by changing the voicemail password in IP500 security settings to the same password in VMPro client under General Preferences.

I believe this has to do with the IP Office requiring paswsword changes every few months?

The previous night's reboot of the IP500 must have initiated this?

Regards,

cg11
 
That feature isn't enabled by default, suggest someone put something in the diary for the future instances (which will at least flag up any other instances when it is liable to occur during a holiday period).

Stuck in a never ending cycle of file copying.
 
The "Password Change Period" should only affect Service User logins, it doesn't make much sense if it would require you to change System, VM Pro & Monitor passwords since it would case more issues than it fixes.

"Trying is the first step to failure..." - Homer
 
More likely someone change the VM Pro password in IPO and after the server rebooted it couldn't connect again.

"Trying is the first step to failure..." - Homer
 
If we're getting pernickity, most IT's don't let company server's auto-update. They do that manual and after a backup, so that they are present and able to rollback should the updates cause a problem. End

Stuck in a never ending cycle of file copying.
 
Janni,

Agreed, the "period" should only affect service users. Your guess is the most likely cause (someone changed the password) and it was not recognized until about 6 weeks later when the IP500 was rebooted.

Sizbut, I like the diary suggestion. I am in agreement on the auto-updates, manual is best, then test all VM functionality.

Thank you all for replies.
 
Out of curiosity, what version of 9.1 are you running on your system and what version of manager? By chance, is your control unit 9.1.4 or lower and manager is above that?
 
crichey,

All is matched for 9.1.5 including level of Manager.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top