Nortel Networks 5100 User Manual

Standard
MCS 5100 Release 4.0
Standard 01.05
Part No. NN42020-110 January 2008
System Management Console User Guide
Standard
2
Copyright © 2008, Nortel Networks. All rights reserved.
Sourced in Canada
The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks.
Nortel, Nortel (Logo), and the Globemark are trademarks of Nortel Networks. Microsoft, Windows, Windows NT, Internet Explorer, and Outlook are trademarks of Microsoft Corporation. Oracle is a trademark of Oracle Corporation. All other trademarks are the property of their respective owners.
Standard

Revision history

January 2008
Standard 01.05. This document is up-issued to support Multimedia Communication Server 5100 Release 4.0. This document addresses CR Q01812909.
April 2007
Standard 01.04. This document is up-issued to support Multimedia Communication Server 5100 Release 4.0. This document addresses CR Q01616608.
March 2007
Standard 01.03. This document is up-issued to support Multimedia Communication Server 5100 Release 4.0. This document addresses CR Q01557499.
3
January 2007
Standard 01.01. This document is issued to support Multimedia Communication Server 5100 Release 4.0. This document contains information previously contained in the following legacy document, now retired: System Management Console User Guide (NN10273-111).
January 2006
Standard 4.0. This document is up-issued for MCS 5100 Release 3.5. Some referenced document numbers changed.
November 2005
Standard 3.0. This document is up-issued for MCS 5100 Release 3.5.
November 2005
Standard 2.0. This document is up-issued for MCS 5100 Release 3.5.
System Management Console User Guide
Standard
4
October 2005
Standard 1.0. This document is up-issued for MCS 5100 Release 3.5.
NN42020-110 MCS 5100 Release 4.0 Standard 01.05 January 2008
Standard

Contents

