Avaya S8500 Series User manual

Job Aid: Manual Backup Servers for S8500 or S8700 Media Servers—R2.0 or later
Manual Backup Servers for S8500 or S8700 Media Servers 1
Issue 2 June 2004 03-300154
Job Aid:
Manual Backup Servers for S8500 or
S8700 Media Servers—R2.0 or later
Please disregard any references to the S8710 Media Server in this
document. The S8700 Media Server is the currently available product. If
you need additional information, please contact your Avaya
representative or Avaya authorized business partner.
A Manual Backup Server(s) (MBS) backs up an existing S8500 Media Server or a S8700 or S8710 Media
Server pair. The MBS resolves two failure situations:
•When the primary media server(s) fail, meaning Avaya Communication Manager is unable to
control call processing
•When the network becomes fragmented, meaning the primary media server(s) cannot
communicate with remote location(s)
The MBS does not address other failure situations.
The media server(s) running Avaya Communication Manager the majority of the time is called the
primary media server(s). The active media server(s) is defined as the one(s) running Avaya
Communication Manager at any given time.
The primary media server(s) and MBS must be the same media server type. That is, the S8700 Media
Servers must be backed up with S8700 Media Servers, the S8710 Media Servers must be backed up with
S8710 Media Servers, and the S8500 Media Server must be backed up with an S8500 Media Server. Only
one MBS per primary media server(s) is permitted.
An MBS is available beginning with Release 2.0 of Avaya Communication Manager.
NOTE:
MBS requires a software update (patch) to work with Release 2.0, 2.0.1, or 2.1. Contact
your remote Services Tier 3 team to obtain the required patch.

Job Aid: Manual Backup Servers for S8500 or S8700 Media Servers—R2.0 or later
What is an MBS?
2 Manual Backup Servers for S8500 or S8700 Media Servers
03-300154 Issue 2 June 2004
What is an MBS?
An MBS adds a survivability option to those that already exist for Avaya’s media servers. An MBS is a
media server (S8500) or pair of media servers (S8700/S8710) with identical license files and translations
in a non-call-processing state. The MBS becomes available through the customer’s manual intervention
to control port networks (PNs) when a major outage takes place, such as when the primary server(s)
malfunction directly or when the channel connectivity over the LAN, WAN, or MAN, and possibly port
network connectivity is severed.
The MBS supports
•S8500, S8700, or S8710 IP Connect configuration
•S8700 or S8710 Multi-Connect configuration using:
— Center Stage Switch (CSS)
— Asynchronous Transfer Mode (ATM)
MBS does not support the Direct Connect configuration on an S8500, S8700, or S8710 Media Server.
In the supported Multi-Connect configurations, careful consideration needs to be given to deploying
IPSI-controlled PNs. To be under MBS control, the PN needs IPSI or EI connectivity that may be
different than when under the control of the primary media server(s).
For a typical S8500 Media Server installation, see Figure 1, Sample S8500 MBS configuration,on page
2. For a typical S8700 or S8710 Media Server installation, see Figure 2, Sample S8700 or S8710 MBS
configuration,on page 3.
Figure 1: Sample S8500 MBS configuration

Job Aid: Manual Backup Servers for S8500 or S8700 Media Servers—R2.0 or later
What is an MBS?
Manual Backup Servers for S8500 or S8700 Media Servers 3
Issue 2 June 2004 03-300154
Figure 2: Sample S8700 or S8710 MBS configuration
Translations must be saved only on the primary media server(s) because scheduled transfers of the
translations via script to the MBS occur automatically and overwrite any translations temporarily saved
on the MBS. No transfers take place from the MBS to the primary media server(s).
When a failure occurs, the customer activates the MBS, allowing it to take over. This also means that
when the problem rectifies itself, the customer must bring the primary media server(s) back on line as
soon as possible after deactivating the MBS.
NOTE:
If Local Survivable Processors (LSPs) exist on the system, the LSPs likely become active
before the customer manually brings up the MBS. In this case, a customer has gateway
locations that are controlled by LSPs independent of an MBS being active. As part of the
switchover, to establish control of the LSPs by the now active MBS, the LSPs must be
reset.
Avaya Communication Manager software is disabled by default on the MBS; therefore, after a reboot, the
MBS will not start call processing nor have control of any port network resources.
General operation of the MBS requires removing the file that allows Avaya Communication Manager to
start automatically when MBS reboots. Installation of the MBS also requires enabling anonymous ftp by
default on the MBS, which implies that the use of ftpserv on the MBS must cease. This environment must
be reestablished after any server configuration changes or software upgrades that affect the MBS.
All changes described above must be made by Avaya Services as part of the implementation process due
to root access requirements.

