Standard MCS 5100 Release 4.0 Standard 01.05 Part No.
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.
Standard 3 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.
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.
Standard 5 Contents New in this release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Feature changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Base OAMP supportability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 CallP checkpointing support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Complete re-IP support . .
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standard 7 Deleting an external node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Informational elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Configuring an informational element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Deleting an informational element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Cipher suites . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . . .
Standard 10 Deleting an administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 System Manager password reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Role administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Adding or modifying a role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Privileges . . . . . . . .
Standard 11 New in this release The following sections describe what is new in this document for Multimedia Communication Server (MCS) 5100 Release 4.0.
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.
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.
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.
Standard 15 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.
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.
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 locato
Standard 18 How to get help For service issues, contact your local support or Information Services team. NN42020-110 MCS 5100 Release 4.0 Standard 01.
Standard 19 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.
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.
Standard 21 Table 1 Management PC requirements Category Minimum requirements Recommended requirements Operating systems Microsoft Windows 98(SE)/ME/ 2000/XP/ Microsoft Windows NT 4.x with Service Pack 5 (SP5) Microsoft Windows 2000/XP/ 98(SE) Microsoft Windows NT 4.x with Service Pack 5 (SP5) Network connectivity 56 Kbps modem 10Base-T or other fast network connection (DSL, Cable, LAN, etc.) Internet browsers Netscape Communicator 7.0 Microsoft Internet Explorer 6.0 Netscape Communicator 7.
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.
Standard 23 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).
Standard 24 NN42020-110 MCS 5100 Release 4.0 Standard 01.
Standard 25 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.
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.
Standard 27 Alarm summary bar This narrow horizontal bar, located below the toolbar, provides a concise systemwide 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.
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.
Standard 29 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.
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.
Standard 31 Figure 4 Physical view icon Logical and physical view icons For both view windows, a green dot indicates that the state of the network element or server is clear. A yellow, orange, or red triangle indicates an alarm. If the bar icon in the triangle is horizontal, it indicates a minor alarm. An angled bar indicates a major alarm; a vertical bar indicates a critical alarm. A blue triangle that does not have a bar indicates a warning.
Standard 32 NN42020-110 MCS 5100 Release 4.0 Standard 01.
Standard 33 Network Data configuration and management The topics in this chapter include: • “License key management” on page 33 • “Addresses” on page 35 • “SNMP Profiles” on page 38 • “Physical sites” on page 39 • “External nodes” on page 40 • “Informational elements” on page 41 • “Cipher suites” on page 42 • “Subnet masks” on page 43 • “Static routes” on page 43 • “OAM profiles” on page 44 License key management Updating and querying license keys requires an administrative role with LicenseKeyService pri
Standard 34 • • Licenseable Units: This tab shows licenseable units that are always enabled and have a limit restricting their use. Network Elements: This tab shows the network elements that do not have ports or endpoints associated with them in the licensekey. The tab shows the number of these network elements that can be configured in the system as well as the type and number of configured network elements. . Note: The Network Elements tab does not show information about servers.
Standard 35 Updating a license key Administrators update license keys by selecting Network Data and Mtc > Licensekey in the configuration view of the System Management Console. The License Key can be updated dynamically without any disruption of service. The update rolls back if the License Key update procedure fails. 1 In the System Management Console, from the configuration view, select Network Data and Mtc > Licensekey. 2 Click the Edit button at the Licensekey window.
Standard 36 Before you add a server to the MCS network, you must add the server IP address, in the Addresses window and associate a Logical Name with that IP Address. You cannot delete an IP address if a third-party Trusted Device, Gateway, Operations Support System (OSS) Server, or server that hosts an MCS network element is configured against the Logical Name for that IP address. You can change the IP address, but services are interrupted.
Standard 37 Component re-IP The MCS software components belong to three broad categories based on their interactions with the System Manager: • Managed: The System Manager manages the core MCS components, such as the Accounting Manager, IP Client Manager, Database, Provisioning Manager, and Session Manager. • Monitored: Some components are monitored, but not managed, by the System Manager. These components can be running on a server that does not support re-IP.
Standard 38 2 Select Network Data and Mtc > Addresses. 3 Select and modify or delete an address, or add an address, and click Apply. 4 Confirm the changes. SNMP Profiles The System Manager uses simple network management protocol (SNMP) profiles to access (query) SNMP agents on network elements. You can access or create SNMP Profiles by selecting Network Data and Mtc > SNMP Profiles from the navigation pane. To perform SNMP profile configuration, you must have SnmpProfileService privileges.
Standard 39 1 Select Network Data and Mtc > SNMP Profiles from the navigation pane. 2 Click Add or select an entry and click Edit. 3 In the Server SNMP Profiles dialog box, enter the configuration data. 4 Click Apply. Deleting an SNMP profile. Note: Before deleting an SNMP Profile, edit any servers that use the profile and configure the servers to use a different SNMP Profile. 1 Select an entry from the SNMP Profiles window. 2 Click Delete. 3 Click OK to confirm the delete.
Standard 40 3 In the Site dialog box, enter the configuration data. Table 2 Site configuration Field Value Description Site name alphanumeric (1-20 characters) a unique name identifying the site Zone alphanumeric (1-3 characters) UTM zone location of this site Easting integer (1-1 000 000 digits) Easting of the site For numbers greater than 1 100, do not enter spaces. Northing integer (1-7 digits) Northing of the site 4 Click Apply.
Standard 41 3 In the Add Trusted Device dialog box, enter the configuration data: • • 4 Name—Enter the name of the device, such as MAS110. DeviceAddress—Use the drop-down list to select the address of the device. Click Apply. Deleting an external node 1 Select an entry on the External Nodes window. 2 Click Delete. 3 Click Yes to confirm the delete. Informational elements To configure this data you must have InfoElementService privileges.
Standard 42 • 4 SIP Transport: SIP Transport type Click Apply. Deleting an informational element 1 Select an entry on the Informational Element window. 2 Click Delete. 3 Click Yes to confirm the delete. Cipher suites Use cipher suites to configure the encryption used for communication between the System Manager and the MCS network elements. To configure cipher suites, you must have CipherSuiteService privileges. You do not add cipher suites to the MCS system; you enable or disable them.
Standard 43 Subnet masks Subnet Masks are only required for the RTP Media Portal (renamed to Border Control Point 7000 Series). Subnet Masks provide greater flexibility in defining IP addresses for the Media Portal Service Cluster and define the scope of an address space. This information is used to scope the extent of the service-planes in the “Media Portal Cluster” data structure and to define static routes in separate datafill.
Standard 44 Configuring a static route Use the following procedure to add or edit a Static Route entry. 1 In the System Management Console, from the navigation pane, select Network Data and Mtc > Media Portal Data > Static Routes. 2 Click Add or select an entry and click Edit. 3 In the Add Static Routes dialog box, enter the configuration data. 4 In the Add Static Routes dialog box, provide a Static Route Name to uniquely identify this static route.
Standard 45 OSS server Use the OSS server to send alarms, logs, OMs, and accounting record information to a northbound OSS, which is the OSS destination. Open the OSS server window by selecting Network Data and Mtc > OAM Profiles > OSS Server from the configuration view of the System Management Console. Before configuring an OSS server, you must add the IP address for the server in the Addresses window. To perform operations in the OSS Server window, you must have OssProfileService privileges.
Standard 46 3 In the Log Record Format dialog box, enter the configuration data. Table 3 Log record format configuration Field Value Description Name string, 1 to 32 characters This field identifies this profile. This value is used to create a Format Path for log reports, for example, MCPO, std., or scc2. Type STD, MCP, or SCC2 STD is Nortel standard format. MCP is an extension of STD and offers log identifiers that are longer than four characters, as well as long lines.
Standard 47 1 In the System Management Console, from the configuration view, select Network Data and Mtc > OAM Profiles > Record Format > Accounting Record Format. 2 Click Add or select an entry and click Edit. 3 In the Accounting Data Format dialog box, enter a Name for the format, such as acct. 4 Select MCPV3 or MCPV4 for the Type. 5 Click Apply. File Type The File Type folder contains configuration data for all OSS file types, such as FLATFILE, MCP3IPDRXML, or MCP4IPDRXML.
Standard 48 Table 4 File type configuration Field Value Description Rotation rule string This creates a rule for closing active files and opening new files. Rules are based on time (interval or a specific hour and minute) and optionally by size (in kilobytes): EVERY n | AT hh:mm AM|PM OR SIZE m EVERY n - This keyword indicates to rotate a file at a specific interval in minutes, such as 60. AT hh:mm AM|PM - This keyword indicates to rotate a file at a specific time each day, such as 06:00 AM.
Standard 49 3 In the Log Format Path Profile dialog box, enter a name, and then select a Data Format and File Type. The options for Data Format and File Type depend on information previously entered for Log Record Format and File Type. For example, enter the name mcp-file if the Data Format is mcp and the File Type is file. 4 Click Apply. The Log Format Path Profile dialog box closes and an entry appears in the Log Format Path window.
Standard 50 3 In the Accounting Format Path Profile dialog box, enter a name, and then select a Data Format and File Type. Options for Data Format and File Type depend on previous configuration data. For example, enter a name of mcp4-ipdr4 if the Data Format is mcp4 and the File Type is ipdr4. 4 Click Apply. The Accounting Format Path Profile dialog box closes and an entry appears in the Accounting Format Path window. Use this data to configure the Standard Accounting Stream for an Accounting Manager.
Standard 51 3 In the FTP Push Profile dialog box, enter the configuration data. Table 5 FTP Push profile configuration Field Value Description Name string, 1 to 32 characters Enter a name to identify this profile. This value is needed to associate this profile with an FTP Push log, OM, or accounting stream. Server drop-down menu selection Select a configured OSS Server from the drop-down menu. An OSS Server must be configured before performing this procedure.
Standard 52 • • ne—This identifies the network element instance that gathered the data, such as SM_x, FPM_x, or AM_x. monitored_nes—Directories are created for each network element instance that is monitored by this System Manager, Fault-Performance Manager, or Accounting Manager. For example, if System Manager instance 0 (SM_0) is responsible for collecting logs from Accounting Manager instance 0 (AM_0), and the records are transferred, the log files are placed in the following location: ...
Standard 53 3 In the Add SNMP Manager dialog box, enter the configuration data. Table 6 SNMP manager configuration Field Value Description Name string, 1 to 32 characters This field identifies the SNMP Manager profile. This value is used to associate this SNMP Manager profile with the System Manager or a Fault-Performance Manager. Community string This field indicates the community string that the SNMP trap daemon on the OSS server is configured to accept.
Standard 54 NN42020-110 MCS 5100 Release 4.0 Standard 01.
Standard 55 Server configuration and maintenance The topics in this chapter include: • “Server configuration and management overview” on page 55 • “Server configuration” on page 56 • “Server performance statistics” on page 58 Server configuration and management overview The addition of new servers and server configuration typically occurs during installation and commissioning. The number, type, and redundancy of servers depends on the specific network configuration.
Standard 56 Server configuration To perform operations with server data, you must have PhysicalServerService, PhysicalSiteService, IPAdddressService, and SnmpProfileService privileges. Configuring a server. Note: If you modify an operational server, you affect services deployed on that server. 1 In the System Management Console, from the configuration view, select Servers. 2 Click Add or select an entry and click Edit. 3 In the Server dialog box, enter the configuration data.
Standard 57 Table 7 Server configuration data Field Value Description Operating System drop-down This field is used for SNMP polling. If this field is configured to windows, memory information will not be polled from the server. This field must not be configured to windows. This field is also used to determine file paths. Server Type drop-down Use this field to specify the server type: Bladeserver, CC3310, or Other. SNMP Profile drop-down Select the name of an SNMP profile.
Standard 58 Server performance statistics After you enter server configuration data through the System Management Console, one of the parameters is SNMP Profile. To monitor the performance statistics for the server, you must use the System Management Console to start the server monitor. Before the monitor starts, a grey down arrow icon is associated with the server in the Logical and Physical View windows.
Standard 59 Configuring server alarm thresholds To configure server alarm thresholds you must have ServerMonitorConfigService privileges. Note: If the monitor is running and no statistics appear on the monitor window, check the Logical or Physical View window for a major SRVR101 alarm against the server. This alarm indicates that the SNMP daemon on the server is not responding. Verify that the server is running, and then verify the configuration data related to the SNMP Profile associated with the server.
Standard 60 NN42020-110 MCS 5100 Release 4.0 Standard 01.
Standard 61 Database configuration and management The topics in this chapter include: • “Viewing the database monitor status” on page 61 • “Configuring resource thresholds” on page 62 You configure and deploy the database when you install and commission it. After you commission the database, the only database operation you perform from the System Management Console is monitoring the database.
Standard 62 Configuring resource thresholds To perform this procedure you must have DBMonitorConfigService privileges. Use the following procedure to configure thresholds for the database monitor control, after a DBMN401 alarms occur. 1 In the System Management Console, from the configuration view, select Database > mcpdb > Monitor. 2 In the mcpdb_x Database Instance Monitor window, click Configure Thresholds. The DB Monitor Alarm Threshold Configuration window appears.
Standard 63 Network element configuration and management The topics in this chapter include: • “Network element configuration overview” on page 63 • “Network element configuration” on page 63 • “Network element software updates” on page 69 • “Network element management” on page 71 • “MCS system without a BCP” on page 73 • “MAS OAM fault integration” on page 74 • “IPCM profile” on page 75 Network element configuration overview Administrators add, configure, and manage most network elements by using the Sys
Standard 64 The network elements you can add to a specific server depend on the system architecture and operational requirements. Refer to the individual network element guides for specific details related to network element configuration. The following procedures are generic and do not apply to any specific network element application. For specific configuration details and service property descriptions, see the individual network element guides.
Standard 65 7 In the Add Instance dialog box, use the drop-down menus to associate a server, a software load, and an engineering profile with the instance. The engineering profile controls the initial size of the Java Virtual Machine and establishes engineering parameters appropriate for the hardware capabilities of the server. 8 Click Apply on the add instance dialog box.
Standard 66 The time required to complete the installation and activation depends on the network element type and the hosting server. Network element modification Network elements can be modified in several ways: • modify a whole network element: Use this option to modify the base port of a network element application, to associate a different Fault-Performance Manager with the network element, and to modify many options that are specific to each network element type.
Standard 67 Modifying a network element instance. Caution: Before performing this procedure, contact your next level of support. Engineering parameters must not be modified in the field. Modifying the engineering parameters for a network element instance can reduce the performance and services of the network element.
Standard 68 8 Click OK to confirm the warning. You must manually restart for the changes to take effect. For information on how to perform a manual restart, see the documentation for the particular network element type. Modifying configuration parameters Every network element type has some configurable operating parameters. Which parameters can be configured, depends on the network element type. To perform this procedure you must have ConfigParmService privileges.
Standard 69 3 Click Yes to confirm the Stop. The network element instance state changes to DEACTIVATING, DISCONNECTED, and then OFFLINE. 4 From the Maintenance window, select each network element instance and click Undeploy. The network element instance state changes to CONFIGURED. 5 From the configuration view, select Network Elements > > > Instance, to view a list of the configured network element instances for this network element.
Standard 70 Updating network element software To perform this procedure, you must have NEInstanceService privileges 1 In the System Management Console, from the configuration view, select Network Elements > > > NE Maintenance. The Maintenance window opens in the work area. 2 From the Maintenance windows, select the STANDBY instance for redundant network elements, or the only instance for simplex network elements and click Stop. 3 Click Yes. to confirm the Stop.
Standard 71 Network element management Administrators use Start, Stop, and Restart operations to modify the configured properties of network elements. After a network element instance stops, the state changes to OFFLINE and services become unavailable. Starting, stopping, and restarting a network element instance require an administrative role with NEInstanceService privilege.
Standard 72 Starting a network element A Start operation starts the processes of a network element instance on a server. Software must be deployed to the server before the network element instance can be started. A network element instance in the state of OFFLINE has software deployed and is stopped.
Standard 73 Killing a network element The Kill operation stops the MCS software that is running on the network element instance; the operating system continues to run. The instances terminates immediately and there is no system cleanup prior to shutdown. Use this operation if stop and restart do not resolve the problem. 1 In the System Management Console, from the configuration view, select Network Elements > > > NE Maintenance.
Standard 74 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 MAS into the MCS Fault and Performance Manager (FPM). With this feature, administrators can monitor the MAS from the System Management Console (SMC). On the SMC you add a MAS as a Monitored Element with a name and IP address.
Standard 75 IPCM profile With the IPCM profile feature, you can upgrade IP Phones 2004 that have the Unistim firmware to SIP firmware. All configuration for the SIP phones (such as the domain name, IP address of the session manager, and the Trivial File Transport Protocol (TFTP) server IP address) is uploaded during the upgrade process. Use the System Management Console to configure the required MCS parameters.
Standard 76 Configuring IPCM profile parameters Use the following procedure to add a new profile, or to configure the parameters for an existing IPCM profile. 1 In the System Management Console, in the Configuration view, expand Network Elements. 1 Under Network Elements, expand IPCM Configuration. 2 Under IPCM Configuration, select IPCM Profile. 3 In the IPCM Profile window, select the profile that you want to configure. OR To add a new profile, click Add.
Standard 77 1 In the System Management Console, in the Configuration view, expand Network Elements. 1 Under Network Elements, expand IPCM Configuration. 2 Under IPCM Configuration, select IPCM Profile Server. 3 In the IPCM Profile Server window, select the profile that you want to configure. OR To add a new profile, click Add. 4 In the Edit IPCM Profile Server window, enter the configuration parameters.
Standard 78 Table 10 Firmware Codes Code Telephone FirmwarePhase0x12 IP Phone 2004 Phase 2 SIP transitional firmware FirmwarePhase0x21 IP Phone 2007 FirmwarePhase0x24 IP Phone 1120E FirmwarePhase0x25 IP Phone 1140E FirmwarePhase0x92 IP Phone 2004 with SIP firmware Media Gateway This section describes the upgrading of the Media Gateway firmware. You must have a fully-installed and configured Media Gateway before upgrading its firmware.
Standard 79 The Edit AudioCodes Gateway window appears. 3 View the contents of the Software load menu. If there are no newer loads, then the Media Gateway is up-to-date. Upgrading the Media Gateway firmware Using the System Management Console, 1 In the Config tree, select Network Elements > AudioCodes Gateways. The window shows all the configured Media Gateways. 2 Select a gateway and click -/+. The Edit AudioCodes Gateway window appears. 3 Select the new firmware load in the Software Load field.
Standard 80 NN42020-110 MCS 5100 Release 4.0 Standard 01.
Standard 81 Alarm browser The topics in this chapter include: • “Alarm browser fundamentals” on page 81 • “Alarm browser operations” on page 83 For descriptions of alarms that are generated by the managed elements, see Alarm and Log Reference (NN42020-703). To view alarms from the alarm browser, you must have AlarmQueryService privileges. To acknowledge or clear alarms, you must have AlarmMtcService privileges. Alarm browser fundamentals System elements that are operating can raise and clear alarms.
Standard 82 Table 11 “Alarm browser functions” on page 82 describes available alarm browser functions. Table 11 Alarm browser functions Function Description Start | Stop Auto Refresh The System Management Console begins polling the service components to enable the alarm browser to dynamically update the alarm status. The elements are polled approximately every 5 seconds if this function is enabled. Refresh Updates the Alarm Display area with the current alarms and their status.
Standard 83 For example, if you select a server, the alarm browser shows alarms for the server only, not for the network elements deployed on the server. If you select a network element, the browser shows alarms generated by the network element application only, not alarms for the server or other applications on the server. Administrators can start more than one browser, allowing them to view alarms for specific elements separately.
Standard 84 • • • “Copying alarm information” on page 85 “Clearing alarms” on page 85 “Refreshing alarm information” on page 85 Viewing alarms The alarm browser displays all of the alarms that originated from services and servers under the selected element in the configuration view pane. 1 In the System Management Console, from the configuration view, select a network element or server. 2 On the toolbar, click the alarm browser icon.
Standard 85 Copying alarm information You can copy alarm information (such as one or more alarm rows from the display, or alarm details text) to the PC clipboard, and then paste it into other PCbased documents, such as e-mail. 1 From the Alarm Display area of the alarm browser, select an alarm entry. 2 In the Alarm Details section, click and highlight the alarm details text using the pointer. 3 Press Ctrl+c. The text copies to the PC clipboard.
Standard 86 NN42020-110 MCS 5100 Release 4.0 Standard 01.
Standard 87 Log browser The topics in this chapter include: • “Log browser fundamentals” on page 87 • “Log browser operations” on page 88 For more information about logs generated by the managed elements, see Alarm and Log Reference (NN42020-703). To view log reports from the log browser you must have LogStreamService privileges. Log browser fundamentals The system uses logs to record information related to an event so that the information can be analyzed at a later time.
Standard 88 A live stream of logs (including alarm logs) is reported to the configured FaultPerformance Manager (which can be the System Manager) from the generating network element. As the server receives the logs, they are saved to the current (.active) log file on the Fault-Performance Manager server. After a configured period of time, or after the file reaches a configured size in kilobytes, the log file is closed and renamed (rotated) to an archived log file and a new active log file is opened.
Standard 89 • • • “Clearing log details” on page 89 “Saving logs” on page 90 “Log file rotation period configuration” on page 90 Starting the log browser from the configuration view 1 In the System Management Console, from the configuration view, select Network Elements > > . 2 On the icon toolbar, click the log browser icon. The log browser opens. If the selected network element type is redundant, a log browser for each instance appears.
Standard 90 Saving logs You can select text from the log browser window and paste it into other applications. 1 Select the log text from the log browser with the pointer, or to select all text, press Ctrl+a. 2 Press Ctrl+c to copy the text to the clipboard. 3 Position the cursor in another application, and press Ctrl+v to paste the text.
Standard 91 Operational measurements browser The topics in this chapter include: • “Operational measurements browser fundamentals” on page 91 • “OM browser operations” on page 92 For descriptions about operational measurements (OM) generated by the managed elements, see Operational Measurements Reference (NN42020-704). To view OMs in the OM browser you must have OMQueryService privileges.
Standard 92 All OMs that appear in the OM browsers display the following common information. All other attributes in the OM Details area are specific to the OM group selected. Table 14 OM details Attribute Description Instance This drop-down menu indicates the instance of the network element from which the OMs were collected. If a network element has a second instance and that instance is in service, use the drop-down menu to query the second instance.
Standard 93 Starting the OM browser from the configuration view 1 From the configuration view, select Network Elements > > . 2 Click the OM browser icon in the toolbar. The OM browser for the selected network element opens. By default, the browser queries Active OMs. Figure 7 OM browser icon Starting the OM browser from the physical or logical view After you select a network element in the logical or physical view pane, the OM browser icon becomes active.
Standard 94 Refreshing data in the OM browser The system updates the OM data according to the interval that is configured for the OfficeTransferPeriod configuration parameter. After the browser is open for an extended period, you can query the latest OM data. 1 In the OM browser, from the Type drop-down menu, select Active or Holding. 2 Click Refresh.
Standard 95 Administrator tools The topics in this chapter include: • “User administration” on page 95 • “System Manager password reset” on page 97 • “Role administration” on page 97 • “Viewing and forcing off users” on page 102 • “User password rules” on page 102 • “Database export and import” on page 103 • “Provisioning Client interface” on page 104 • “Message of the day” on page 105 • “HTTP Denial of Service mitigation” on page 106 • “SIP Denial of Service mitigation” on page 109 • “Trusted node configu
Standard 96 Adding or modifying an administrator Before you add an administrator, you must determine the administrative role and password policy to apply to the new administrator. 1 From the System Management Console menu bar, select Administration > User Administration. 2 In the Users window, click Add, or select an existing entry and click Edit.
Standard 97 Deleting an administrator An administrator can delete another administrator from the system. This prevents the deleted administrator from logging in again, but it does not force a logged-on administrator off the system. 1 From the System Management Console menu bar, select Administration > User Administration from the menu bar. 2 From the User window, select the entry for the user and click Delete. 3 Click Yes to confirm the delete.
Standard 98 3 If adding a new role, enter a Role Name. 4 Configure the privileges for this role by selecting the check boxes. 5 Click Apply. Privileges The effects of the READ, WRITE, and MTC privileges differ according to the service that is selected, but some generalizations are possible: • • • READ: This privilege typically allows you to view, but not modify configuration data. WRITE: The WRITE privilege enables READ automatically.
Standard 99 Table 16 Services Privilege Description CipherSuiteService OAMP SSL/TLS cipher suite configuration ConfigParmService Configuration parameters DBInstanceService Database instance configuration DBMonitorConfigService Database monitor threshold configuration DBMonitorService Database instance monitoring DeviceService IPCM device maintenance EndpointMtcService Endpoint Maintenance configuration/ monitoring EngParmService Engineering parameters ExportImportService Bulk configuratio
Standard 100 Table 16 Services Privilege Description MPClusterFaultToleranceService Media Portal Cluster Fault Tolerance configuration MPClusterGwcCallSvrService Media Portal Cluster Gateway Controllers configuration MPClusterMultiGwy Multiple Network Gateway Routers configuration for Media Portal Cluster MPClusterNet2RouteService Choosing the Net2 Routable Networks configuration for a Media Portal MPClusterService Media Portal Cluster configuration MPClusterSessionMgrService Media Portal Clust
Standard 101 Table 16 Services Privilege Description PolicyServerConnectionService Choose Policy Server Connection data Application Manager ID (AMID) for a Session Manager PolicyServerService Policy Servers configuration RTPPortalBladeService RTP Portal blade configuration RegisteredGwcService Registered gateway controller service configuration SecurityService User/Role configuration and user display/ forceoff capability ServerLOMCommandService Server maintenance for servers that are configured
Standard 102 Viewing and forcing off users Administrators with SecurityService privileges can view all logged-on administrators and can force another administrator off the MCS system. Use the following procedure to view administrators logged on to the MCS system and to force an administrator off the MCS system. 1 From the System Management Console menu bar, select Administration > User Display/Forceoff. The Logged-in Users window appears in the work area.
Standard 103 4 From the drop-down menu, select the Minimum Number of Characters in Password. 5 From the drop-down menu, select the Maximum Number of Failed Authentication Attemps. 6 From the drop-down menu, select the Lockout Duration Seconds. 7 Place a check in the Enable Password Complexity Rules check box. 8 Click OK.
Standard 104 7 Click Export Now. You can view the results by opening the exported file. Importing the password and properties for an SMC user Imported passwords can be in clear text or hashed format. 1 Log on to the System Management Console. 2 Select Tools > DB Import. 3 In the DB Export dialog box, click Choose and specify the path to the saved (import) file. 4 Click Choose and specify the path and name for the new (result) file.
Standard 105 Provisioning Client failed authentication Administrators configure the failed authentication threshold and lockout duration parameters as part of the password complexity rules. If authentication fails, the user receives an "invalid login attempt" message. This error message appears for all failed authentication attempts due to invalid user ID, invalid password and lockout conditions.
Standard 106 Figure 8 Message of the day example To enable this feature, log on to the System Manager server and create a file named motd.txt. This file must be in /var/mcp/run/MCP_9.1/SM_x/data/. You can create this file with an editor like vi. If this file does not exist, no Message of the Day window appears. Note that this file is not persisted after any software upgrade or update. During a software upgrade or update, the data directory and its contents are overwritten.
Standard 107 Enabling HTTP DoS mitigation Use the following generic procedure to enable HTTP DoS mitigation. For detailed procedures, see Provisioning Client User Guide (NN42020-105), or Personal Agent User Guide (NN42020-100). 1 From the System Management Console, select the . 2 Select Configuration Parameters > HTTPDoS Parm Group. 3 Configure the Enable DoS filter attribute to true. The default value is false (disabled).
Standard 108 • • • • • MaxNumLockouts: the maximum number of source IP addresses that can be locked out at a given time — range: 1-10 000 — default: 10 000 AlarmThresholds: the thresholds for the distributed DOS alarms, indicating the number of locked-out endpoints — minor alarm (first value) default: 10% — major alarm (second value) default: 50% — critical alarm (third value) default: 100% MaxAttemptsPerInterval: the number of new HTTP transactions per sample interval calculated — range: 1-MAXINT — d
Standard 109 Configuring HTTP DoS mitigation Use the following generic procedure to configure HTTP DoS mitigation parameters. For detailed procedures, see Provisioning Client User Guide (NN42020-105), or Personal Agent User Guide (NN42020-100). 1 From the System Management Console, select the Instance. 2 Select HTTPDoS Parm Group. 3 Configure the parameters (Parms).
Standard 110 3 Configure the Enable DoS filter attribute to true. The default value is false (disabled). SIP DoS engineering parameter group Use the SIP DoS engineering parameter group to configure threshold detection and lockout characteristics for the SIP DoS mitigation feature. Use the System Management Console to configure the following parameters: Note: MAXINT is a hardware-independent Java constant. It is equal to 2147483647—or 231-1.
Standard 111 • BucketCapacityFactor—used to determine the size of the token bucket (BucketCapacityFactor × MaxAttemptsPerInterval = bucket size) • — range: 1-MAXINT — Session Manager default: 165 — other network element default: 1 MaxNumSuspects—the maximum number of source IP addresses that can be monitored at one time — range: 1-MAXINT — default: 1000 Calculations Use the following calculations to determine the SIP DoS parameter values.
Standard 112 Configuring SIP DoS mitigation Use the following generic procedure to configure SIP DoS mitigation parameters. For detailed procedures see Session Manager Fundamentals (NN42020-107), IP Client Manager Fundamentals (NN42020-106), the Provisioning Client User Guide (NN42020-105), or the Personal Agent User Guide (NN42020-100). 1 From the System Management Console, select the Instance. 2 Select SIPDoS Parm Group. 3 Configure the parameters (Parms).
Standard 113 9 From the Node list, select the previously defined external node. 10 In the ShortName and LongName fields, enter short and long names for the informational element. These names must be unique. 11 In the Port field, enter a port number. The port number is usually 5060. 12 From the Type list, select the appropriate type of informational element.
Standard 114 Specifying four levels increases overload control. If you specify only two levels, or after an upgrade (only two levels exist), the system blocks everything but insession messages after the Severe threshold is exceeded. After the call queue drops back below the threshold, the alarm clears and the MCS stops blocking new sessions. Configuring call queue thresholds 1 Start the System Management Console. 2 Navigate to Network Elements > Session Managers.
Standard 115 Troubleshooting The topics in this chapter include: • “System Management Console connection is lost” on page 115 • “Font problems in System Management Console” on page 116 System Management Console connection is lost After the connection between the System Manager and System Management Console is lost, a dialog box and then a prompt to log on appears on your workstation screen.
Standard 116 Font problems in System Management Console The Java Runtime Environment (JRE) can have conflicts with Post Script (PS) fonts that are installed on the management PC. The conflict causes spacing problems with the text displayed in the System Management Console GUI. The text generates an extra space, which cuts off part of the text below. “Example of the spacing problem generated by PS fonts” on page 116 illustrates the problem.
Multimedia Communication Portfolio Multimedia Communication Server 5100 System Management Console User Guide 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.