New in this release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Feature changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Base OAMP supportability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
CallP checkpointing support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Complete re-IP support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
IBM core hardware introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
MAS OAM/fault integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Password management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
SIP Denial of Service mitigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
SSL for web and SOAP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
System Management Console dual NIC PC support . . . . . . . . . . . . . . . . . . . . . . 14
IPCM profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Other changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
How this guide is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
System Management Console—getting started . . . . . . . . . . . . . . . . . . . . . 19
System Management Console overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
System Management Console installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installing the System Management Console for the first time . . . . . . . . . . . . . . . . 21
Uninstalling the System Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Upgrading the System Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
System Management Console log on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
System Management Console User Guide
Standard
6
Logging on to the System Management Console . . . . . . . . . . . . . . . . . . . . . . . . . 23
System Management Console navigation . . . . . . . . . . . . . . . . . . . . . . . . . . 25
System Management Console layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Title bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Icon tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Alarm summary bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Refreshing the work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Refreshing the configuration, logical and physical views . . . . . . . . . . . . . . . . . . . . 29
Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Logical view window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Physical view window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Logical and physical view icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Network Data configuration and management . . . . . . . . . . . . . . . . . . . . . . 33
License key management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Licence key updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Updating a license key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Querying a license key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Configuring an IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Deleting an address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Component re-IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Editing the address table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
SNMP Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuring an SNMP profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Deleting an SNMP profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Physical sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Configuring a site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Deleting a site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
External nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Configuring an external node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
NN42020-110 MCS 5100 Release 4.0 01.05 January 2008
Standard
7
Deleting an external node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Informational elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring an informational element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Deleting an informational element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Cipher suites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configuring cipher suite usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Subnet masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configuring a subnet mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Deleting a subnet mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Static routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configuring a static route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Deleting a static route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
OAM profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
OSS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Record format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Configuring a log record format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Configuring an OM record format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configuring an Accounting record format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
File Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Adding a file type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Format path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuring a log format path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuring an OM format path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring an accounting format path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
FTP Push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Creating an FTP Push profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Pushed file directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
SNMP Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Adding an SNMP manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Server configuration and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Server configuration and management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configuring a server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Deleting a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Server performance statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
System Management Console User Guide
Standard
8
Monitoring a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Configuring server alarm thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Database configuration and management . . . . . . . . . . . . . . . . . . . . . . . . . 61
Viewing the database monitor status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Configuring resource thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Network element configuration and management . . . . . . . . . . . . . . . . . . . 63
Network element configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Network element configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Adding a network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Network element modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Modifying a whole network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Modifying a network element instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Modifying configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Deleting a network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Network element software updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Updating network element software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Network element management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Stopping a network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Starting a network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Restarting a network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Killing a network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
MCS system without a BCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configuring Session Manager parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
MAS OAM fault integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Configuring a MAS to FPM association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
IPCM profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
IPCM profile configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Configuring IPCM profile parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
IPCM profile server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Configuring an IPCM profile server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Verifying firmware codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Media Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Upgrade the Media Gateway firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Checking the Media Gateway firmware version . . . . . . . . . . . . . . . . . . . . . . . 78
NN42020-110 MCS 5100 Release 4.0 01.05 January 2008
Standard
9
Upgrading the Media Gateway firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Alarm browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Alarm browser fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Alarm information displayed in the browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Alarm browser operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Viewing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Viewing alarm details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Sorting alarms based on alarm attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Copying alarm information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Clearing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Refreshing alarm information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Log browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Log browser fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Log browser operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Starting the log browser from the configuration view . . . . . . . . . . . . . . . . . . . . . . . 89
Starting the log browser from the logical or physical view . . . . . . . . . . . . . . . . . . . 89
Clearing log details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Saving logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Log file rotation period configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Dual NIC PCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Operational measurements browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Operational measurements browser fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
OM browser operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Starting the OM browser from the configuration view . . . . . . . . . . . . . . . . . . . . . . 93
Starting the OM browser from the physical or logical view . . . . . . . . . . . . . . . . . . 93
Viewing register information of a specific OM group . . . . . . . . . . . . . . . . . . . . . . . 93
Saving OM data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Refreshing data in the OM browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
OM file rotation period configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
OM interval period configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Administrator tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
User administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Adding or modifying an administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
System Management Console User Guide
Standard
10
Deleting an administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
System Manager password reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Role administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Adding or modifying a role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Deleting a role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Viewing and forcing off users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
User password rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Configuring password complexity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Database export and import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Exporting the password and properties for an SMC user . . . . . . . . . . . . . . . . . . 103
Importing the password and properties for an SMC user . . . . . . . . . . . . . . . . . . 104
Provisioning Client interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Starting the Provisioning Client interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Provisioning Client failed authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Configuring failed authentication parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Message of the day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
HTTP Denial of Service mitigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Enabling HTTP DoS mitigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
HTTP DoS engineering parameter group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Configuring HTTP DoS mitigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
SIP Denial of Service mitigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Enabling SIP DoS mitigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
SIP DoS engineering parameter group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Example using the default values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Configuring SIP DoS mitigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Trusted node configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Configuring trusted nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Overload Engineering parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Configuring call queue thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
System Management Console connection is lost . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Font problems in System Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Removing PS fonts from a workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
NN42020-110 MCS 5100 Release 4.0 01.05 January 2008
Standard

New in this release

The following sections describe what is new in this document for Multimedia Communication Server (MCS) 5100 Release 4.0.

Feature changes

The following features affect this document:
“Base OAMP supportability” on page 11
“CallP checkpointing support” on page 12
“IBM core hardware introduction” on page 12
“MAS OAM/fault integration” on page 12
“Password management” on page 13
“SIP Denial of Service mitigation” on page 13
“System Management Console dual NIC PC support” on page 14
“IPCM profile” on page 14
11
The following sections describe the feature changes for this release.

Base OAMP supportability

The Base Operations, Administration, Maintenance, and Provisioning (OAMP) supportability feature enhances the support and hardware configuration of the Multimedia Communication Server (MCS) 5100 product. The feature includes the following benefits:
shared network data
consolidated configuration data
consolidated software to reduce memory requirements
ability to configure additional Accounting Managers (AM), and Fault and Performance Managers (FPM)
System Management Console User Guide
Standard
12
Consequently, the System Management Console graphical user interface (GUI) layout is different. The application area replaces the general information area (GIA). The system tree pane is replaced by the navigation pane.

CallP checkpointing support

The CallP checkpointing support feature ensures that SIP messaging for calls remain synchronized, and that essential cached data is available if a standby server must become active. By remaining synchronized, call information is preserved during call failover. With this feature, the standby server can be a hot standby.