Job Aid: Manual Backup Servers for S8500 or S8700 Media Servers—R2.0 or later
Installing and configuring an MBS
4 Manual Backup Servers for S8500 or S8700 Media Servers
03-300154 Issue 2 June 2004
Installing and configuring an MBS
Install the primary media server(s) first. For installation and configuration procedures, see the appropriate
documentation listed below:
For Release 2.0:
•Getting Started with the Avaya S8500 Media Server (555-245-701)—physical installation
•Installing the Avaya S8500 Media Server with Avaya G650 Media Gateway (555-245-107)—
Communication Manager installation and configuration
•Getting Started with the Avaya S8700 Media Server (555-245-703)—physical installation
•Installing the Avaya S8700 Media Server with Avaya G650 Media Gateway (555-245-109)—
Communication Manager installation and configuration
For Release 2.1:
•Quick Start for Hardware Installation: Avaya S8500 Media Server (555-245-701)—physical
installation
•Installing and Configuring the Avaya S8500 Media Server (03-300143)—Communication
Manager installation and configuration
•Quick Start for Hardware Installation: Avaya S8700 or S8710 Media Server (555-245-
703)—physical installation
•Installing and Configuring the Avaya S8700 or S8710 Media Server (03-300145)—
Communication Manager installation and configuration
Install the MBS second. You install and configure the MBS just like the primary media server(s) with
some exceptions:
•Use different IP addresses and host names when configuring the media server(s).
•Do not translate.
•Use separate modem(s) and phone number for remote access.
•Do not connect the MBS to the control network and the customer’s LAN until both the primary
media server(s) and MBS are configured to avoid simultaneous active media servers.
Only one media server (S8500) or server pair (S8700/S8710) can be connected to the control
network and the customer’s LAN at the same time while Avaya Communication Manager is
running.
Configuring the MBS
A script must be added to both the primary media server(s) and the MBS to implement MBS. Avaya
Services must configure MBS-related scripts on the primary media server(s) and the MBS because the
configuration process requires root access. After the configuration is complete, the following statements
are true:
•The primary media server(s) is intended to be the active media server(s) most of the time.
•Flexibility in how often to schedule translations transfers is provided. Although the highest
frequency is hourly, Avaya recommends running this process daily and outside of normal business
hours or any time that network usage or activity is at a minimum.

