Consensus Please 1

[CrossTalkTek]

Avaya recommends rebooting after the DST patches.
PLEASE tell me you experiences.

 

[phoneguy55]

Just did it. No problems.

 

[sjforcum]

I was told a reboot is REQUIRED before April 1.

 

[mikeydidit]

I was too by a friend in Tier 3. I did mine last week, no problems.

Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read faq690-6594

 

[mentallimit]

We have to Reboot sometime after the patches were installed and before April 1st?

 

[CrossTalkTek]

Thanks for the reply's.

And, Yes to mentallimit,
A reboot is needed afterall. This is a linux patch, not a CM patch.

Thanks again, just wondering who all knew this.

 

[mentallimit]

Would anyone mind posting the steps for rebooting the PBX?

 

[mikeydidit]

Here is a condensed version of what Avaya has on their site. The only thing I saw that was left out was step #5. I am not sure about the other or Avaya list you refer to, so no I didnt post anything there. If you could point me in the right ditection I will look into posting it there as well.

The following procedures are for completing the patch process and the patch has already been installed.

This is what needed to be done to make the DST patch a permanent change on the severs.

1. Log into Communications Manager through the Avaya Site Administration and run the “save translations” command.
2. Log into the stand-by server through the web interface and log into the maintenance interface.
3. Select the “Make upgrade permanent” and hit submit.
4. Run the “Backup now“ command (retain 3 sets or copies of data to compact flash cards)
5. Busy out the stand-by server by selecting “busy out” (This command will only work on the stand-by server) This prevents you from accidentally busing out the active server.
6. Run the “Shut down” command. Make sure to select “delayed shutdown” and to check the “restart server after shutdown” Then hit submit..
7. After the sever comes back into service you need to hit “release server”.
This should release the sever back into a “stand-by “ status.
8. Hit the “status summary” button and check the refresh every 10 seconds button. This will let you view the status of the servers as the stand-by comes completely back into server and is able to process calls.
9. When the server comes back into service and the mode returns to “Duplication link is up, the stand-by shadowing is on, and the stand-by is refreshed.” You are now back to a “normal service state“.
10. After the above is complete you need to run the “Interchange servers” command. Do not select the “Force interchange regardless of server status. Refer back to procedure #8 and run the “status summary” command until both servers are refreshed and back into a normal service state. Now the “Stand-by” server has become the “Active” server.
11.You need to log back into the system and into the “stand-by and run procedures 3 thru 9.
This will take care of the procedures for the second server and insure the server pair have been fixed.

Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read faq690-6594

 

[mojoputter]

I attempted to load the DST patch on a CM3.1.1.628.7 and after rebooting the standby server it never came back up, I had tier 3 into it for about an hour and ended up re-loading the S/W to get it back up and working, I followed the process to a T so I'm not sure what the issue was but were going to give it another try on Thursday night. One of the Avaya tech service guys told me he had another case that the same thing happened and a reload had to be done.
He also said that this patch was created so quickly that he wouldn't be suprised if it had a few bugs in it.

 

[wildcard100001]

I only had issues with DST on CM 2.2... Avaya had to correct the issue... that did require a reboot. The patch was jacked...

Anybody, is it true that all PBX's with DST patches need to be rebooted before April 1st? This is news to me..

Thanks,

Wildcard

 

[wildcard100001]

Doh... I should have read all the threads about this...

What a pain....

Thanks,

Wildcard