Complete re-IP support

With the Complete re-IP support feature, you do not need to reinstall the server software after you change various server identification parameters, such as country, time zone, and IP address.

IBM core hardware introduction

This feature introduces the IBM x306m hardware for all the core MCS servers. The Sun Fire V100, V210, and Netra 240 servers are not supported on Release
4.0.

MAS OAM/fault integration

The Media Application Server (MAS) Operations, Administration, and Maintenance (OAM) fault integration feature provides the integration of the log and alarm notifications from the MAS into the MCS Fault and Performance Manager (FPM). After you provision the MAS servers on the MCS system, the management server can receive logs and alarms from the MAS, which increases the visibility of MAS problems.
After the FPM restarts, it queries the alarm state of each MAS server configured on the MCS and reflects the state of each server on the System Management Console. Configuration of the FPM to request periodic updates to the MAS alarm state is provided, to ensure synchronization between the MCS and MAS.
Standard
13
With this feature you can use the System Management Console to view Media Application Server alarms and logs.

Password management

This Password management feature provides encryption of subscriber and administrator passwords, password complexity rules, and password enforcement. The system stores all passwords in an encrypted format for improved security. Password policies provide the ability to configure a default subscriber password and to enforce password changes. Complexity rules and password enforcement rules govern Administrator passwords.

SIP Denial of Service mitigation

The SIP Denial of Service mitigation feature provides a mechanism to protect the call server from Denial of Service (DoS) attacks. The feature protects the call server from wasting computing resources due to SIP messaging that exceeds the configured threshold. Statically configure the IP addresses of the SIP servers to maintain Domain Name System (DNS) lookup advantages.

SSL for web and SOAP interface

This feature provides the following benefits:
increased security for the MCS Provisioning Client and Personal Agent (PA)
separation of the Personal Agent from the Provisioning Client
protection mechanisms that defend against brute force and dictionary password attacks
This feature increases security in the MCS Provisioning Client and Personal Agent by adding Hypertext Transfer Protocol (HTTP) over Transport Layer Security (HTTPS) support for all Web transactions. The Provisioning Client and Personal Agent use different Web server ports to implement generic routing Access Control Lists (ACL).
Additional PAs, separate from Provisioning Clients and running on different servers, are supported. You can configure additional PAs, depending on the number of subscribers.
System Management Console User Guide
Standard
14
The protection mechanisms provide
temporary locking of subscriber or administrator accounts after the configured number of failed authorization attempts
temporary blocking of HTTP or HTTPS requests from a particular source after a configurable request-rate threshold is exceeded.

System Management Console dual NIC PC support

The System Management Console dual NIC PC support feature supports log browsing functionality at the System Management Console (SMC) if the PC has two Network Interface Cards (NIC).

IPCM profile

With the IPCM profile feature, you can upgrade Nortel IP Phones 2004 that have Unistim firmware to session initiation protocol (SIP) firmware.

Other changes

This section describes other technical changes for this release.
The AudioCodes Mediant 2000 is now called the Media Gateway.
Java Web Start technology supports the installation, start, and update of the System Management Console.
This document is renumbered from NN10273-111 to NN42020-110.
Standard

Introduction

This guide provides instructions for using the System Management Console. The System Management Console is the interface used to configure, monitor, and manage the Multimedia Communications Server (MCS) component hardware and software.
The System Management Console interacts with the MCS system hardware and software components through the System Manager. The tasks described in this guide are generic and do not include specific information for any one component.
The topics in this chapter include:
“How this guide is organized” on page 15
“Audience” on page 16
“Text conventions” on page 16
“Acronyms” on page 16
“Related publications” on page 17
“How to get help” on page 18
15

How this guide is organized

This guide is organized as follows:
“System Management Console—getting started” on page 19
“System Management Console navigation” on page 25
“Network Data configuration and management” on page 33
“Server configuration and maintenance” on page 55
“Database configuration and management” on page 61
“Network element configuration and management” on page 63
“Alarm browser” on page 81
“Log browser” on page 87
System Management Console User Guide
Standard
16
“Operational measurements browser” on page 91
“Administrator tools” on page 95
“Troubleshooting” on page 115

Audience

This guide is intended for administrators who use the System Management Console to manage the MCS system component hardware and software.