Job Aid: Manual Backup Servers for S8500 or S8700 Media Servers—R2.0 or later
Installing and configuring an MBS
Manual Backup Servers for S8500 or S8700 Media Servers 5
Issue 2 June 2004 03-300154
•Activation and deactivation of media servers is enacted by a one-step command on both the
primary media server(s) and the MBS. The one-step command is start -a for activation and
stop -afc for deactivation.
•Translations are restored to the MBS after the script executes a backup from the primary media
server(s). These translations are current as of the last time the customer saved translations on the
primary media server(s).
CAUTION:
Do not copy the system files from the primary media server(s) to the MBS. Doing this
would overwrite MBS-specific information, causing IP and naming contentions. Follow
the directions in this document and do no more.
1Ensure that the MBS is not physically connected to the control network or customer’s network
until later in the process. If S8700 or S8710, the only connection allowed is between the
duplicated media servers.
2Configure the MBS with different host names and IP addresses than the primary media server(s).
This requires a separate, filled-out Electronic Preinstallation Worksheet (EPW) when using the
Avaya Installation Wizard (AIW). The primary media server(s) and MBS must be configured
identically as IP Connect (S8500 or S8700/S8710) or Multi-Connect (S8700/S8710). The
Ethernet port address for the Eth2 duplication link (S8700/S8710) may remain the same.
3Install the same license and authentication files on the MBS as on the primary media server(s). If
a new license is ever issued, reinstall it on both the MBS and the primary media server(s).
4Install the same software load and update on both the MBS and the primary media server(s).
NOTE:
WAN/MAN outages force either the primary or backup media server(s) into License Error
mode, as the connectivity to the reference IPSI is lost. When in License Error mode, you
can use maintenance commands but no administration commands. The license is restored
when Avaya Communication Manager reacquires the reference IPSI.
Because translations transfer from the primary media server(s) to the MBS, you do not need to
perform any administration on the MBS.
5Have Avaya Services set up the scripts and schedules on the primary media server(s) and MBS.
CAUTION:
Perform the following steps after Avaya services has completed the configuration on both
the primary media server(s) and MBS.
6Once Avaya Services finishes configuring the primary media server(s) and the MBS, they will
stop call processing on the MBS to ensure processes are stopped on the media server(s).
aConnect to the services port (Eth1) on the back of the MBS (standby if S8700 or S8710).
bClick Start > Run to open the Run dialog box.
cType telnet 192.11.13.6 and press Enter.
dType stop -acf and press Enter to stop call processing on the MBS (standby if S8700 or
S8710). If S8700 or S8710, you must do the command on both the active and standby
media servers, the standby one first.

Job Aid: Manual Backup Servers for S8500 or S8700 Media Servers—R2.0 or later
Using the MBS
6 Manual Backup Servers for S8500 or S8700 Media Servers
03-300154 Issue 2 June 2004
eUsing the Maintenance Web Interface, under Server click Status Summary.
fVerify that the field Mode: says Not Ready. If on the S8700 or S8710, both the active and
standby media servers must show Not Ready. If not, do not proceed. Call Avaya Services
immediately.
7If S8700 or S8710, repeat Steps a through f on the active MBS.
8Connect the MBS to the customer’s network.
Using the MBS
Typical failure scenario
A primary media server(s) is controlling all local and remote port networks. The MBS is not controlling
anything (Avaya Communication Manager is down). Using a secure method, the script on the primary
media server(s) backs up the security and translation files to the MBS at a scheduled time.
The script running on the primary media server(s) generates a log file in the /var/home/defty directory
called coldstandby.log that reports:
•The Verbose output of the backup command issued by the script
•Success or failure of the command(s) issued
A second log file is generated on the active primary media server(s) in the /var/home/defty/ called
lastbackup.log. This log file indicates when the last successful backup occurred as well as to which media
server on the MBS if an S8700 or S8710 pair.
The script running on the MBS generates a log file in the /var/home/defty directory called
coldstandby.log that reports:
•The verbose output of the restore command issued by the script
•Success or failure of the command(s) issued
A second log file is generated on the MBS in /var/home/defty called lastrestore.log. This log file indicates
when the last successful restore occurred as well as the file used during the restore and any files removed
as part of a cleanup process that runs against /var/home/ftp/pub.
NOTE:
Files located in /var/home/ftp/pub not ending in .tar, .tar.gz, .lic, .pwd, .bin or .fw will
automatically be removed upon execution of the scripts running on the MBS. This is not
true for the scripts running on the primary media server(s).
A failure occurs that prevents the primary media server(s) from controlling all or some of the port
networks. At this time, the customer must activate the MBS.

