Avaya Support Forums  

Go Back   Avaya Support Forums > IP Telephony and Convergence

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 04-01-2011, 12:32 AM
najeebtimani najeebtimani is offline
Hot Shot
 
Join Date: Oct 2010
Posts: 10
najeebtimani has 10 reputation points
Default CM 5.2 MBT(startup time).. more than 20 mins?

Start Up time
After powering up the system, the IP phones and the G450 need about 13 minutes to register and become operational. During that time, we can notice in system platform that the CM State is running but the application state is N/A or timeout.
Is this startup time normal?
The switch over to the failover server needs a complete system restart. So every switch over will require that time?
Note that we installed CM 5.2.1SP7 and the release is currently 02.1.016.4-18759. We used MBT template without Media Services.

Pleas Advise
Reply With Quote
  #2  
Old 04-12-2011, 06:28 AM
aviswanathan's Avatar
aviswanathan aviswanathan is offline
Hot Shot
.
 
Join Date: Feb 2010
Location: Pune
Posts: 19
aviswanathan has 11 reputation points
Default

18759 is recalled. So that need to be deactivated first. The latest SP of CM 5.2.1 is
https://support.avaya.com/css/appman...946074#summary
Expected failover/switchover times
System Platform High Availability Failover uses 30 seconds as a timeout interval of lost ping
replies upon which standby node will declare active node as dead (although it can be not
accessible, not running or blocked). When that period expires, the standby node executes a
takeover (that is, starts resources). Note that System Platform does not provide any web
interface to modify this interval.
In case of manual switchover or in case there is some state of the system that initiates
preemptive failover, the total time between start of the command and time when all resources are running on the standby node includes graceful shutdown of all resources and start of all
the resources:
• stop of resources - up to 2 minutes. If this is machine shutdown, Communication
Manager takes about 4 minutes to shutdown
• stop of resources - up to 5 minutes
• start of resources - up to 5 minutes
• resulting longest switchover time - up to 10 minutes
In case of failover due to total failure of the active node, the total time between the start of the
outage and time when all resources are running on the standby node includes detection interval
timeout and start of all the resources:
• detect active node failure - 30 seconds
• start of resources - up to 5 minutes
• resulting longest switchover time - up to 5.5 minutes
Note:
Switchover time will vary depending on hardware in use and the specific template installed
on the system. Templates with more virtual machines will take slightly longer to switch over
due to multiple virtual machines booting simultaneously
Please open a ticket/SR with backbone if MBT is taking more than 10 minutes in manual failover or 5.5 minutes in case of a normal failover.
Reply With Quote
  #3  
Old 10-13-2015, 01:00 PM
hurdk hurdk is offline
Brainiac
 
Join Date: Oct 2015
Posts: 67
hurdk has 11 reputation points
Default 5.2.1 SP 18 patch MBT

I have to install SP 18 to the CM and from what I am tolfd by Avaya I just apply the patch on the active and wait for it to sync up. Then do a failover and make sure it mirrored at which point I failover again to make sure I am on the first server.

Has anyone had any issues with just applying a patch on CM and it synching right?
Reply With Quote
  #4  
Old 10-14-2015, 06:21 AM
marzahn's Avatar
marzahn marzahn is offline
Genius
 
Join Date: May 2014
Location: Among the trees in Western RI
Posts: 236
marzahn has 24 reputation pointsmarzahn has 24 reputation points
Unhappy Welcome to the Dark Side

I have been restarting and interchanging servers on a monthly schedule since installing redundant servers. All went well. That is I was able to perform this task during business hours or not as my work load allowed.

We started opening satellite offices about two years ago. At the time, it made sense to begin moving staff into the VoIP environment. As many of you have discovered while the new phones are well accepted by most staff, They come with a host of new administrative issues. One of these is the loss of service during my monthly maintenance.

So I’m back to weekend restarting and interchanging servers. This is not a great hardship as I can easily do this remotely. And if something goes sideways, I can make the trip to the main distribution frame (MDF) to tune things up with my trusty ball peen hammer.
__________________
Thank you,
Bill Marzahn
Telecommunications Administrator
Neighborhood Health Plan of Rhode Island
299 Promenade Street
Providence, RI 02908-5720
401-459-6677 (Direct "Find-me" Line)
Reply With Quote
  #5  
Old 11-06-2015, 08:45 AM
hurdk hurdk is offline
Brainiac
 
Join Date: Oct 2015
Posts: 67
hurdk has 11 reputation points
Default 5.2.1 MBT Updates

FYI:

I updated the CM patches and the CMM Field updates then failed over to the standby server and it synced. failed back and the two servers were mirrored.

Just in case anyone else needs the info.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 12:21 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.