Text conventions

This guide uses the following text conventions:
bold text Indicates a menu option, link, or command key you need
to click. Examples: Click Apply
italic text Indicates a document title
Example: MCS 5100 Overview (NN42020-143)
<ElementName> Indicates a configured element name in the GUI tree
Example: <ApplicationServerName>
separator > Indicates a menu path
Example: Configuration > Query

Acronyms

This guide uses the following acronyms:
BPS Business Policy Switch
GUI graphical user interface
IP Internet protocol
IPCM IP Client Manager
Standard
17
Mbyte megabyte
MCS Multimedia Communications Server
MCP Multimedia Communications Portfolio
MO managed object
NE network element
OAM Operations, Administration, Maintenance
OEM Oracle Enterprise Manager
OM operational measurement
PRI primary route interface
RAM random access memory
RTP Real-Time Protocol
SIP Session Initiation Protocol
SNMP Simple Network Management Protocol
UAS Universal Audio Server
UFTP UNIStim File Transfer Protocol
URL uniform resource locator (Internet address)
XML EXtensible Markup Language

Related publications

For more information, see the following publications:
Alarm and Log Reference (NN42020-703)
Database Manager Fundamentals (NN42020-142)
IP Client Manager Fundamentals (NN42020-106)
Operational Measurements Reference (NN42020-704)
Provisioning Client User Guide (NN42020-105)
MCS 5100 Overview (NN42020-143)
MCS Installation and Commissioning (NN42020-308)
MCS Upgrades—Maintenance Releases (NN42020-303)
System Manager Fundamentals (NN42020-109)
System Management Console User Guide
Standard
18

How to get help

For service issues, contact your local support or Information Services team.
Standard
System Management Console—getting started
The topics in this chapter include:
“System Management Console overview” on page 19
“System Management Console installation” on page 19
“System Management Console log on” on page 22

System Management Console overview

Use the System Management Console to interact with the element manager (System Manager) of the MCS software and hardware. The System Management Console is a Java-based graphical user interface (GUI) that operates on a personal computer (PC) that runs a supported Microsoft Windows operating system. Use the System Management Console to
administer system, database, and service components
deploy and configure system sites, servers, components, and component services
monitor system using alarms, logs, and performance measurements
manage collection of operations, administration, and maintenance information
19
Note: The System Management Console only supports the display of
the English language.

System Management Console installation

Install the System Management Console on administrator workstations (management PCs) during system deployment. The System Manager must be deployed and operational before you can connect to the System Management Console.
System Management Console User Guide
Standard
20
The System Management Console installation uses Java Web Start technology.
You can install only one version of the System Management Console on a workstation. During installation of the System Management Console, the Java Machine uses the JNLP file to obtain version information.
The System Management Console version must correspond to the load version that you are installing. You can view the current System Management Console version by selecting Help > About MCP System Management Console. Before deploying software upgrades, you must upgrade the System Management Console to the equivalent version. Each time you start the System Management Console, the system automatically checks for and applies updates.
For more information, see the following topics:
“System requirements” on page 20
“Installing the System Management Console for the first time” on page 21
“Uninstalling the System Management Console” on page 22
“Upgrading the System Management Console” on page 22

System requirements

Nortel recommends that the management PC meet the following requirements.:
Table 1 Management PC requirements
Category Minimum requirements Recommended requirements
Processor 600 MHz Pentium-class or
equivalent processor
Free RAM 64 MB of RAM
This requirement is in addition to the memory requirements of the operating system and other concurrent applications.
Free hard disk drive space
Mouse Required Required
Video graphics card
Sound card not applicable not applicable
50 MB 50 MB
640 x 480 @8bpp [256 colors] VGA 800 x 600 @16bpp [65,536 colors]
1.0 GHz (or higher) Pentium-class or equivalent processor
64 MB of RAM This requirement is in addition to
the memory requirements of the operating system and other concurrent applications.
VGA or better
Standard
Table 1 Management PC requirements
Category Minimum requirements Recommended requirements
21
Operating systems
Network connectivity
Internet browsers
Java Sun Java 1.4.9 Sun Java 1.4.9 or higher
Cookies Enabled Enabled
Javascript Enabled Enabled
Microsoft Windows 98(SE)/ME/ 2000/XP/
Microsoft Windows NT 4.x with Service Pack 5 (SP5)
56 Kbps modem 10Base-T or other fast network
Netscape Communicator 7.0 Microsoft Internet Explorer 6.0
Microsoft Windows 2000/XP/ 98(SE)
Microsoft Windows NT 4.x with Service Pack 5 (SP5)
connection (DSL, Cable, LAN, etc.)
Netscape Communicator 7.1 or greater
Microsoft Internet Explorer 6.0 or greater
If you use a Proxy server in Java network settings, this Proxy server must allow access to the IP Address & port. If there is no access to the IP Address & port, use Direct Connection in the Java network settings.