Job Aid: Manual Backup Servers for S8500 or S8700 Media Servers—R2.0 or later
Using the MBS
Manual Backup Servers for S8500 or S8700 Media Servers 7
Issue 2 June 2004 03-300154
If the primary media server(s) fail
1Before bringing up the MBS, disconnect the primary media server(s) from the control network for
repair. Never connect the primary media server(s) back to the control network until the customer
can tolerate a service outage and the MBS has been de-activated and disconnected from the
control network.
2Bring up the MBS
aConnect to the services port (Eth1) on the back of the MBS.
bClick Start > Run to open the Run dialog box.
cType telnet 192.11.13.6 and press Enter.
dType start -a and press Enter on the MBS (active if S8700 or S8710) to start call
processing on the MBS. If S8700 or S8710, repeat the command on the standby media
server.
eUsing the Maintenance Web Interface, under Server click Status Summary.
fVerify that the field Mode: says Active. If on the S8700 or S8710, one media server says
Active, the other says Standby. If not, do not proceed.
Service is restored to the primary media
server(s)
Once the primary media server(s) are repaired, verify operation, restore necessary system files and
translations, verify that the customer can tolerate a service outage, and de-activate and disconnect the
MBS before connecting the primary server(s) to the control network.
1Disconnect the MBS from the customer’s network.
2Stop call processing on the MBS:
aConnect to the services port (Eth1) on the back of the MBS.
bClick Start > Run to open the Run dialog box.
cType telnet 192.11.13.6 and press Enter.
dType stop -afc and press Enter on the MBS (standby if S8700 or S8710) to stop call
processing on the MBS. If S8700 or S8710, repeat the command on the active media
server.
eUsing the Maintenance Web Interface, under Server click Status Summary.
fVerify that the field Mode: says Not Ready. If on the S8700 or S8710, both the active and
standby media servers must show Not Ready. If not, do not proceed.
3Reconnect the MBS to the customer’s network and test for connectivity.
4Connect the primary media server(s) to the customer’s network and test for connectivity.
5Avaya Communication Manager on the primary media server(s) automatically connects and takes
over all the IPSI- and non-IPSI-connected port networks. This causes a service outage as the
primary media server(s) gains control. To verify:
aIn a SAT session, log into the primary media server(s). If S8700 or S8710, the active
media server.
bType list ipserver and press Enter.
cVerify that the Service State says IN for all the IPSIs.

Job Aid: Manual Backup Servers for S8500 or S8700 Media Servers—R2.0 or later
Using the MBS
8 Manual Backup Servers for S8500 or S8700 Media Servers
03-300154 Issue 2 June 2004
NOTE:
All translation changes to the MBS while the MBS was in control will be lost and must be
re-entered on the active primary media server(s) at this time.
6If the customer has LSPs, reset them.
7For the now active primary media server(s) to establish control of the LSPs, the LSPs must be
reset.
If the network becomes fragmented
Network fragmentation means both the primary media server(s) and MBS may be made active when
WAN connectivity to the far-end port networks is severed.
NOTE:
When the MBS is activated, it cannot control a PN that the primary media server(s) may
be controlling. Also, once the network problem is resolved, the MBS and the primary
media server(s) may attempt to control the same PN, resulting in unexpected service
disruptions.
You want to make sure that the network temporarily stays fragmented by physically
disconnecting the appropriate cables.
CAUTION:
To avoid unexpected service disruptions, you must physically isolate the portion of the
network fragmented from the main control network. This is to avoid situations where the
source of the network failure is outside the control of the affected customer, implying that
the repair of such a network may happen without the customer’s knowledge.
On the primary media server(s) (active server if S8700 or S8710):
1Busy out the CSS port network connectivity (PNC) fiber connections to the remote port networks.
If a duplicated bearer network, busy out both the active and standby expansion interface (EI)
circuit packs and the switch node interface (SNI) circuit packs.
This action prevents accidental EI-EAL fallback from taking control of the PNs if the PNC fiber
connectivity is restored before WAN connectivity or if PNC fiber connectivity is never lost.
NOTE:
With ATM-PNC, switched virtual circuit (SVC) connectivity cannot be reliably
severed by busying out the fiber. But you can disconnect the fiber connecting the two
segments over the WAN, that is the ATM switch/blade 1 to ATM switch/blade 2.
2Connect to the services port (Eth1) on the back of the primary media server(s) (active if S8700 or
S8710).
3Log into a SAT session.
4Type busyout board UUCSS and press Enter, where UUCSS is the location of the circuit pack
(cabinet, carrier, slot). Repeat for each EI circuit pack.

