NN10364-301 Multimedia Communication Portfolio Multimedia Communication Server 2-server Sun Fire V100 Solaris Installation and Commissioning Guide MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks 3 Contents Finding the latest updates on the Nortel Web site . . . . . . . . . . . . . . . . . . . .7 How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Restrictions and limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 MCS 5100 documentation . . . . . . . .
Copyright © 2006 Nortel Networks 4 Installing Disk 6 (MgmtSvr/AcctMgr only) . . . . . . . . . . . . . . . . . . . . . . . . . 67 Installing Oracle 9.2.0.4 on the database server . . . . . . . . . . . . . . . . . . . . 69 Installing Oracle 9.2.0.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Deploying the initial database load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copyright © 2006 Nortel Networks Procedures 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 Adding and configuring the Web Client Manager . . . . . . . . . . . . . . . . . . 133 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 Installing and configuring the Oracle Monitor . .
Copyright © 2006 Nortel Networks 6 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Finding the latest updates on the Nortel Web site The content of this documentation was current at the time the product was released. To check for updates to the latest documentation and software for MCS 5100, click one of the following links: Link to Takes you directly to the Latest Software Nortel page for MCS 5100 software located at www130.nortelnetworks.com/cgi-bin/eserv/cs/main.
Copyright © 2006 Nortel Networks 8 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks How to get help This section explains how to get help for Nortel products and services. Getting help from the Nortel web site The best way to get technical support for Nortel products is from the Nortel Technical Support web site: www.nortel.com/support This site provides quick access to software, documentation, bulletins, and tools to address issues with Nortel products.
Copyright © 2006 Nortel Networks 10 Getting help from a specialist by using an Express Routing Code To access some Nortel Technical Solutions Centers, you can use an Express Routing Code (ERC) to quickly route your call to a specialist in your Nortel product or service. To locate the ERC for your product or service, go to: www.nortel.
Copyright © 2006 Nortel Networks Overview The MCS 2-server Sun Fire* V100 Solaris system is a small-scale version of the Multimedia Communication Portfolio (MCP) system, geared towards an environment with a maximum of 250 subscribers. This system allows more effective cost management for smaller-sized enterprises. This document describes the installation of the 2-server Sun Fire V100 Solaris system. The 2-server Sun Fire V100 Solaris system must be connected to a 100-MB full-duplex Ethernet switch.
Copyright © 2006 Nortel Networks 12 Figure 2 2-server network with single Ethernet switch SunFireV100 1 0 0 B T P o w e rc a b le SunFireV100 Ethernet switch Protectedpower source Figure 3 2-server network MAS Ad hoc audio conferencing with single Ethernet switch E t h e r n e tS w it c h 1 0 0 B T M X 3 0 5 IBMIB X336 P o w e rc a b le P r o t e c t e d P o w e r S o u r c e The rest of this document will refer to the example data in the figure that follows.
Copyright © 2006 Nortel Networks 13 Figure 4 Example of 2-server Sun Fire V100 Solaris system configuration Restrictions and limitations The 2-server V100 Solaris system is non-redundant. Since redundancy is not built into the system, a server failure will result in the loss of services. The 2-server V100 Solaris system has a mirrored disk. In the event of a disk failure, the failed disk should be replaced as soon as possible.
Copyright © 2006 Nortel Networks 14 MCS 5100 documentation Refer to the MCS 5100 Network Deployment and Engineering Guide, NN10313-191, that accompanies the MCS 5100 product and to your customer-specific information (CSI) datasheet for your system requirements.
Copyright © 2006 Nortel Networks 15 • MCS 5100 Fault Management: Alarm and Log reference, NN10385-900 • MCS 5100 Performance Management: OM reference , NN10386-700 MCS 2-server Sun Fire V100 Solaris Installation and Commissioning Guide
Copyright © 2006 Nortel Networks 16 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Before you start the installation ATTENTION Make sure you install the latest software loads. Check with your support team for the correct latest load. Prerequisites Have available your completed Customer-Specific Information (CSI) datasheet. Refer to the MCS 5100 Network Deployment and Engineering Guide, NN10313-191, that accompanies the MCS product for CSI and system requirements.
Copyright © 2006 Nortel Networks 18 The procedures in this Guide assume that you are using the PuTTY VT100 terminal emulator tool. ATTENTION To set up sessions, download from the web the PuTTY VT100 Emulator, a shareware configurator tool. Download PuTTY from www.chiark.greenend.org.uk/~sgtatham/putty/ Provide the following hardware: • Business Policy Switch 2000 (BPS 2000) or Layer-2 switch • One (1) cat-5 Ethernet cable that is used to connect the MRV LX terminal server to the layer-2 switch.
Copyright © 2006 Nortel Networks 19 Key stroke symbols The following key stroke symbols are used in this document. When you are asked to You must... Press Esc+2 Press Escape then press 2. Navigate Use the arrow keys to move up or down. Select Use the spacebar to select an item. Enter value indicated in brackets. [Enter] Press key indicated in brackets.
Copyright © 2006 Nortel Networks 20 Server configuration The following table shows the basic configuration of the 2-server V100 Solaris system. Table 1 2-server configuration Configuration Server type Components 2-server V100 Solaris Server1 Active System Manager Active Accounting Manager Primary database Oracle Monitor Server2 IPCM (S1) Active Provisioning Module Active SIP Application Module Active WebClient Manager iPlanetMonitor UFTP Base Software Loading disks MCS 5100 Release 3.
Copyright © 2006 Nortel Networks 21 MCS Base Platform System Software disks are loaded on the following servers as indicated in Table 2, Mapping of Kit NTVW01BD disks to servers (with times) MCS Base Platform System Software: Order code NTVW01BD Approximate time to install Server 1 Server 2 Table 2 Mapping of Kit NTVW01BD disks to servers (with times) CD1 Disk Partitioning & Solaris OS Kernel 45 minutes X X CD2 Solaris OS Packages 15 minutes X X CD3 Solaris Packages and Patches 90 minutes
Copyright © 2006 Nortel Networks 22 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Minimum and recommended requirements for customer-provided PC Configure your management pc to have an IP address that is in the same subnet of the IP address range used for your servers. Check your pc vendor’s documentation to learn how to configure the PC’s IP address.
Copyright © 2006 Nortel Networks • mouse: required • Video Graphics Card: 24 — minimum: 640x480 @8bpp [256 colors] VGA — recommended: 800x600 @16bpp [65,536 colors] VGA or better • sound card: not applicable • operating systems: — minimum: Microsoft Windows 98(SE)/ME/2000/XP, or Microsoft Windows NT 4.x with Service Pack 5 (SP5) — recommended: Microsoft Windows 98(SE)/ME/2000/XP, or Microsoft Windows NT 4.
Copyright © 2006 Nortel Networks Setting up the baseline hardware Baseline hardware See the following figure for an overview of the hardware connectivity. Figure 3 Hardware connections overview ATTENTION You need an uninterrupted power source (UPS). If a power outage occurs, bring the server for the Database Module into service before bringing the other servers into service. If other servers do not come up, restart the server for the Management Module.
Copyright © 2006 Nortel Networks 26 Hardware required for the 2-server system consists of the following: • terminal server: 1 MRV LX-4008-101AC including — Linux-based secure console standalone unit with 8 RS232 RJ45 ports — internal V.
Copyright © 2006 Nortel Networks • Media Application Server: 1 IBM x336 (2 3.
Copyright © 2006 Nortel Networks 28 Figure 4 MCS 5100 19-inch rack Connecting the Sun Fire V100 server to the layer-2 switch Procedure 2 Connecting the V100 server to the layer-2 switch At the back of the Sun Fire V100 server, 1 Connect the Sun Fire V100 server Net 0 and Net 1 ports to the layer-2 switch using Ethernet, cat-5 cables. Figure 5 Back view of Sun Fire V100 server NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks 29 Figure 6 Sun Fire V100 server cabling to layer-2 switch Note 1: Net 0 and Net 1 are for redundancy. It is preferable that each Ethernet port get cabled to a different layer-2 switch, if available, for maximum redundancy. Note 2: The two Ethernet switches are physically linked together through either cascade modules or Ethernet links. 2 Plug in the power cords at the back of the V100 server. ATTENTION Do not power up the server at this time.
Copyright © 2006 Nortel Networks 30 Figure 7 Sun Fire V100 server network callouts ATTENTION If the network is down, or the server needs to be configured or restarted, use the console port A. By default from manufacturing, serial port A is the only active serial port. Note 1: The cables with part numbers A0500465 or NTVW01IM are serial cables. Note 2: The P1 end goes to the V100 server and the P2 end goes to the MRV LX terminal server. NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks 31 Figure 8 P1 and P2 custom cable connections to terminal server See note Note: This cable is only connected to configure the terminal server. Following configuration, remove the cable.
Copyright © 2006 Nortel Networks 32 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Installing and accessing the MRV LX-4000 series terminal server The MRV LX terminal server allows the installer to access all the servers simultaneously. ATTENTION For complete information on how to install, configure, and access the MRV LX terminal server, refer to the MRV Communications, Inc., LX Series Software Kit CD, particularly the "Getting Started with the LX-4000 Series" and LX-4000 Quick Start Instructions that come in the terminal server box, or go to www.mrv.
Copyright © 2006 Nortel Networks 34 Figure 9 MRV Configuration Console window 2 Make sure you have the Java Plug-in installed. 3 When your browser connects to the terminal server, the Java Security Warning window appears. Figure 10 Java Security Warning pop-up window NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks 4 35 Click on Grant this session. The Java Security Warning window closes. The LX Series Configuration Console page reappears, now with the green console selection visible. Figure 11 LX Series Configuration Console page Choosing Encrypted Console means the Graphical User Interface (GUI) will run slower, but with security. Encrypted and Not Encrypted Console also require Java Runtime Environment 1.4 or later.
Copyright © 2006 Nortel Networks 36 Figure 12 Login window 6 Enter your Username and Password, and click Login. Note: By default, authentication is done against the local user database. To start, use the known username InReach and password access. 7 If you log in as a user, the following window appears. NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks 37 Figure 13 User login window 8 To log in as a superuser, click the Admin button on the tool bar and log in with the default Superuser password system. You can now configure the unit at the GUI. 9 Click on the menus on the left side of the window. For example, selecting Ports: Async opens the Async ports window.
Copyright © 2006 Nortel Networks 38 Figure 14 Example: selecting Ports: Async a When you click on a port, the following dialog box appears for you to enter your information. Note: In the TCP window (see Figure 15), ensure that both the Telnet CR Filtering radio button, and the Telnet Negotiations radio button are Enabled. NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks 39 Figure 15 Port 19 dialog box For details on using the IP Configuration Menu, refer to “Using the IP Configuration Menu” in the LX-Series Configuration Guide. For information on how to boot your unit from defaults, refer to “Booting from Defaults” in the LX-Series Configuration Guide.
Copyright © 2006 Nortel Networks 40 Procedure 6 Connecting through the server to the MRV LX terminal server At the management pc, 1 ATTENTION MRV Communications recommends that you change the default password for the user’s MRV LX terminal server before you put the unit on a network. For more information, refer to Changing the password defaults on page 40.
Copyright © 2006 Nortel Networks 41 4 Enter a new user password at the Enter your NEW password: prompt. The password will be displayed as asterisks. 5 Re-enter the new user password at the Re-Enter your NEW password: prompt. The password will be displayed as asterisks. 6 To change the superuser password for the unit, do the following: a Access the Configuration Command Mode. b Enter the password command at the Config:0 >> prompt.
Copyright © 2006 Nortel Networks 42 7 Enter your password: system [Enter] 8 Define server ip address [Enter] 9 Define server ip subnet mask [Enter] 10 Define server ip primary gateway address [Enter] 11 Define port:
Copyright © 2006 Nortel Networks 4 43 For port, enter . Note 1: For LOM ports, use terminal server ports 2100-2400 (physical ports 1-4). For Serial ports, use terminal server ports 3100-3400 (physical ports 11-14). The port number identifies the location of the target host. This value is based on the following formula: 2000 + (Port number physically connected on the MRV LX terminal server x 100).
Copyright © 2006 Nortel Networks 44 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Powering on the servers Procedure 10 Powering on the servers At the server, 1 ATTENTION Do not have any bootp servers on the same subnet of the system. If there is such a server, disconnect the LAN interface cable from the system subnet. Turn power on to the server. 2 If the system boots up, log into the server as root. 3 Type init 0 [Enter]. This will bring you to the boot (>ok) prompt. If the system does not have Solaris installed, it will power up to the >ok prompt.
Copyright © 2006 Nortel Networks 4 46 The >ok prompt appears. ATTENTION If you do not use PuTTY, use the appropriate key sequence to send a break to the server to get an >ok prompt. NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Installing Disks 1 to 3 ATTENTION Refer to the customer-specific information datasheet for host name, IP addresses, subnet masks, and so on. ATTENTION For installation on a brand-new machine, connect through the terminal server to the A/LOM port until after you have installed CD5. Then log out. Log back in through the terminal server to B/Serial port for the rest of the installation.
Copyright © 2006 Nortel Networks 48 2 ATTENTION Make sure you put spaces before and after the hyphen: boot [space] cdrom [space] - [space] install. At the >ok prompt, boot the system: boot cdrom - install [Enter] Note 1: For instructions on how to get to the >ok prompt, see Powering on the servers on page 45. Note 2: You must wait several minutes before information begins to appear.
Copyright © 2006 Nortel Networks 49 Network Connectivity/Networked 3 Accept the default Yes by pressing Esc+2 to continue. DHCP/Use DHCP 4 Accept the default No by pressing Esc+2 to continue. Primary Network Interface /Primary Network Interface 5 Accept the default dmfe0 interface by pressing Esc+2 to continue. Host name/Host name 6 Enter the host name of the server, for example: micromgmt Note 1: Host name cannot start with a number.
Copyright © 2006 Nortel Networks 50 Netmask/Netmask 9 ATTENTION Do not accept the default unless you are sure it is correct for your subnet. Enter the subnet mask, for example: 255.255.255.0. Press Esc+2 to continue. IPv6/Enables IPv6 10 ATTENTION IPv6 is not supported. Accept the default No. Press Esc+2 to continue. There is a slight delay between screens. Please wait. Confirm information 11 Ensure all fields are filled correctly. Press Esc+2 to continue. Press Esc+4 if you need to change anything.
Copyright © 2006 Nortel Networks 51 Continuing the process 15 Confirm your information. Ensure all fields are filled correctly. Press Esc+2 to continue. Press Esc+4 if you need to change anything. 16 At the Regions prompt, select the country where the system is going to be deployed. Use the arrow keys to navigate to the required country and press the spacebar to mark your choice. Ignore time zone syntax errors. Press Esc+2 to continue.
Copyright © 2006 Nortel Networks 52 21 ATTENTION Make the following selection very carefully. If you make a mistake at this point, you will need to start over, beginning with Powering on the servers on page 45. The selection of the number depends on the server type.
Copyright © 2006 Nortel Networks 53 Procedure 13 Installing CD2 At the management pc, 1 Place CD2 in the CD-ROM drive and press Enter. You will see a number of messages requiring no specific answer. Press Enter following each one. 2 You will then see the following message: What type of installation are you performing? 1=Typical; 2=CustomType 1 and press Enter.
Copyright © 2006 Nortel Networks 54 Procedure 14 Installing CD3 At the management pc, 1 ATTENTION Wait for the login prompt to appear. The script will execute after you press Enter. Place CD3 in the CD-ROM drive and press Enter at the prompt. The installation will continue. Please wait. The system will prompt you for the next step. 2 Log in as root. [Enter] 3 Enter your [Enter] Note 1: CD 3 will eject from the CD-ROM when installed.
Copyright © 2006 Nortel Networks Installing Disk 4 ATTENTION The following sections describe installing CD4 according to the specific server type. Please note that there are some small, but very important, differences in the installation of the two types of servers (database/accounting/management or application server).
Copyright © 2006 Nortel Networks 56 to use the local system clock as the time source. Note: Select Time Source • X - External Clock Device • E - External Clock Source {IP Address(es)} • I - Internal Clock (Unreliable) Select option from list above [E, I, X] 4 ATTENTION Refer to the CSI for NTP time source IP information. Select one of the options, then press Enter. If you select X - External Clock Source, you will see a list of clock types. Select the type you have or none (99).
Copyright © 2006 Nortel Networks 57 7 Press Enter to continue. 8 You will see the following statement: ”You are now configuring IPMP (Multipathing)" ”Please have the Database Server Physical IP addresses and the Machine Logical IP address ready. Have 6 IP addresses that can be used as ping buddies." Recommendations for ping buddies are provided. 9 Press the Enter key to continue.
Copyright © 2006 Nortel Networks 58 Enter ping target #1: 120.120.13.25 Enter ping target #2: 120.120.13.1 Enter ping target #3: 0.0.0.0 Note: Do NOT use this server's own IP address as a ping target. Press Enter after each IP address. 14 The configuration information will come up as shown in the following figure: Figure 16 Database/Management/Accounting server IPMP configuration summary Is this IPMP group configuration acceptable? (Y/N) Select Y and press Enter.
Copyright © 2006 Nortel Networks 59 You will see the following message: Obtaining IP Addresses for SysMgr/AcctMgr Failover Operation Note: If you don't have plan to configure the failover service, type in the same primary service logical IP address and primary machine logical IP address or type 0.0.0.0 instead. 17 Enter the (in dot-notation format). Example: 120.120.13.22 18 Enter the (in dot-notation format).
Copyright © 2006 Nortel Networks 60 Procedure 16 Installing CD4 At the management pc, 1 Place CD4 in the CD-ROM drive and press Enter to continue. WAIT until you see the following statement appear: ”You are now configuring the NTP time source for this server. The servers which run the Management and Accounting service will be the source. You will need to provide the Machine Logical IP Address of each server. If running simplex mode, provide the same address twice.” 2 Press Enter to continue.
Copyright © 2006 Nortel Networks 9 61 Enter the primary machine physical IP address for the dmfe0 interface: Example: 120.120.13.23 10 Enter the secondary machine physical IP address for the dmfe1 interface: . Example: 120.120.13.24 11 Enter the that are the ping targets. Note: Do not enter the IP address of the server you are working on.
Copyright © 2006 Nortel Networks 62 Figure 17 Application server IPMP configuration summary Is this IPMP group configuration acceptable? (Y/N) Select Y to accept or N to change. 14 The default route IP address should appear. If correct, press Enter. Otherwise, type it in, then press Enter. Note: If your configuration does not include a router, then enter the machine logical IP address of your server. 15 Do you intend to deploy the Web Server to this machine (y,n)? Enter Y.
Copyright © 2006 Nortel Networks Installing Disk 5 (all servers) Approximate time estimate is 30 minutes. Procedure 17 Installing CD5 At the management pc, 1 Place CD5 in the CD-ROM drive, on the server, and press Enter at the prompt. Note 1: CD5 will eject from the CD-ROM when installed. Note 2: For Management/Accounting servers, you will be prompted for CD6. Refer to Installing Disk 6 (MgmtSvr/AcctMgr only) on page 67 for instructions. Application/IPCM servers (AppSvr/IPCM) will reboot.
Copyright © 2006 Nortel Networks 64 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Enabling or disabling the automatic mount Use the following procedure if you need to use the CD-ROM auto-mount after installation of CD5. Execute this procedure on the MgmtSvr (Server1). ATTENTION Keep this procedure for future use. Procedure 18 Enabling or disabling the CD-ROM auto-mount At the management pc, 1 The system disables volmgt by default after CD5 is installed. To toggle it back on to install additional CDs, follow this step.
Copyright © 2006 Nortel Networks 66 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Installing Disk 6 (MgmtSvr/AcctMgr only) ATTENTION CD6 must be installed on the MgmtSvr and on the AcctMgr machines only. If you do not install CD6, you will not be able to deploy or start the secondary MgmtSvr or AcctMgr. Approximate time estimate = 30 minutes Procedure 19 Installing CD 6 At the management pc, 1 Place CD6 in the CD-ROM drive, on the server, and press Enter at the prompt. Note: CD6 will eject from the CD-ROM when installed.
Copyright © 2006 Nortel Networks 68 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Installing Oracle 9.2.0.4 on the database server The procedures to install Oracle 9 on the DBSvr include storing Oracle 9 CDs 1-6 to your local hard drive. Refer to the section that follows. Approximate time for loading Oracle 9 = 90 minutes ATTENTION Refer to the CSI datasheet for such items as the hostname, IP addresses, and subnet masks. ATTENTION Perform these steps on all servers in parallel if multiple CDs are available. Installing Oracle 9.2.0.
Copyright © 2006 Nortel Networks 70 5 ATTENTION Make sure you put a space before the ending slash (/) in step 5. cp [ space] Install_CD_to_Disk [ space] / [Enter] 6 cd [ space] / [Enter] 7 .
Copyright © 2006 Nortel Networks 71 Refer to this table when entering the following command: Prompt Definition Enter pri_db_hostname There is only one hostname for a 24-server configuration. Hostname of the database server, for example, micromgmtDBSvr. sec_db_hostname Since there is no secondary server, enter again the pri_db_hostname (Hostname of the database server). Re-enter hostname of the database server. cd [space] /IMS/ora_cds/Disk1 [Enter] .
Copyright © 2006 Nortel Networks 72 Failing to answer Y will cause the system to raise a disk space alarm on the SysMgr screen for the DBSvr. You will see the message: Removing Disk 1, Disk2, Disk3, Disk4, Disk5, Disk6 from /IMS/ora_cds.... Oracle_Install Complete. 18 At the completion of the script, you will see the message: Oracle_Install complete Press Ctrl-C to exit. 19 To check for errors, at the prompt, type cd [space] /tmp [Enter] 20 View the /tmp/oracleinstall.
Copyright © 2006 Nortel Networks Deploying the initial database load Prerequisites Ensure that the MCS Base Platform Software and Oracle 9i have been installed on database servers. ATTENTION Refer to your CSI datasheet to enter the IP addresses that you are prompted for in this section. Deploying the MCS database load (imssipdb) After performing the steps for installing MCS Base Platform software and Oracle software, an empty imsdb1 database is all that exists.
Copyright © 2006 Nortel Networks 74 5 You will see the following message: Select the Type of Deployment: [1] Initial Deployment [2] Upgrade of Database [3] Rollback of Database [4] Install Files only to Select 1 for initial deployment, then press Enter. 6 Enter Machine Logical IP Address - Primary DB [No default]: Enter the Example: 120.120.13.22 7 Enter the Machine Logical IP address Management Server: Enter the .
Copyright © 2006 Nortel Networks Deploying and starting the Sysmgr Prerequisites The dbdeploy.pl script is successfully deployed on the database. ATTENTION Refer to the customer-specific information for hostname, IP addresses, subnet masks, and so on. Deploy the Sysmgr for a non-redundant configuration. The operator logs into the machine logical IP address of the management server. At the UNIX prompt, the operator the uses the script mgmtdeploy.pl to deploy and start the Sysmgr.
Copyright © 2006 Nortel Networks 76 3 ATTENTION When selecting the management server load, always select the load that contains the word "micro" in it. If the non-micro load is selected, the installer will receive an Out Of Memory error. The server load names are: • mgmtsvr_all-mico-ims — for a 2-server installation. • mgmtsvr_all-small-ims — for a 4-server or an 8-server V100 installation. • mgmtsvr_all_ims — for an 8-server N240 installation.
Copyright © 2006 Nortel Networks Example: 120.120.13.22 7 Will a Motorola SAM16 server (SIP PriGwy or SIP Audio Svr) be deployed? [Y/N] Always answer N [Enter] even if you have a third-party gateway. Note: Information obtained for deploying the Sysmgr appears. 8 Is the above data correct? [Y] Answer Y [Enter] 9 Start up the SysMgr and TSS processes? [Y] Answer Y [Enter] Note: You must wait until the system returns to prompt since the system does a sleep message as it starts each service.
Copyright © 2006 Nortel Networks 78 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Registering your license key Before installing the license key as described in Procedure 25, Installing the System Management Console, follow the procedure below to generate and register your license key. Procedure 24 Registering the license key At the management pc, 1 Before you can begin generating keycodes, first “Register” (or create) your site on the KRS (Keycode Retrieval System) webpage.
Copyright © 2006 Nortel Networks 80 Figure 18 KRS login screen 4 In step 1 (Location) select a login server that matches your region, for example, European Login or North American Login. 5 In step 2 (Product Family) select the product you wish to generate keycodes for; in this case, select Multimedia Communication Portfolio. 6 Next you will be asked to enter your User ID and Password. The following screen then appears. NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks 81 Figure 19 Keycode Retrieval System, Creating your site 7 Select Create to register a new system. The following screen appears.
Copyright © 2006 Nortel Networks 82 Figure 20 Keycode Retrieval System, Entering your site information 8 Fill in the requested information and press the Continue button. Ensure you choose the correct software version from the dropdown box. Your screen should look like the one in the following figure. NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks 83 Figure 21 Keycode Retrieval System, Current Summary 9 Select the server you want to enter MAC addresses for first, then click on Create. 10 Enter the MAC addresses of the CORE servers and click on Add.
Copyright © 2006 Nortel Networks 84 Figure 22 Keycode Retrieval System, Adding MAC address 11 Repeat Step 10 for the second MAC address (required). If you make an error, you can remove one or both and begin again. If you have a second Core that is going to be installed as a redundant server enter all four MAC addresses at this time. 12 When finished you will need to select Create again to enter the Media Application Server's MAC addresses, enter those just as you did in Step 10.
Copyright © 2006 Nortel Networks 85 Server Service Guide applicable to your system (see the Overview chapter for a listing of the service guides). Note: If you have a second Media Application Server for your system, you must select Create a second time as only two MAC addresses can be associated with any one Media Application Server. Figure 23 Keycode Retrieval System, Adding a Media Application Server 14 You will see a summary page of your entries.
Copyright © 2006 Nortel Networks 86 Figure 24 Keycode Retrieval System, Current Summary 15 To generate keycodes for this site, click on Gen KC with Auth Code from the side bar, as shown in the following figure. NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks 87 Figure 25 Keycode Retrieval System, Gen KC with Auth Code 16 To generate your keycodes, enter one of the MAC addresses of the server you want your Auth code applied to. In this case, the example shows one of the CORE MAC addresses. Select Add. 17 The KRS automatically searches for and pulls up both MAC addresses associated with the CORE. Click on Continue.
Copyright © 2006 Nortel Networks 88 Figure 26 Keycode Retrieval System, Finding the keycode 18 Select the proper Software Version for your system. Then click on Continue. NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks 89 Figure 27 Keycode Retrieval System, Adding a MAC address 19 Enter the authcode number for the feature you wish to enable into the Auth Code box. Use the system Authorization codes to build your license key file.
Copyright © 2006 Nortel Networks 90 Figure 28 Keycode Retrieval System, Entering the authcode 05006201 20 Select Add to have the KRS accept the authcode. 21 The KRS will validate the authcode and ensure the features represented are valid for your server type (CORE or MAS). If validated successfully you will be allowed to enter more authcodes until you've entered all for your server. When this process is complete, click on Continue.
Copyright © 2006 Nortel Networks 91 Figure 29 Keycode Retrieval System, Summary of features Best Customer 23 The KRS will indicate it is generating your keycodes and saving the results in its database. After generating the keycodes and saving results in the KRS database, the system shows the Retrieve Keycode page where you can view the features enabled for the server. From this page you will be able to download the keycode (see the figures below).
Copyright © 2006 Nortel Networks 92 Figure 30 Keycode Retrieval System, Retrieving the keycode Best Customer The screens show the features of your keycode and the option to download the keycode to your local PC. To download the keycode click on Download Keycode. From there you will see the screens to download the file and save it where you choose to on your local machine. Note that the file will be provided with a product-specified naming convention. NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks 93 Figure 31 Keycode Retrieval System, Retrieving your keycode, part 2 24 Download the new license key file to the MgmtSvr hard drive.
Copyright © 2006 Nortel Networks 94 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Installing and launching the System Management Console Prerequisites Make sure that • The dbdeploy.pl script has been successfully executed. • The mgmtdeploy.pl script has been successfully executed. • The Sysmgr is started. • The license key is registered.
Copyright © 2006 Nortel Networks 96 12 Click Next to begin installation. 13 At the pop-up window that says, Installation successfully completed, click OK. Launching the System Management Console Make sure that the System Management Console application has been successfully installed on the PC. Procedure 26 Launching the System Management Console At the management pc, 1 Click Start ->Programs ->MCP->System Management Console.
Copyright © 2006 Nortel Networks 97 the License Key->Update dropdown menu (You can also select the System=>License Key=>Update menu option from the System tree.) as shown in Figure 32, Management Console Update License Key. The System item on the file tree must be highlighted.
Copyright © 2006 Nortel Networks 98 Figure 33 Select License key File Window 7 Once you have entered the new License Key, you will see a dialog box notifying you whether the update is successful or fails. If the system does not find a license key in the database or on the Managements server local disk, a dialog box (Figure 33) will appear, prompting for a license key file. If you do not immediately see your license key, locate it by browsing the file system.
Copyright © 2006 Nortel Networks 99 The console screen has the basic look and feel of a Windows Explorer window with a tree structure on the left, and a general information area on the right. Each folder on the management console tree is represented as a Network Element and each has a different functionality.
Copyright © 2006 Nortel Networks 100 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Adding a server Prerequisites The System Management Console has been successfully installed and started. Adding a server Use this procedure to add each of your servers. Note: You should view the content of this chapter as reference information. When you perform the procedures in the next three chapters (in this document) you will be asked to return to this chapter. Procedure 27 Adding a server At the System Management Console, 1 Select Sites->MgmtSite->Servers.
Copyright © 2006 Nortel Networks 102 System server field Customer defines Example Longitude Optional field. Describes the longitudinal coordinates of the location of this server. default Platform type Drop-down menu with following choices: Sun or Linux. Select Sun. Sun IP address The machine logical IP address of the server. 120.120.13.25 Snmp Port Request Leave the default value as is.
Copyright © 2006 Nortel Networks Adding and configuring the Accounting Module Prerequisites Make sure that • The System Management Console has been successfully installed and started. • A valid license key has been entered and accepted by the management system. Procedures Procedure 28 Adding an Accounting Module component to the server At the System Management Console, 1 Select Sites->MgmtSite->Servers->Add->General->MgmtSvr.
Copyright © 2006 Nortel Networks 104 Procedure 29 Configuring the tabs At the System Management Console, 1 Use the values from the table that follows to complete the Central Accounting Manager tab parameters. Note: The shaded row indicates values that must be addressed by the installer. Table 1 Central Accounting Manager tab (Sheet 1 of 2) Parameter Recommended value Notes CAM IP Address 192.168.14.11 120.120.13.
Copyright © 2006 Nortel Networks 105 Table 1 Central Accounting Manager tab (Sheet 2 of 2) Parameter Recommended value TCP/IP Address 0.0.0.0 default TCP/IP Primary Host Port 9000 default TCP/IP Recovery Host Port 9001 default FTP Push Enabled unchecked default Primary FTP Directory (blank) default Recovery FTP Directory (blank) default Remote FTP Node ID 0.0.0.0 default FTP User ID (blank) Configurable based on your system.
Copyright © 2006 Nortel Networks 106 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Adding and configuring the SIP Application Module Prerequisites Make sure that • The System Management Console has been successfully installed and started. • A valid license key has been entered and accepted by the management system. Procedures Procedure 30 Adding the SIP Application Module component At the System Management Console, 1 Select Sites->MgmtSite->Servers->Add->General->AppSvr.
Copyright © 2006 Nortel Networks 108 Procedure 31 Configuring the SIP Application Module tabs ATTENTION Do not click Apply until you have FINISHED configuring all the tabs. At the System Management Console, 1 Use the values from the following table to enter into the Authentication tab parameters.
Copyright © 2006 Nortel Networks Table 2 Authentication tab (Sheet 2 of 2) Parameter Recommended value Nonce Interval 600 Authorized Method Entries: Authorized Method register (initial registration authorization) invite (calls authenticated) subscribe (Presence authenticated) message (Instant Message authenticated) 2 Notes Example default Use the following values to complete the Local Accounting Manager tab. The shaded rows indicate values that must be addressed by the installer.
Copyright © 2006 Nortel Networks Table 3 Local Accounting Manager tab (Sheet 2 of 2) Parameter Recommended value Disk Monitor Critical Threshold 75 default Enable Billing For Instant Message unchecked default 3 Notes Example Use the values from the table that follows to complete the Media Portal tab parameters. The shaded rows indicate values that must be addressed by the installer.
Copyright © 2006 Nortel Networks The shaded rows indicate values that must be addressed by the installer. Table 6 Database Base tab Parameter Recommended value Primary Host 192.168.14.111 120.120.13.22 Connections 8 default Secondary Host Not applicable 6 Notes Example Use the values from the table that follows to complete the SIP TCF Base tab parameters.
Copyright © 2006 Nortel Networks Table 8 In Memory Database tab (Sheet 2 of 2) Parameter Recommended value Number of users 2000 Notes Update interval for presence limits Example default default 86400 Update interval for admin banned users 900 default Update interval for user banned users 900 default IMAuthNonce table size 5 default IMAuthNonce generation interval 60 default Number of call logs 5000 default IM CallLog DB write interval 60 default 8 Use the values from the tabl
Copyright © 2006 Nortel Networks 10 Use the values from the table that follows to complete the Server Subscription tab parameters. Table 11 Server Subscription tab Parameter Recommended value Notes provServerURL 120.120.13.25:5095:8 0:http Server name (App Server) 11 Example Use the values from the table that follows to complete the Subscription Processing tab parameters.
Copyright © 2006 Nortel Networks Table 14 Server Properties tab (Sheet 2 of 2) Parameter Recommended value Notes Example Service Parameter: Label Private_Service_Address not applicable default Value: Service Parameter: Label CallPark.TokenRange default Value: 14 Range is 1-80 characters default This is the value to enter if you have the ability to park a call. For more information, see the MCS SIP Application Module Basics (NN10259-111) document.
Copyright © 2006 Nortel Networks Table 15 Overload Controls tab (Continued) Parameter Recommended value Database queue low threshold 1 default Protocols Monitored sip default 15 Notes Example Use the table that follows to modify the fields for the Transport Management tab. The shaded rows indicate values that must be addressed by the installer. Modify the public fields only. There are no private addresses.
Copyright © 2006 Nortel Networks 116 Table 16 Transport Management tab (Sheet 2 of 3) Parameter Recommended value Notes Example Remote Server Address Only fill PUBLIC Service Address field. 120.120. 13.25 Local Server Address Public_Static_Address default Parameters: NSD Number 1 default NSD Enabled unchecked Box unchecked.
Copyright © 2006 Nortel Networks 117 Table 16 Transport Management tab (Sheet 3 of 3) Parameter Recommended value Protocol SIP default Transport TCP default Address Public_Service_Address default Port 5060 default Params name=sipLscConduit:inte rface=dmfe0 16 Notes Change default qfe0 to dmfe0 Example dmfe0 Click Apply. The component will deploy. Wait until you see the dialog box indicating successful installation. The component will appear in the file tree.
Copyright © 2006 Nortel Networks 118 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Adding and configuring the IP Client Manager Prerequisites Make sure that • The System Management Console has been successfully installed and started. • A valid license key has been entered and accepted by the management system.
Copyright © 2006 Nortel Networks 120 Procedure 33 Configuring the IP Client Manager tabs ATTENTION Do not click Apply until you have finished configuring the component. At the System Management Console, 1 Use the values from the table that follows to complete the IP Client Manager tab parameters. Note: The shaded rows indicate values that must be addressed by the installer.
Copyright © 2006 Nortel Networks 121 Table 17 IP Client Manager tab (Sheet 2 of 2) Parameter Recommended Value Phase 1 Firmware ID B60 default Phase 2 Firmware ID D61 default Use UFTP checked UFTP Server Port 50020 default Keep Alive Timer 40 default KA Phone Timer 90 default Switch Server Delay 5000 default Min ReReg Delay 60000 default Max # Reg Attempts 25 default Server Recovery Time Min 1 default Server Recovery Time Max 5 default 2 Notes Box is checked.
Copyright © 2006 Nortel Networks The shaded rows indicate values that must be addressed by the installer. Table 19 UNISTIM Base tab Parameter Recommended value LocalHost 192.168.14.41 120.120.13.25 Port 5000 default 4 Notes Example Use the values from the table that follows to complete the SIP TCF Base tab parameters. The shaded rows indicate values that must be addressed by the installer.
Copyright © 2006 Nortel Networks 6 Use the values from the following table to enter into the In Memory Database tab parameters. The shaded rows indicate values that must be addressed by the installer.
Copyright © 2006 Nortel Networks 124 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Installing the UFTP BaseSoftware You will be installing the UFTP software on the application server. Prerequisites The System Management Console has been successfully installed and started. Note: This procedure also assumes that the IP Client Manager (IPCM) component was deployed successfully; the UFTP software therefore can interact with the IPCM for firmware.
Copyright © 2006 Nortel Networks 126 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Configuring the Provisioning Module Prerequisites Make sure the System Management Console has been installed and started. Procedures Procedure 35 Adding the Provisioning Module (Small SharedMicro) At the System Management Console, 1 Select Sites->MgmtSite->Servers->AppSvr. 2 Click on the plus sign next to the server to which you are adding the component. 3 Right click on the Components folder. 4 Select Add->Component.
Copyright © 2006 Nortel Networks 128 Procedure 36 Configuring the Provisioning Module tabs At the System Management Console, 1 Use the values from the table that follows to complete the SIP TCF Base tab parameters. The shaded rows indicate values that must be addressed by the installer. Table 24 SIP TCF Base tab Parameter Recommended value Notes Example Transport Config UDP=:5070:optional ;TCP=:5070:optional UDP=192.168. 14.
Copyright © 2006 Nortel Networks Table 25 User Agent Server tab (Continued) Parameter Recommended value Notes Example Application Server Port 5060 default Click-to-call Cancel Delay 18 default 3 Use the values from the table that follows to complete the Web Client Manager tab parameters. The shaded rows indicate values that must be addressed by the installer.
Copyright © 2006 Nortel Networks Table 26 Web Client Manager tab (Sheet 2 of 2) Parameter Recommended value Allow Auto Login checked Download JRE Version This field holds the version of the Java Runtime Environment (JRE) installer that the Web Client applet downloads. For the latest version of the installer from Sun, leave this field empty. For the installer provided by the MCS (The MCS currently provides 5 different JRE installers.) , use string "1.4.2_01", "1.4.2_02", "1.4.2_03", "1.4.
Copyright © 2006 Nortel Networks The shaded rows indicate values that must be addressed by the installer. Table 29 Provisioning Client tab Parameter Recommended value Provisioning Server Host 192.168.14.41 120.120.13.25 Provisioning Server Port 8821 default Provisioning Blocked Wait Time 10000 default 7 Notes Example Use the values from the table that follows to complete the Conference_Service tab parameters.
Copyright © 2006 Nortel Networks 132 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Adding and configuring the Web Client Manager Prerequisites Make sure that • The System Management Console has been successfully installed and started. • A valid license key has been entered and accepted by the management system. Procedures Procedure 37 Adding the Web Client Manager (Small SharedMicro) At the System Management Console, 1 Select Sites->MgmtSite->Servers->AppSvr. 2 Click on the plus sign next to the server to which you are adding the component.
Copyright © 2006 Nortel Networks 134 Procedure 38 Configuring the Web Client Manager tabs ATTENTION Do not click Apply until you have finished configuring the component. At the System Management Console, 1 Use the values from the table that follows to complete the User Agent Server tab parameters. The shaded rows indicate values that must be addressed by the installer.
Copyright © 2006 Nortel Networks The shaded rows indicate values that must be addressed by the installer. Table 32 SIP TCF Base tab Recommended Value Notes Example Transport Config UDP=:5080:optiona l;TCP=:5080:optiona l;UDP=:5085:optiona l:name=sipLscConduit ;TCP=:5085:optiona l:name=sipLscConduit Replace each instance of 0.0.0.
Copyright © 2006 Nortel Networks Table 33 Web Client Manager tab (Sheet 2 of 2) Parameter Recommended value Audio RTP Port Low 50000 default Audio RTP Port High 50100 default Use SSL checked default Keep Alive Ping checked default Ping Time Out Timer 60 default Ping Interval Timer 120 default Connection Time Out Timer 360 default Allow Auto Login checked default Download JRE Version This field holds the version of the Java Runtime Environment (JRE) installer that the Web Cli
Copyright © 2006 Nortel Networks The shaded rows indicate values that must be addressed by the installer. Table 35 Database Base tab Parameter Recommended Value Notes Example Primary Host 192.168.14.21 120.120.13.22 Connections 5 default Secondary Host default 6 Click Apply. 7 The component will deploy. Wait until you see the dialog box indicating successful installation. The component will appear in the file tree.
Copyright © 2006 Nortel Networks 138 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Installing and configuring the Oracle Monitor Prerequisites Make sure the following are completed successfully: • The System Management Console has been installed and started. • A server definition has been created for the Oracle Monitor. Procedures Procedure 39 Adding the Oracle Monitor (Micro) to the System Management Console At the System Management Console, 1 Select Sites->MgmtSite->Servers->MgmtSvr.
Copyright © 2006 Nortel Networks 140 Procedure 40 Configuring the Oracle Monitor tabs ATTENTION Do not click Apply until you have finished configuring the component. At the System Management Console, 1 Use the values from the table that follows to complete the Oracle Server tab parameters. The shaded rows indicate values that must be addressed by the installer.
Copyright © 2006 Nortel Networks The shaded rows indicate values that must be addressed by the installer. Table 37 IMS Main Database tab (Sheet 1 of 4) Parameter Recommended value Notes SNMP request port 9161 default SNMP agent IP address 192.168.14.21 120.120.13.
Copyright © 2006 Nortel Networks Table 37 IMS Main Database tab (Sheet 2 of 4) Parameter Recommended value Gauged Component Monitoring: Threshold monitors: Positive going threshold value 1 70 default Gauged Component Monitoring: Threshold monitors: Positive going threshold hysteresis 1 5 default Gauged Component Monitoring: Threshold monitors: Positive going threshold value 2 85 default Gauged Component Monitoring: Threshold monitors: Positive going threshold hysteresis 2 5 default Gauge
Copyright © 2006 Nortel Networks Table 37 IMS Main Database tab (Sheet 3 of 4) Parameter Recommended value Notes Gauged Component Monitoring: Threshold monitors: Alarm Severity on Positive Going Threshold2 MINOR default Gauged Component Monitoring: Threshold monitors: Alarm Severity on Maximum Rate MAJOR default Gauged Component Monitoring: Threshold monitors: Alarm Severity on Upper Limit overrun MAJOR default Gauged Component Monitoring: Threshold monitors: Alarm Severity on Lower Limit
Copyright © 2006 Nortel Networks Table 37 IMS Main Database tab (Sheet 4 of 4) Parameter Recommended value Monitor functions: Polling interval (min) 1 default Monitor functions: Active checked default Monitor functions: Component name CacheHitRatio default Monitor functions: Polling interval (min) 1 default Monitor functions: Active checked default Trap handlers: Trap handler name oracleDBTrapHandler default Active checked default 3 Notes Example Use the values from the table
Copyright © 2006 Nortel Networks The shaded rows indicate values that must be addressed by the installer. Table 39 Oracle Listeners tab Parameter Recommended value SNMP request port 9161 default SNMP agent IP address 192.168.14.21 120.120.13.
Copyright © 2006 Nortel Networks 146 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Installing the iPlanet Monitor Prerequisites Make sure the System Management Console has been successfully installed and started. Procedures Procedure 41 Adding the iPlanet Monitor At the System Management Console, 1 Select Sites->MgmtSite->Servers->AppSvr 2 Click on the plus sign next to the server to which you are adding the component. 3 Right click on the Components folder. 4 Select Add -> Component. 5 A list of component loads appears in the Load List window.
Copyright © 2006 Nortel Networks Procedure 42 Configuring the iPlanet Monitor At the System Management Console, 1 ATTENTION Do not click Apply until you have finished configuring the tab. Use the values from the table that follows to complete the Web Monitor tab parameters. Note: The shaded rows indicate values that must be addressed by the installer.
Copyright © 2006 Nortel Networks Table 40 Web Monitor tab (Sheet 2 of 12) Parameter Recommended value Notes Example Component Monitoring: Threshold monitors: Lower Limit 0 default Component Monitoring: Threshold monitors: Negative going threshold value 10 default Component Monitoring: Threshold monitors: Negative going threshold hysteresis 5 default Component Monitoring: Threshold monitors: Positive going threshold value 1 70 default Component Monitoring: Threshold monitors: Positive go
Copyright © 2006 Nortel Networks Table 40 Web Monitor tab (Sheet 3 of 12) Parameter Recommended value Notes Example Component Monitoring: Threshold monitors: Alarm Severity on Negative going threshold NONE default Component Monitoring: Threshold monitors: Alarm Severity on Positive going threshold 1 WARNING default Component Monitoring: Threshold monitors: Alarm Severity on Positive going threshold 2 MINOR default Component Monitoring: Threshold monitors: Alarm Severity on Maximum Rate MA
Copyright © 2006 Nortel Networks Table 40 Web Monitor tab (Sheet 4 of 12) Parameter Recommended value Notes Example Component Monitoring: Threshold monitors: Negative going threshold value 10 default Component Monitoring: Threshold monitors: Negative going threshold hysteresis 5 default Component Monitoring: Threshold monitors: Positive going threshold value 1 70 default Component Monitoring: Threshold monitors: Positive going threshold hysteresis 1 5 default Component Monitoring: Thres
Copyright © 2006 Nortel Networks Table 40 Web Monitor tab (Sheet 5 of 12) Parameter Recommended value Notes Example Threshold monitors: Alarm Severity on Positive going threshold 1 WARNING default Threshold monitors: Alarm Severity on Positive going threshold 2 MINOR default Component Monitoring: Threshold monitors: Alarm Severity on Maximum Rate MAJOR default Component Monitoring: Threshold monitors: Alarm Severity on Upper Limit OverRun MAJOR default Component Monitoring: Threshold mo
Copyright © 2006 Nortel Networks Table 40 Web Monitor tab (Sheet 6 of 12) Parameter Recommended value Notes Example Component Monitoring: Positive going threshold value 1 70 default Component Monitoring: Positive going threshold hysteresis 1 5 default Component Monitoring: Positive going threshold value 2 85 default Component Monitoring: Positive going threshold hysteresis 2 5 default Component Monitoring: Capacity or max value 99 default Component Monitoring: Capacity or max hystere
Copyright © 2006 Nortel Networks Table 40 Web Monitor tab (Sheet 7 of 12) Parameter Recommended value Notes Example Component Monitoring: Component name Cpu Util default Component Monitoring: Polling interval in minutes 1 default Component Monitoring: Active for polling checked default Component Monitoring: Threshold monitors: Gauge name cpuUserTime default Component Monitoring: Threshold monitors: Upper limit 100 default Component Monitoring: Threshold monitors: Lower Limit 0 defa
Copyright © 2006 Nortel Networks Table 40 Web Monitor tab (Sheet 8 of 12) Parameter Recommended value Notes Example Component Monitoring: Threshold monitors: Positive going threshold hysteresis 2 5 default Component Monitoring: Threshold monitors: Capacity or max value 99 default Component Monitoring: Threshold monitors: Capacity or max hysteresis 0 default Component Monitoring: Threshold monitors: Alarm Severity on Negative going threshold NONE default Component Monitoring: Threshold m
Copyright © 2006 Nortel Networks Table 40 Web Monitor tab (Sheet 9 of 12) Parameter Recommended value Notes Example Component Monitoring: Threshold monitors: Usage state affected unchecked default Component Monitoring: Class name com.nortelnetworks.i ms.mw.probe.iplanet.
Copyright © 2006 Nortel Networks Table 40 Web Monitor tab (Sheet 10 of 12) Parameter Recommended value Notes Example Component Monitoring: Threshold monitors: Positive going threshold hysteresis 1 5 default Component Monitoring: Threshold monitors: Positive going threshold value 2 85 default Component Monitoring: Threshold monitors: Positive going threshold hysteresis 2 5 default Component Monitoring: Threshold monitors: Capacity or max value 99 default Component Monitoring: Threshold m
Copyright © 2006 Nortel Networks Table 40 Web Monitor tab (Sheet 11 of 12) Parameter Recommended value Notes Example Component Monitoring: Threshold monitors: Alarm Severity on Upper Limit OverRun MAJOR default Component Monitoring: Threshold monitors: Alarm Severity on Lower Limit UnderRun MAJOR default Component Monitoring: Threshold monitors: Usage state affected unchecked default Component Monitoring: Class name com.nortelnetworks.i ms.mw.probe.iplanet.
Copyright © 2006 Nortel Networks Table 40 Web Monitor tab (Sheet 12 of 12) Parameter Recommended value Notes Example Trap handlers: Trap handler name iPlanet Operation Trap default Trap handlers: Active checked default 2 Click Apply. Wait for the component to appear in server list. The iPlanet Monitor is installed on the same server as the Provisioning Module.
Copyright © 2006 Nortel Networks 160 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Verification procedures Verifying Server1 (DBSvr/MgmtSvr/AcctMgr) The following commands are executed on the database/management/accounting Sun Fire V100 server using PuTTY SSH into the machine logical IP address. Example: Open a PuTTY SSH session to 120.120.13.
Copyright © 2006 Nortel Networks interface is ‘UP.’ This example output shows that dmfe0 is assigned to IP address 120.120.13.20, its subnet mask is ffffff00, which translates to 255.255.255.0, and the interface is UP (active). 4 Look for the entry which starts with ‘dmfe1.’ The parameters that follow show the IP address, subnet mask, and whether the interface is ‘UP.’ This example output shows that dmfe1 is assigned to IP address 120.120.13.21, its subnet mask is ffffff00 which translates to 255.
Copyright © 2006 Nortel Networks 163 120.120.13.1 The only address in this file defines your default gateway route (your router). If this file is empty and the machine is rebooted, then you will not have network access to your other servers. Verifying Server2 (application server) The following commands are executed on the application server using PuTTY SSH into the machine logical IP address. Example: Open a PuTTY SSH session to 120.120.13.
Copyright © 2006 Nortel Networks 4 Look for the entry that starts with ‘dmfe1.’ The parameters that follow show the IP address, subnet mask, and whether the interface is ‘UP.’ This example output shows that dmfe1 is assigned to IP address 120.120.13.24, its subnet mask is ffffff00 which translates to 255.255.255.0, and the interface is UP (active). 5 Look for the entry that starts with ‘dmfe0:1.’ This is the machine logical interface.
Copyright © 2006 Nortel Networks 165 The only address in this file defines your default gateway route (your router). If this file is empty and the machine is rebooted, then you will not have network access to your other servers. Verifying the database load (imssipdb) deployment The initial deployment of the imssipdb load is command-line driven from the MgmtSvr. Updates to the imssipdb load in future loads will be handled through the System Management Console.
Copyright © 2006 Nortel Networks 166 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Appendix A Deploying the PC Client Along with the initial load, Nortel Networks delivers the following: • Java Network Launch Protocol (JNLP) file: pcclient.jnlp • Zip file containing latest code resources: pcclientcode.zip System administrators need to perform the following steps to deploy Multimedia PC Client loads. At the management pc, 1 Unzip the zip fle containing the code resources (pcclientcode.zip) onto any machine connected to the network.
Copyright © 2006 Nortel Networks 168 NN10364-301 MCS 5100 3.5 Standard 6.
Copyright © 2006 Nortel Networks Appendix B Reloading IP addresses after system installation This process prompts you for the hostname, country, time-zone, and IP address to enable movement of the system after the system is installed. You can re-enter the same data that was already in those parameters if they have not changed. You can change the system identification parameters and all IP addresses binding to a single interface without having to reload the OS from a CD.
Copyright © 2006 Nortel Networks 170 the server, which takes about five minutes, and then reload the IP addresses (see Procedure 46, Reloading IP addresses after system installation). Reloading the IP addresses on each server takes about 15 minutes. Procedure 46 Reloading IP addresses after system installation At the management pc, 1 Log in to the system as root through the console port connection. You must have the root password to apply this procedure.
Copyright © 2006 Nortel Networks 171 Type the number of your choice and press Return: Select 2 and press Enter. 7 See the instructions for installing Disk 1 in this document for more information on what to enter for the following items: • Networked • DHCP • Primary Network Interface • Hostname (You may have to backspace over the word "unknown" and type in the correct name.
Copyright © 2006 Nortel Networks 9 172 Follow the instructions for installing Disk 4 in this document. After step 13 in the instructions for installing the DBSvr1 or DVSvr2, you will see the following: Follow the instructions below as shown in this message that appears on your machine: Starting Oracle Intelligent Agent....
Copyright © 2006 Nortel Networks 173 b Then log in to the Accounting server and type in the following command: #/usr/local/bin/Interface.
Copyright © 2006 Nortel Networks 174 NN10364-301 MCS 5100 3.5 Standard 6.
Multimedia Communication Portfolio Multimedia Communication Server 2-server Sun Fire V100 Solaris Installation and Commissioning Guide Copyright © 2006 Nortel Networks. All rights reserved. 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.