Installing the System Management Console for the first time

1 On the workstation, open Internet Explorer (IE).
2 In the IE address bar, enter the following:
HTTP://<IP address>:12120
where <IP address> is the IP address of the System Manager (SM) or SM service IP.
The <IP>/index.html page load in the browser.
3 Click the Launch MCP Management Console link.
The System Management Console installs automatically. After the installation is complete, a log on window appears.
System Management Console User Guide
Standard
22

Uninstalling the System Management Console

1 Start javaws.exe.
2 Select the MCP Management Console and click Remove Selected
Application.

Upgrading the System Management Console

The System Management Console automatically updates (if required) each time you start it.

System Management Console log on

Only individuals with defined administrative roles have access to the system through the System Management Console. Which menu options are available depends on the role of the administrator and the system architecture. The three administrator roles are:
general administrator
General administrators have management console access to configure servers, components, and services. They can monitor operations and maintenance information, and provision end-user information.
database administrator
Database administrators can log on to the Oracle Enterprise Manager and use the management tools to perform database administration tasks. In addition, they have management console access which lets them perform the same tasks as general administrators.
system administrator
The system administrator is the system superuser assigned during the initial deployment. System administrators have access rights to all component modules, and are responsible for adding and defining the roles of other administrators. The system administrator has access to all tasks and tools available through the System Management Console.
To configure System Management Console rights, select Administrator > Role administrator.
Use the Provisioning client to add administrators and configure rights for provisioning. For additional information about adding administrators and defining administrator roles, see the Provisioning Client User Guide (NN42020-105).
Use the Oracle Enterprise Management (OEM) Console to add administrators and configure database administration rights. For more information, see Database Manager Fundamentals (NN42020-142).

Logging on to the System Management Console

1 From the workstation, start the System Management Console.
The log on dialog box opens.
2 Enter the required log on information
Log on information fields include the following:
User ID: the user name of the administrator
Current Password: the administrator’s password
Server: the logical IP address of the System Manager component
Force Out check box: (optional) if selected, the user’s session ends
Standard
23
3 Click OK.
4 To terminate a session, from the System Management Console menu bar,
select File > Exit.
System Management Console User Guide
Standard
24
Standard

System Management Console navigation

The topics in this chapter include:
“System Management Console layout” on page 25
“Refresh” on page 28
“Views” on page 29

System Management Console layout

The System Management Console (SMC) uses the familiar Windows layout. Like other Windows applications, the SMC consists of the title bar on the top, the menu bar, and an icon-based toolbar. Under the icon-based toolbar, an alarm summary indicates the status of the network elements in the MCS system. Below the alarm summary are the configuration view in the left pane and the work area in the right pane.
25

Title bar

The title bar indicates the following items:
the application—MCP System Management Console
the software version of the System Manager
login user name
IP address of the System Manager

Menu bar

Use the menu bar to access to File, Views, Administration, Tools, and Help menus. Menu items provide access to functions not accessible from the GUI tree pane.
System Management Console User Guide
Standard
26
Not all menu options are available for every component or server. Unavailable menu options appear dimmed.
This guide discusses menu options with the related procedures.
Note: You can access available menu options for an element that is selected in the GUI tree by right-clicking to open the shortcut menu.

Icon tool bar

The icons on the tool bar are button shortcuts to the record browsers and the refresh button. Not all tool bar options are available for every component or server. Dimmed icons are unavailable for the element selected in the GUI tree.
The tasks associated with the tool bar options are described in the relevant sections of this guide.
Figure 1 System Management Console tool bar icons
As shown in Figure 1 “System Management Console tool bar icons” on page 26, the icons from left to right are:
•Alarm browser
•OM browser
Log browser
Logical view
•Physical view
Refresh