Job Aid: Manual Backup Servers for S8500 or S8700 Media Servers—R2.0 or later
Using the MBS
Manual Backup Servers for S8500 or S8700 Media Servers 9
Issue 2 June 2004 03-300154
On the MBS (active server if S8700 or S8710):
1Busy out the CSS port network connectivity (PNC) fiber connections to the remote port networks.
If a duplicated bearer network, busy out both the active and standby expansion interface (EI)
circuit packs and the switch node interface (SNI) circuit packs.
2Disconnect the MBS from the customer’s network to prevent dueling active media servers.
3Connect to the services port (Eth1) on the back of the MBS.
4Click Start > Run to open the Run dialog box.
5Type telnet 192.11.13.6 and press Enter.
6Type start -a and press Enter on the MBS (active if S8700 or S8710) to start call processing on
the MBS. If S8700 or S8710, repeat the command on the standby MBS.
7Using the Maintenance Web Interface, under Server click Status Summary.
8Verify that the field Mode: says Active. If on the S8700 or S8710, one media server says
Active, the other says Standby. If not, do not proceed.
9Type busyout board UUCSS and press Enter, where UUCSS is the location of the circuit pack
(cabinet, carrier, slot). Repeat for each EI circuit pack.
10 Connect the MBS to the customer’s network.
When the Network is No Longer Fragmented
When the network is no longer fragmented, plan for a time when service interruptions are acceptable.
On the MBS (active server if S8700 or S8710):
1Disconnect the MBS from the customer’s network.
2Connect to the services port (Eth1) on the back of the MBS.
3Click Start > Run to open the Run dialog box.
4Type telnet 192.11.13.6 and press Enter.
5Type stop -afc and press Enter on the MBS (standby if S8700 or S8710) to stop call processing.
If S8700 or S8710, repeat the command on the active MBS.
6Using the Maintenance Web Interface, under Server click Status Summary.
7Verify that the Mode: field says Not Ready. If S8700 or S8710, both the active and standby
media servers must show Not Ready. If not, do not proceed.

Job Aid: Manual Backup Servers for S8500 or S8700 Media Servers—R2.0 or later
Other Configurations
10 Manual Backup Servers for S8500 or S8700 Media Servers
03-300154 Issue 2 June 2004
On the primary media server(s) (active server if S8700 or S8710):
Avaya Communication Manager on the primary media server(s) automatically connects and takes over all
IPSI- and non-IPSI-connected port networks. This causes a service outage as the primary media server(s)
gains control. To verify:
1In a SAT session, log into the primary media server(s). If S8700 or S8710, the active media server.
2Type release board UUCSS and press Enter, where UUCSS is the location of the circuit pack
(cabinet, carrier, slot). Repeat for each EI circuit pack and SNI circuit pack if applicable.
3Type list ipserver and press Enter.
4Verify that the Service State says IN for all the IPSIs.
NOTE:
All translation changes to the MBS while the MBS was in control will be lost and must be
re-entered on the active primary media server(s) at this time.
Other Configurations
Many configurations can be created between the primary media server(s) and MBS. Customers may
choose to busy out certain IPSIs during network fragmentations or to bring up the MBS as the active
media server(s) more frequently than during a crisis. Some of these configurations are legitimate and
work fine, but the previous example is what Avaya supports. Be aware that other configurations can result
in unwanted service interruptions because two active media servers are trying to control the same IPSI
group. Also be aware that when media servers cannot communicate with the IPSI referenced in the
license file, the media server(s) go into License Error mode. After several days, a media server in License
Error mode will not accept translations.
Customer responsibilities
The customer has an active role in the MBS process. Customers must:
•Monitor their system and determine when there is an outage.
•Manually activate the MBS when there is a failure and bring it back down when the main server
or network recovers.
•Register the MBS with Avaya.
•Keep software updates (patches) the same for the MBS as the primary media server(s).
•Maintain current software upgrades for the server complex.
•Verify that the MBS is alarming to Avaya. Avaya Services will accept alarms from the MBS if
Communication Manager is running and the MBS is connected to a modem. If these conditions
are not met, the customer cannot expect Avaya to be aware of any issues around the MBS.
•Maintain copies of the software (Unity) CD on-site at the backup and main locations. The
customer can either purchase an extra CD or make a copy of the one ordered with the primary
media servers.