Administering Avaya Aura® System
Administering Avaya Aura® System
Administering Avaya Aura® System
System
Manager for Release 6.3.8
Release 6.3
Issue 4
June 2014
System Manager
Overview and Specification
Describes product characteristics
and capabilities, including product
overview and feature descriptions,
interoperability, performance
specifications, security, and licensing
requirements.
Sales Engineers,
Solution
Architects,
Implementation
Engineers, and
Support
personnel
Implementation
Deploying Avaya Aura
System
Manager on System Platform
Describes the procedures to install
and configure System Manager on
System Platform.
Implementation
Engineers and
Support
personnel
Deploying Avaya Aura
System
Manager on VMware in
Virtualized Environment
Describes the procedures for
deploying the Avaya Aura
System
Manager virtual application in
Virtualized Environment. The
document includes procedures for
installation, configuration, initial
administration, troubleshooting, and
basic maintenance.
Implementation
Engineers,
Support
personnel
Installing the Dell
PowerEdge
R610 Server,
03-603793
Describes the procedures to install
the Dell
PowerEdge
R610 server.
Implementation
Engineers and
Support
personnel
Installing the HP ProLiant
DL360 G7 Server, 03-603799
Describes the procedures to install
the HP ProLiant DL360 G7 server.
Implementation
Engineers and
Related resources
Administering Avaya Aura
System Platform
Describes the procedures to install
and troubleshoot System Platform.
Implementation
Engineers and
Support
personnel
Maintenance and Troubleshooting
Upgrading Avaya Aura
System
Manager from earlier releases to the
latest release on VMware in
Virtualized Environment.
Implementation
Engineers,
Support
personnel
Avaya Aura
System Manager
Fault Management and
monitoring using SNMP
Describes the procedures to monitor
System Manager using SNMP.
Implementation
Engineers and
Support
personnel
Troubleshooting Avaya Aura
System Manager
Describes the procedures to
troubleshoot the problems during the
installation and administration of
System Manager and the managed
elements that System Manager
supports.
Implementation
Engineers and
Support
personnel
Training
The following courses are available on the Avaya Learning website at http://www.avaya-
learning.com. After logging into the website, enter the course code or the course title in the
Search field and click Go to search for the course.
Course
code
Course title Type
1A00234
E
Avaya Aura
Engage Theory
1A00236
E
Knowledge Access: Avaya Aura
Session
Manager and System Manager
Fundamentals
AvayaLive
Engage Theory
Introduction
24 Administering Avaya Aura
Session
Manager and System Manager
Implementation
ALE License
5U00050
E
Knowledge Access: Avaya Aura
Session
Manager and System Manager Support
ALE License
5U00095
V
Avaya Aura
System Manager
Implementation, Administration,
Maintenance, and Troubleshooting
vILT+Lab Level 1
5U00097I
Avaya Aura
Session Manager
and Avaya Aura
System Manager Release 6.3.8 supports the following new features and
enhancements:
Support for the deployment on VMware Release ESXi 5.5 in Virtualized Environment
Support for the following web browsers:
- Microsoft Internet Explorer Release 8.x, 9.x, and 10.x
- Mozilla Firefox Release 27, 28, and 29
Note:
System Manager does not support Firefox releases earlier to 27.
System Manager overview
28 Administering Avaya Aura
applications
in future releases of System Manager:
System Manager collects all the needed upgraded information from the administrator at
the beginning of the upgrade process workflow. Communication Manager and other
Avaya Aura
Settings icon ( ): You can navigate to Help, About, and Change Password links.
User Preference: You can add a page as your preference by using the plus sign (+) in
the top-right corner. The web console displays the link to the page on System Manager.
You can delete the user preferences.
Quick Navigator: You can type the name of the link that you want to search. The web
console displays all related links with the search text in the top-right corner of the page.
You can click a link to navigate to the specific page.
A message on the web console that prompts you to restart the System Manager virtual
machine after a patch installation if the kernel is upgraded.
The Administrators link opens on the same System Manager window in a different tab.
Log on to System Manager
Administering Avaya Aura
Session
Manager and Communication Manager.
Geographic Redundancy
70 Administering Avaya Aura
Session Manager
Release 6.3.
Geographic Redundancy-unaware element
An element that does not support Geographic Redundancy, such as Avaya Aura
Session
Manager release earlier than 6.3.
Geographic Redundancy operational modes
The normal operation mode. Also called the Sunny Day scenario. A System Manager
Geographic Redundancy scenario where the primary System Manager server runs in the
active mode while the secondary System Manager server runs in the standby mode
providing limited set of services. In the normal operation mode, the primary System
Manager server manages all elements and provides the complete System Manager
functionality.
Primary nonoperational mode. Also called the Rainy Day scenario. The primary System
Manager server fails or loses connectivity to all elements that the system manages. The
administrator activates the secondary System Manager server to make the secondary
System Manager server manage all elements in the system.
Split network. A System Manager Geographic Redundancy scenario when the primary
and secondary System Manager servers run in the active mode but cannot communicate
with each other due to a network connectivity outage or when some elements cannot
Geographic Redundancy
72 Administering Avaya Aura
PowerEdge
R620 server.
Must have the same hardware configuration, for example, the same processor.
Must contain the same version of the System Platform software that includes software
packs.
Geographic Redundancy replication
Administering Avaya Aura
System
Manager on the Avaya Support website at http://support.avaya.com/.
Must ensure that the minimum data pipe between the primary and the secondary System
Manager server is T1. T1 provides 1.544 Mbps.
Must ensure that the network latency is less than 500 ms.
Prerequisites for System Manager on VMware in the
Geographic Redundancy setup
In a Geographic Redundancy-enabled system running on VMware, ensure that System
Manager that you designate as primary and secondary systems meet the following
requirements:
Must be on VMware environment.
Note:
System Manager does not support the mixed VMware and System Platform
environment. For example, the primary System Manager on and the secondary System
Manager on VMware ESXi.
Must contain the same profile for primary and secondary System Manager Geographic
Redundancy virtual machines. For example, if the primary System Manager contains
Profile 1, the secondary System Manager must also contain Profile 1.
Geographic Redundancy
74 Administering Avaya Aura
System
Manager on the Avaya Support website at http://support.avaya.com/.
Must ensure that the minimum data pipe between the primary and the secondary System
Manager server is T1. T1 provides 1.544 Mbps.
Must ensure that the network latency is less than 500 ms.
Key tasks for Geographic Redundancy
Prerequisites
Ensure that the two System Manager servers meet the requirements that are defined in
Prerequisites for servers in the Geographic Redundancy setup.
Key tasks
Only the system administrator can perform Geographic Redundancy-related operations.
Configure Geographic Redundancy.
Configure Geographic Redundancy to handle the situation when the primary System
Manager server fails or when the managed element loses connectivity to the primary
System Manager server.
Important:
During the configuration of Geographic Redundancy, the primary System Manager
replicates the data between the primary and the secondary System Manager servers.
Therefore, ensure that the system maintenance activities such as backup, restore, and
shutdown are not in progress.
Enable the Geographic Redundancy replication between the two servers.
Key tasks for Geographic Redundancy
Administering Avaya Aura
Session
Manager
6.3 Active-Standby (Auto)
6.2 and earlier GR-unaware
Communication Manager 6.2 and earlier Active-Standby (Manual)
CS 1000 7.5 Active-Active
Meeting Exchange 6.2 GR-unaware
Conferencing 7.0 GR-unaware
Presence Server 6.1.4 GR-unaware
CallPilot 5.0 GR-unaware
Messaging
Avaya Aura
Agent
2.5 GR-unaware
Avaya Aura
Contact Center
6.3 Active-Active
Configuring the GR-unaware elements to work with System Manager
Administering Avaya Aura
Presence Services.
CallPilot configuration
CallPilot elements are GR-unaware. All communication with CallPilot is always initiated from
System Manager. CallPilot does not store the IP address or FQDN of System Manager. In
other words, System Manager points to CallPilot, but CallPilot does not point to System
Manager. Use the Quantum UI to add the CallPilot element to System Manager. The system
stores the element information in Elements tables through the UDDI interface and replicates
to the secondary System Manager. The system provisions the System Manager data to the
CallPilot element through the CallPilot adapter integrated with UPM. During a failover or an
ActiveActive scenario, CallPilot elements can be serviced using any of the active System
Manager. The secondary System Manager must have CallPilot certificates. CallPilot
certificates are imported in the primary System Manager server. The system replicates the
certifications to the secondary server using file replication.
System Manager Geographic Redundancy deployment does not support some CallPilot
functionality. For more information, see Limitations to the CS 1000 and CallPilot functionality
support on System Manager.
Related topics:
Limitations to the CS 1000 and CallPilot functionality support on System Manager on
page 105
Geographic Redundancy
108 Administering Avaya Aura
Conferencing configuration
Avaya Aura
Conferencing.
Procedure
1. On the web browser, type http://<IP address>:12120.
where IP address is the logical IP address of the server that is running the Element
Manager Internal OAM Service.
2. Press Enter.
The system displays a webpage with the IP address that you entered and the
Launch Element Manager Console link.
3. Click Launch Element Manager Console.
4. In the navigation pane of Element Manager Console, select Addresses.
5. In the Addresses window, click Add (+).
6. In the Add IPv4 Address dialog box, complete the following fields:
Logical Name: Type SMGRAddress.
IPv4 Address: Type the IP address of the primary System Manager.
7. Click Apply.
8. Repeat Step 3 through Step 5 on the secondary System Manager, and enter a
logical name and IP address.
9. In the navigation pane, click External Nodes.
10. In the External Nodes window, click Add (+).
Configuring the GR-unaware elements to work with System Manager
Administering Avaya Aura
Conferencing. Because
the same root Certificate Authority exists on the primary and the secondary System Manager,
you can use the same end-identity certificate for both System Manager servers. During a
failover in a System Manager Geographic Redundancy setup, for trust management to work,
reconfigure the IP address and FQDN to match the IP address and FQDN of the active System
Manager.
Single Sign-On and Role Based Access Control
For the initial setup, follow the procedures in Deploying Avaya Aura
Conferencing. In a System
Manager Geographic Redundancy setup, all elements in the inventory, such as Avaya Aura
Conferencing. In a System
Manager Geographic Redundancy setup, all elements in the inventory, user profiles, and user
data in the System Manager database replicate between the primary and secondary System
Manager. During a failover in System Manager Geographic Redundancy setup, Single Sign-
On or RBAC must work for user management. Reconfigure the IP address and FQDN to match
with the IP address and FQDN of the active System Manager.
Configuring the GR-unaware elements to work with System Manager
Administering Avaya Aura
Conferencing. In a System Manager Geographic Redundancy setup, send the logs to the
active System Manager. In a GR-enabled System Manager pair, the enrollment password is
the same for the primary and active System Manager servers. During a failover in a System
Manager Geographic Redundancy setup, for log forwarding to the active System Manager,
run the logAgent script again with the IP address or FQDN of the active System Manager, the
same https System Manager port, and the same enrollment password.
Alarms
For the initial setup, follow the alarm forwarding procedures in Deploying Avaya Aura
Contact Center
Avaya Aura
System Manager.
4. Convert the primary System Manager server to standalone server.
5. On System Manager web console, click Services > Replication and verify that the
system synchronized all elements to the primary System Manager server the data
replication is working.
6. Log on to System Manager web console of the standalone System Manager server
that you installed and change the password.
7. Configure Geographic Redundancy.
8. Enable the Geographic Redundancy replication if you have not already enabled.
Related topics:
Configuring Geographical Redundancy on page 77
Enabling the Geographic Redundancy replication on page 79
Converting the primary System Manager server to the standalone server on page 88
Replacing System Manager servers
Administering Avaya Aura
Aura is
lost. If a Branch Session Manager is
selected, and the termination and origination
application sequences contain a
Communication Manager application,
sequencing to this application continues,
locally, to the Communication Manager
survivable remote server resident with the
Branch Session Manager. A selection is
optional.
Note:
If a termination or origination application
sequence contains a Communication
Manager application, the Communication
Manager associated with the application
must be the main Communication
Manager for the Communication Manager
survivable remote server that is resident
with the Branch Session Manager.
Max. Simultaneous Devices The maximum number of endpoints that you
can register at a time using this
communication profile. If you register more
than one endpoint, all the endpoints receive
calls simultaneously.
Block New Registration When Maximum
Registrations Active
If you select the check box and an endpoint
attempts to register using this
communication profile after the registration
requests exceed the administered limit, the
system denies any new registrations with
Session Manager. The system sends a
warning message and stops the SIP service
to the endpoint.
Origination Application Sequence An application sequence that will be invoked
when the system routes the calls from this
user. A selection is optional.
Note:
If you specify origination and termination
application sequences, and if each
sequence contains a Communication
Manager application, Communication
Managing users
Administering Avaya Aura
Messaging
server.
deleteOnUnassign Optional
Class of service
cos
The class of service
for this subscriber.
The COS controls
subscriber access to
many features and
provides general
Optional Valid ranges from 0
to 995
Managing users, public contacts, and shared addresses
514 Administering Avaya Aura
Avaya Aura
Avaya Aura
Messaging server
Save as Template Saves your current settings as a template.
Basic Information
Field Description
Class Of Service The class of service for this subscriber. The
COS controls subscriber access to many
features and provides general settings, such
as mailbox size. You can select an option
from the drop-down box.
Community ID The default community ID for the subscriber.
Community IDs are used to control message
sending and receiving among groups of
subscribers. The default value is 1.
Numeric Address The unique address in the voice mail
network. The numeric address can be from 1
to 50 digits and can contain the Mailbox
Number.
PBX Extension The primary telephone extension of the
subscriber. For a Multisite system
subscriber, this number is up to 50 digits in
length.
Site The name of the site. Messaging includes a
site named Default. Change this name when
you set the site properties for the first time.
Subscriber Directory
Field Description
Email Handle The name that the system displays before
the computer name and domain in the
subscriber's email address.
Telephone Number The telephone number of the subscriber as
displayed in address book listings and client
applications. The entry can be a maximum of
50 characters in length and can contain any
combination of digits (0-9), period (.), hyphen
Managing elements
606 Administering Avaya Aura
Communication
Manager Feature Description and Implementation, 555-245-205.
blank Indicates that the existing location algorithm applies. By default, the
value is blank.
Active Station Ringing
Defines how calls ring to the telephone when it is off-hook without affecting how calls ring at
this telephone when the telephone is on-hook.
Valid Entry Usage
continuous All calls to this telephone ring continuously.
single Calls to this telephone receive one ring cycle and then ring silently.
if-busy-single Calls to this telephone ring continuously when the telephone is off-hook
and idle. Calls to this telephone receive one ring cycle and then ring
silently when the telephone is off-hook and active.
silent All calls to this station ring silently.
Auto Answer
In an Expert Agent Environment (EAS) environment, the auto answer setting for an Agent
LoginID overrides the endpoint settings when the agent logs in.In EAS environments, the auto
answer setting for the Agent LoginID can override a stations setting when an agent logs in.
Valid entry Usage
all All ACD and non-ACD calls to an idle station cut through immediately.
The agent cannot use automatic hands-free answer for intercom calls.
With non-ACD calls, the station rings while the call is cut through. To
prevent the station from ringing, activate the ringer-off feature button,
provided the Allow Ringer-off with Auto-Answer feature is enabled for the
system.
acd Only ACD split, ACD skill, and direct agent calls cut through. Non-ACD
calls to the station ring audibly.
Managing Communication Manager
700 Administering Avaya Aura
Communication
Manager, 03-300509.
hunt group A hunt group is a group of extensions that
receive calls according to the call distribution
method you choose. When a call is made to
a certain phone number, the system
connects the call to an extension in the
group. Use hunt groups when you want more
than one person to be able to answer calls to
the same number.
For more information on hunt groups, see
Managing Hunt Groups in the
Administering Avaya Aura
Communication
Manager, 03-300509.
intercom group An intercom group is a group of extensions
that can call each other using the intercom
feature. With the intercom feature, you can
allow one user to call another user in a
predefined group just by pressing a couple of
buttons.
For more information on intercom groups,
see Using Phones as Intercoms in the
Managing Communication Manager objects
Administering Avaya Aura
Communication
Manager, 03-300509.
pickup group A pickup group is a group of extensions in
which one person can pick up calls of another
person.
For more information on pickup groups, see
Adding Call Pickup in the Administering
Avaya Aura
Communication Manager,
03-300509.
terminating extension group A Terminating Extension Group (TEG)
allows an incoming call to ring as many as 4
phones at one time. Any user in the group
can answer the call.
For more information on terminating
extension groups, see Assigning a
Terminating Extension Group in the
Administering Avaya Aura
Communication
Manager, 03-300509.
Edit Endpoint Extension field descriptions
Use this page to change the extension of an endpoint.
Field Description
System Specifies the list of Communication
Managers. Select one of the options.
Extension Extension of the device you want to
change.
New Extension New extension you want to provide for the
device.
Emergency location extension Existing emergency location extension of
your device.
New emergency location extension New existing emergency location extension
you want to provide.
Message lamp extension Existing message lamp extension of your
device.
New message lamp extension New message lamp extension you want to
provide.
Managing Communication Manager
722 Administering Avaya Aura
Communication Manager
Feature Description and Implementation,
555-245-205, for a detailed description of
Bearer Capability Classes (BCC) and their
ability to provide specialized routing for
various types of voice and data calls. The
BCC value is used to determine compatibility
when non-ISDN-PRI facilities are connected
to ISDN facilities (ISDN-PRI Interworking).
The valid entries are:
1: Relates to 56-bkps
2, 3, 4: Relates to 64 kbps
Broadcast Address Used with Ethernet data modules. Does not
appear for S87XX Series IP-PNC.
Connected Data Module This is the data module extension to which
the link connects. Used with Processor
Managing Communication Manager objects
Administering Avaya Aura
Communication Manager,
555-233-504, for more information on Point-
to-Point data modules.
system-port Assigns a System Port Data Module.
tdm Assigns a DTE interface for Processor/Trunk
Data Modules. See the pdm entry above.
wcbri Assigns a World Class BRI Data Module.
Button Description
Commit Performs the action you initiate.
Schedule Performs the action at the specified time.
Reset Clears the action and resets the fields.
Clear Clears all entries.
Done Completes your current action and takes you
to the subsequent page.
Cancel Cancels your current action and takes you to
the previous page.
Now Performs the action you initiate real time.
Managing Communication Manager objects
Administering Avaya Aura
Session Manager.
Viewing details of an element
Procedure
1. On the System Manager web console, click Services > Inventory.
2. In the left navigation pane, click Manage Elements.
3. On the Manage Elements page, select an element.
4. Click View.
The system displays the details of the selected element.
Modifying an element
Procedure
1. On the System Manager web console, click Services > Inventory.
2. In the left navigation pane, click Manage Elements.
Managing inventory
886 Administering Avaya Aura
Messaging
Version The version of Messaging. Supported
versions are 5.0 and later.
Secured LDAP Connection An option to use the secure LDAP
connection.
To use the nonsecure LDAP connection, you
must clear the check box.
Port The port on which the LDAP or secure LDAP
service that the element provides is running.
The default port is 389 for LDAP and 636 for
secure LDAP.
Location The location of the element.
Delete Element Confirmation field descriptions
Use this page to delete an element.
Name Description
Name The name of the element.
Node The node on which the element is running.
Registration The registration status of the element. The
options are:
True: Indicates a registered instance.
False: Indicates an unregistered
instance.
Description A brief description about the element.
Button Description
Delete Deletes the selected element.
Cancel Closes the Delete Element Confirmation
page.
Managing elements
Administering Avaya Aura
System Manager
Fault Management and monitoring using SNMP.
Managing SNMPv3 user profiles
Creating an SNMPv3 user profile
Procedure
1. On the System Manager web console, click Services > Inventory.
2. In the left navigation pane, click Manage Serviceability Agents > SNMPv3 User
Profiles.
3. Click New.
4. On the New User Profile page, complete the User Details section.
5. Click Commit.
Related topics:
SNMPv3 user profiles field descriptions on page 930
Managing inventory
928 Administering Avaya Aura
Messaging server.
Class Of Service The Class Of Service for this subscriber. The
COS controls subscriber access to many
features and provides general settings, such
as mailbox size. You can select an option
from the drop-down list.
Community ID Specifies the default community ID for the
subscriber. Community IDs are used to
Templates
1112 Administering Avaya Aura
PowerEdge
R610, Dell
PowerEdge
PowerEdge
R610, Dell
PowerEdge
R620, HP
ProLiant DL360 G7, and HP
ProLiant DL360p G8
8 GB
CM_SurvRemote
S8800, S8510, Dell
PowerEdge
R610, Dell
PowerEdge
R620, HP
ProLiant DL360 G7, and HP
ProLiant DL360p G8
8 GB
CM_SurvRemoteEmbed S8300D 8 GB
CM_onlyEmbed S8300D 8 GB
The following mandatory preupgrade checks apply only to Communication Manager Release
5.2.1:
The S8510 (Dell PoweEdge 1950) server requires a 3 HDD /RAID 5 to get the 272GB
disk space for Communication Manager on System Platform and additional 1GB DIMMs
to get to 8GB DRAM.
The S8800 (IBM x3550) server requires a third HDD and conversion to RAID 5 to get to
272 GB, and 4 additional 2GB DIMMs to get to 12GB DRAM.
Preupgrade status
Icon State Description
Unknown or Not-
Started
Indicates that the preupgrade check has
not started, or the preupgrade check was
not run earlier.
Software Management
1202 Administering Avaya Aura
System
Platform.
Software Inventory
Administering Avaya Aura
Communication Manager.
When you upgrade a System Platform-based Communication Manager with Branch Session
Manager, the system upgrades the Branch Session Manager.
When you upgrade a System Platform-based Communication Manager with Communication
Manager Messaging, the system upgrades Communication Manager Messaging.
Procedure
1. On the System Manager web console, click Services > Software Management.
2. In the left navigation pane, click Software Inventory.
3. On the Software Inventory page, select the templates that you want to upgrade.
4. Click Upgrade.
5. On the System Platform Template(s) Upgrade Configuration page, select one or
more templates of the same type.
6. In the Upgrade Configuration section, select the templates that you want to
upgrade and complete the fields.
For more information, see System Platform Template(s) Upgrade Configuration
field descriptions.
7. Perform one of the following actions:
To upgrade the solution template automatically, select Auto Commit
Upgrade.
Important:
You cannot perform rollback if you select Auto Commit Upgrade.
To commit the upgrade of the Communication Manager template manually,
perform the following:
i. Clear the Auto Commit Upgrade check box.
ii. On the Software Inventory page, click More Actions > Commit
Template Upgrade.
8. (Optional) If you find any errors or issues, click More Actions > Rollback
Template Upgrade.
The system rolls back the software to the original version.
Software Management
1206 Administering Avaya Aura
Communication Manager.
Procedure
1. On the Software Inventory page, click the status of the Communication Manager
device to view the logs and the description of the upgrade operation.
The system displays the status of the upgrade in Status column.
2. To verify that the upgrade is successful, check the following on the Software
Inventory page:
Software Inventory
Administering Avaya Aura
Communication Manager:
Recording the configuration screens.
Worksheet for upgrading Communication Manager to simplex and embedded
templates.
Sample scenario to upgrade Communication Manager Release 6.x to 6.3.6
To upgrade Communication Manager Release 6.x to 6.3.6, do the following:
1. Perform the Preupgrade tasks on page 1208
2. Perform the Upgrading Communication Manager 6.x to Release 6.3.6 on
page 1209
3. Perform Verifying the upgrade on page 1207
Preupgrade tasks
No. Task References
1. Discover the devices that you want
to upgrade by enabling SNMP or
adding from Discovery on the
Manage Elements page.
Discovering elements on page
914
2. Configure user settings. Configuring user settings on
page 1192
Software Management
1208 Administering Avaya Aura
Communication Manager
on System Platform.
CM VM Platform Patch The platform patch for the Communication
Manager virtual machine.
CM VM Kernel Patch The kernel patch for the Communication
Manager virtual machine.
Override Recommended Failure The checkbox that specifies whether the
system must override any recommended
preupgrade check failure that occurs during
the element upgrade. When you select this
checkbox, the system tries to upgrade the
element.
Note:
You must select Override
Recommended Failure if one or more of
the earlier recommended preupgrade
checks have failed.
Note:
If a version is unavailable in the library, the system displays a warning for the following fields:
Upgrade To
Communication Manager
System Platform Upgrade Version
System Platform Update Version
Software Management
1212 Administering Avaya Aura
Communication Manager:
Recording the configuration
screens.
Worksheet for upgrading
Communication Manager to
simplex and embedded
templates.
6. Create the authorization file for
System Platform, and store the file
in My Computer.
For more information, contact the
Avaya support team.
7. Create the new EPW file for the
Communication Manager selected
for upgrade, and provide all
credentials to the EPW file including
For more information, contact the
Avaya support team.
Software Inventory
Administering Avaya Aura
Communication Manager.
The system backs up most of the server data and restores the data after the upgrade.
You must verify and complete the configuration after the upgrade is complete.
Create the authorization file for System Platform, and store the file in My Computer.
For more information, contact the Avaya support team.
Create the EPW file for the Communication Manager selected for upgrade, and provide
all credentials to the EPW file including System Platform details. Store the EPW file on
the HTTP or HTTPS server.
For more information, contact the Avaya support team.
Get the WebLM server IP address that is mandatory for licensing.
For more information, contact the Avaya support team.
Get the inventory for Communication Manager 5.2.1.
The get inventory operation ensures that the system reflects the exact state of the device
in Software Inventory.
Software Inventory
Administering Avaya Aura
Communication Manager:
Recording the configuration
screens.
Worksheet for upgrading
Communication Manager to
simplex and embedded
templates.
6. Create the authorization file for
System Platform, and store the file
in My Computer.
For more information, contact the
Avaya support team.
7. Create a new EPW file for the
Communication Manager instance
selected for upgrade, and provide
all credentials to the EPW file
including System Platform details.
Store the EPW file on the HTTP or
HTTPS server.
For more information, contact the
Avaya support team.
8. Get the WebLM server IP address
for licensing.
For more information, contact the
Avaya support team.
9. Get the inventory for
Communication Manager 5.2.1.
Get inventory software
inventory on page 1196
10. Analyze the software. Analyzing the software for
software inventory on page 1198
11. Download the related firmware for
the Communication Manager
upgrade.
Downloading the software for
software inventory on page 1199
12. Perform preupgrade checks. Performing the preupgrade
check on page 1199
Software Management
1222 Administering Avaya Aura
Communication Manager
on System Platform.
CM VM Platform Patch The platform patch for the Communication
Manager virtual machine.
CM VM Kernel Patch The kernel patch for the Communication
Manager virtual machine.
Override Recommended Failure The checkbox that specifies whether the
system must override any recommended
preupgrade check failure that occurs during
the element upgrade. When you select this
checkbox, the system tries to upgrade the
element.
Note:
You must select Override
Recommended Failure if one or more of
the earlier recommended preupgrade
checks have failed.
Update Operations
Fields Description
CM Service Pack The Communication Manager service pack
version that you are entitled to.
SES Service Pack The SES service pack update that you are
entitled to.
Kernel Update The kernel update that you are entitled to.
Platform/Security Update The platform or security update that you are
entitled to.
License Authentication Operations
Fields Description
Import License File The license file that you must select for the
upgrade.
Import Authentication File The authentication file that you must select
for the upgrade.
Managing software
Administering Avaya Aura
Session Manager.
Procedure
1. On the System Manager web console, click Services > Inventory.
2. In the left navigation pane, click Manage Elements.
3. Select the registered element from the table.
4. Click Edit.
5. In the General section, in the Node field, update the value.
6. In the Access Profile section, in the Host field update the value.
Changing the System Manager IP address in managed elements
About this task
When the IP address or FQDN of System Manager changes:
If the managed elements use JNDI lookup to communicate with System Manager, the
elements must point to the new System Manager IP address.
The adopting element must recreate the License Manager object with the new IP
address.
Data replication on managed elements, such as Session Manager and Presence can
have an impact because both elements use the System Manager host name to
communicate with System Manager.
Therefore, you must change the references of System Manager IP address and FQDN on the
managed elements, such as Session Manager, Presence, and AES so the elements can
continue to connect and communicate with System Manager.
Procedure
To change the IP address or FQDN of System Manager on the managed elements,
see the documentation of the element.
Changing IP address or FQDN in System Manager running on System Platform
Administering Avaya Aura
System Manager.
Related topics:
changeIPFQDN command on page 1278
System Manager command line interface operations on page 1279
changeIPFQDN command
Use the changeIPFQDN command to change the IP address, FQDN, DNS address, Gateway,
Netmask address for System Manager, and the search list for the DNS address.
Syntax
changeIPFQDN -IP < > FQDN < > -GATEWAY < >-NETMASK < > -DNS < > -SEARCH < >
# Option Description Usage
1 IP The new IP address of System
Manager.
changeIPFQDN -IP
10.11.12.13
2 FQDN The new FQDN of System Manager. changeIPFQDN -FQDN
a.mydomain.smgr.com
3 GATEWAY The new Gateway address of System
Manager.
changeIPFQDN -GATEWAY
10.11.1.1
4 NETMASK The new netmask address of System
Manager.
changeIPFQDN -NETMASK
255.255.203.0
5 DNS The new DNS address of System
Manager.
You an provide multiple DNS
addresses. Separate each address by
a comma.
changeIPFQDN -DNS
10.11.1.2
changeIPFQDN -DNS
10.11.12.5,10.11.12.3
6 SEARCH The new search list of domain names. changeIPFQDN -SEARCH
smgr.com
Example
You can provide options in any combination that the system supports:
changeIPFQDN -IP 10.11.y.z -FQDN a.domain.weblm.com -GATEWAY 10.11.1.1 -NETMASK
255.255.255.0 -DNS 10.11.1.2 -SEARCH platform.avaya.com
changeIPFQDN -FQDN a.domain.weblm.com -GATEWAY 10.11.1.1
changeIPFQDN -IP 10.11.y.z
Changing the IP address and FQDN in System Manager
1278 Administering Avaya Aura
products.
Configuring the firewall in System Manager
Before you begin
Start an SSH session.
About this task
The firewall rules are captured in the $MGMT_HOME/utils/bin/firewall/
ConfigureIptables.sh file.
Procedure
1. Using the command line interface, log in to System Manager as root.
2. To configure and enable the firewall, type the sh $MGMT_HOME/utils/bin/
firewall/ConfigureIptables.sh command.
Using the firewall
Before you begin
Start an SSH session.
Procedure
1. Using the command line interface, log in to System Manager as root.
2. To query the status of the firewall, type the service iptables status
command.
Firewall implementation in System Manager
1286 Administering Avaya Aura