Alarm summary bar

This narrow horizontal bar, located below the toolbar, provides a concise system­wide summary of alarms for managed and monitored MCS network elements. The background color of the alarm bar (green, yellow, orange, or red) indicates the most severe alarm (none, minor, major, or critical) for the system. You can see the total number of alarms for the system, as well as the number of alarms of each severity level.
For information about alarms, see Alarm and Log Reference (NN42020-703).

Configuration view

The configuration view appears in the left pane of the System Management Console. After you select a leaf node in the tree, a new window appears in the application area in the right pane. You can collapse and expand the tree structure.
Information is organized into four sections:
Network Data and Mtc: Use this section to define information such as IP addresses, log report formats, OSS servers, and other data that does not change often, but is reused during other configuration tasks. Enter the data in this section to avoid retyping, and typing errors, during other configuration tasks. Use this section to manage License keys for activating features.
Servers: Use this section to configure servers and to monitor their hardware and operating systems.
Databases: Each Database has a folder. The folder contains software load and configuration data so that the System Manager can connect to the database. The System Manager can then distribute database connection information to other network elements that need database access.
Network Elements: Use this section to configure all managed and monitored MCS network elements. Each network element type has a folder, and each configured network element has a subfolder. After you select a network element folder, the Alarm Browser, OM Browser, and Log Browser icons become active for that network element. Use this section to make changes to load deployment; configuration parameters; om, log, and accounting record configuration. Use this section to perform maintenance tasks, such as start and stop, for network elements.
Standard
27
System Management Console User Guide
Standard
28

Work area

Locate the work area in the right pane of the System Management Console. After you select a node from the configuration view pane, a window appears in the work area. Windows in the work area display information about the selected node. The information displayed in the work area is described with the respective configuration view level in subsequent chapters. Some configuration view nodes (Network Data and Mtc and Network Elements) have no associated windows.
Windows that appear in the work area have the following buttons.
Add: Use this button to add an element.
Edit: Use this button to make changes to an existing element.
Delete: Use this button to remove an existing element.
Refresh: Use this button to update the information in the window. For more information, see “Refreshing the work
area” on page 29.
Use the work area to view and manage multiple windows. Windows in the work area can be moved, resized, or closed.

Refresh

Use the Refresh to update the information displayed in the work area of the System Management Console. Refresh is available for all levels of the GUI tree, except the logical nodes of Sites, Server, and Components.
The Refresh tool is not normally required because the System Management Console updates automatically after an event occurs.
Standard

Refreshing the work area

Use the following procedure to manually refresh the information displayed by windows in the work area.
1 From the System Management Console GUI tree, select system, a site, a
server, a component, or service.
2 On the corresponding window that appears in the work area, click Refresh
Figure 2 Refresh button.

Refreshing the configuration, logical and physical views

The Refresh tool also refreshes the configuration, logical view, and physical view windows of the System Management Console. After you click Refresh, the tool queries the System Manager for the latest topology information and updates this information on the System Management Console.
29

Views

To refresh the configuration, logical and physical views, select Too l s > R ef r e sh , or click the Refresh icon in the tool bar.
The trees in the configuration view and logical and physical view windows collapse. The system updates the data to display the latest topology information.
The logical and physical view windows organize network elements by element type and location, respectively. You can use these windows to diagnose fault conditions.
System Management Console User Guide
Standard
30

Logical view window

The logical view window provides a graphical view of the network elements (NE), servers, and the logical databases. In this view, you cannot determine which network elements are deployed on which servers.
Using this view, you can see the alarm conditions for all equipment for each NE type. Select an NE instance to enable the alarm, log and OM browser buttons for that element.
Open the logical view window by right-clicking on the alarm summary area, or by clicking the logical view window icon in the icon toolbar.
Figure 3 Logical view icon

Physical view window

The physical view window provides a graphical view of the MCS system. The elements are organized by site and server, and then by the network element applications deployed on the server.
Using this view, you can view alarm conditions for all monitored equipment in each site. Select a network element to enable the alarm, log, and OM browser buttons for that element.
Open the physical view window by right-clicking on the alarm summary area, or by clicking the physical view window icon in the icon toolbar.
Loading...
+ 88 hidden pages