How it Works
Nortel
Loading...
V100
User Manual
192 pgs2.46 Mb0
Table of contents
Loading...

Nortel V100 User Manual

NN10287-301
Multimedia Communication Portfolio
Multimedia Communication Server
4-server Sun Fire V100 Solaris Installation and Commissioning Guide
MCS 5100 3.5 Standard 5.0 December 2006
3

Contents

Finding the latest updates on the Nortel web site . . . . . . . . . . . . . . . . . . . .7
How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Installation roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
MCS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Before you start the install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Key stroke symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Text conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Loading disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Total estimated time to install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Setting up the baseline MCS hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
MCS baseline checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Setting up rack to mount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Connecting the Sun Fire V100 server to the layer-2 switch . . . . . . . . . . . . . 24
Connecting the Sun Fire V100 server to the MRV terminal server . . . . . . . 25
Minimum and recommended requirements for customer-provided PC .27
Installing and accessing the MRV LX-4000 series terminal server . . . . .29
Installing Disks 1 to 3 on V100 servers . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Installing CD1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Installing CD2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Installing CD3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Installing Disk 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Database servers (DBSvr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Management/Accounting server (MgmtSvr/AcctMgr) . . . . . . . . . . . . . . . . . 52
Application servers (AppSvr [SIP Application Module,
IPCM/Web Client Manager/Provisioning Module]) . . . . . . . . . . . . . . . . 56
Installing Disk 5 (all servers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Enabling or disabling the automatic mount . . . . . . . . . . . . . . . . . . . . . . . .63
Installing Disk 6 (MgmtSvr and AcctMgr only) . . . . . . . . . . . . . . . . . . . . . .65
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
4
Installing Oracle 9.2.0.4 on the database server . . . . . . . . . . . . . . . . . . . . 67
Installing Oracle 9.2.0.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Deploying the initial database load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Deploying the database load (imssipdb) . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Deploying and starting the Sysmgr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Deploying and starting the Sysmgr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Sysmgr deployment verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Registering your license key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Installing and launching the System Management Console . . . . . . . . . . .93
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Installing the System Management Console . . . . . . . . . . . . . . . . . . . . . . . . 93
Launching the System Management Console . . . . . . . . . . . . . . . . . . . . . . . 94
Adding a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Adding a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Adding and configuring the Accounting Module . . . . . . . . . . . . . . . . . . .101
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Powering on the servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Adding and configuring the SIP Application Module . . . . . . . . . . . . . . .107
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Adding and configuring the IP Client Manager . . . . . . . . . . . . . . . . . . . . 119
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Installing the UFTP BaseSoftware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Add the UFTP to the System Management Console . . . . . . . . . . . . . . . . . 125
Configuring the Provisioning Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006
5
Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Adding and configuring the Web Client Manager . . . . . . . . . . . . . . . . . .133
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Installing and configuring the Oracle Monitor . . . . . . . . . . . . . . . . . . . . .139
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Installing the iPlanet Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Installing the H.323 Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
Installing the server for the H.323 Gatekeeper . . . . . . . . . . . . . . . . . . . . . 159
Initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Verification procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Sun Fire V100 H.323 Gatekeeper server verification . . . . . . . . . . . . . . . 168
Sun Fire V240 and Netra 240 H.323 Gatekeeper server verification . . . 170
Deploying the PC Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
Verifying the installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Verifying the database installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Verifying the Management/Accounting server installation . . . . . . . . . . . . . 177
Verifying the application server (AppSvr) installation
(SIP Application Module, IPCM, Web Client Manager,
Provisioning Module, H.323 Gatekeeper) . . . . . . . . . . . . . . . . . . . . . . 179
Verifying the application server (AppSvr) installation . . . . . . . . . . . . . . . 179
Verifying the IPCM/Prov/WCM installation . . . . . . . . . . . . . . . . . . . . . . . 181
Reloading IP addresses after system installation . . . . . . . . . . . . . . . . . .185
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
6
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006

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/es­erv/cs/main.jsp?cscat=SOFTWARE&resetFil­ter=1&tranProduct=12482
Latest Documentation
Nortel page for MCS 5100 documentation located at www130.nortelnetworks.com/cgi-bin/es­erv/cs/main.jsp?cscat=DOCUMENTATION&re­setFilter=1&tranProduct=12482
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
8
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006

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. From this site, you can:
• download software, documentation, and product bulletins
• search the Technical Support Web site and the Nortel Knowledge Base for answers to technical issues
• sign up for automatic notification of new software and documentation for Nortel equipment
• open and manage technical support cases
Getting help over the phone from a Nortel Solutions Center
If you do not find the information you require on the Nortel Technical Sup­port web site, and you have a Nortel support contract, you can also get help over the phone from a Nortel Solutions Center.
In North America, call 1-800-4NORTEL (1-800-466-7835).
Outside North America, go to the following web site to obtain the phone number for your region:
www.nortel.com/callus
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
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.com/erc
Getting help through a Nortel distributor or reseller
If you purchased a service contract for your Nortel product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller.
10
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006

Installation roadmap

This document aids in understanding the Multimedia Communication Server (MCS) Solution 4-server installation process. The rest of this document will refer to the example data in the figure that follows.
Print and refer to the figure of the example 4-server configuration while executing this installation.
Print your customer-specific information (CSI) datasheet and complete the information sheet with your own configuration to assist in executing this installation.
Configure the pc you are using for management services with an IP address that is in the same subnet of the IP address range used for the servers.
ATTENTION
ATTENTION
ATTENTION
Refer to the MCS 5100 Network Deployment and Engineering Guide, NN10313-191, that accompanies the MCS product for
customer-specific information (CSI) and system requirements.
Figure 1,
configuration.
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
Sample 4-server configuration illustrates a basic 4-server
Figure 1 Sample 4-server configuration
12
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006

MCS documentation

In addition to the following documentation, be sure to refer to the cus­tomer-specific information (CSI) datasheet for your specific system requirements.

Refer to the following documentation for the MCS 5100 system:

• MCS 5100 Network Engineering and Deployment Guide,
NN10313-191
• MCS 5100 Basics, NN10270-100
• MCS 5100 Feature Description Guide, NN10315-115
• MCS 5100 System Management Console User Guide,
NN10273-111
• MCS 5100 Accounting Module Basics, NN10279-111
• MCS 5100 SIP Application Module Basics, NN10259-111
• MCS 5100 Presence Basics, NN10263-111
• MCS 5100 Database Module Basics, NN10267-111
13
• MCS 5100 Management Module Basics, NN10268-111
• MCS 5100 Provisioning Module Basics, NN10274-111
• MCS 5100 Provisioning Client User Guide, NN42020-105
• MCS 5100 H.323 Gatekeeper Basics, NN10280-111
• MCS 5100 Interworking Guide, NN10372-111
• MCS Backup and Recovery Guide, NN42020-502
• MCS Accounting Common Call Scenarios Reference Guide,
NN10374-800
• MCS 5100 IP Client Manager Basics, NN10256-111
• MCS 5100 Web Client Manager Basics, NN10278-111
• MCS 5100 RTP Media Portal Basics, NN10265-111
• Provisioning Enhanced 911 User Guide, NN42020-132
• MCS 5100 Fault Management: Alarm and Log reference,
NN10385-900
• MCS 5100 Performance Management: OM reference, NN10386-700
• Personal Agent User Guide, NN42020-100
• Personal Agent Quick Reference, NN10290-001
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
• Bulk Provisioning Tool Reference Guide, NN42020-501
• Open Provisioning Interface Reference Guide, NN10309-316
• IP Phone 2002 User Guide, NN10319-113
• IP Phone 2002 Quick Reference, NN10301-001
• IP Phone 2004 User Guide, NN10042-113
• IP Phone 2004 Quick Reference, NN10307-001
• IP Phone 2007 User Guide, NN10042-114
• Media Application Server Network Deployment and Engineering Guide, NN10377-191
• MCS 5100 Ad Hoc Audio Conferencing Service Guide, NN10297-111
• Media Application Server Meet Me Audio Conferencing Service Guide, NN10303-111
• Media Application Server - Music on Hold Service Guide, NN10378-113
• Media Application Server Announcements Service Guide, NN10379-113
14
• Media Application Server IM Chat Service Guide, NN10380-113
• Media Application Server - Meet Me Audio Conferencing Quick
Reference, NN10283-001
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006

Before you start the install

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). Refer to the MCS 5100 Network Deployment and Engineering Guide, NN10313-191, that accompanies the MCS product for customer-specific information (CSI) and system requirements.
Read and understand the MCS 5100 Release Notes before installing the system.
Nortel strongly recommends the use of high-speed data network connectivity for optimum remote service capability. Without broadband connectivity, remote service options are limited. We recommend our Contivity Remote Access Solutions for this function.
Nortel also recommends following standard data center conventions for having a Universal Power Supply (UPS) as the power backup for the servers. For more information, refer to the MCS 5100 Network Deployment and Engineering Guide, NN10313-191, which shows how to connect servers to two different UPS systems for maximum uptime.
For power over Ethernet in the closet switches, Nortel recommends use of our Ethernet Switch 460 Power Over LAN layer 2 Ethernet switches.
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
These procedures assume that you are using the PuTTY VT100 terminal emulator tool.
To set up sessions, download from the web the PuTTY VT100 Emulator, a shareware configurator tool.
Download PuTTY from http://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.
• PC (for management administration). Refer to Minimum and
recommended requirements for customer-provided PC on page 27.
You must have access to the MCS network.
16
ATTENTION
ATTENTION

Acronyms

Make sure
• There are no other maintenance or provisioning activities pending, and no such activities are planned for the duration of the installation procedures and follow-up soak period.
• You have a detailed knowledge of your network’s configuration.
• You have proficiency using UNIX operating system commands.
• You have access and privileges to the network.
• You have authority or immediate access to people with authority to make decisions on any issues that may arise.
The following acronyms are referenced in this document:
• lights out management (LOM)
• Network Time Protocol (NTP)
• customer-specific information (CSI)
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006
17

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.
<Value in brackets> Enter value indicated in brackets.
[Enter] Press key indicated in brackets.

Text conventions used in this document

This document uses the following text conventions:
• Bolded type is used to signify commands or buttons that you must press to perform an action, for example, Apply.
• Courier type is used to signify what appears on screen, for example,
Enter your password.
• Italic type is used for emphasis, for special words, or for reference information; for example, "Log in as root."
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
18

Server configuration

The following table shows the basic setup of the 4-server configuration.
Table 0-1 4-server Sun Fire* V100 Solaris configuration
Configuration Server type Components
Sun Fire* V100 Management/Accounting
server
Database server Primary database
SIP Application Module (application server)
IPCM/Prov/WCM (application server)

Loading disks

MCS 5100 Release 3.0 Base Platform System SoftWare Kit NTVW01AJ contains multiple copies of the same CDs to allow simultaneous installation across servers. See Ta bl e 1 , Mapping of Kit
NTVW01BD disks to servers (with times), on page 19 for details. Nortel
recommends that all servers with the same CD numbers be installed at the same time to reduce installation time.
Active System Manager
Active Accounting Manager
Oracle Monitor
Active SIP Application Module
IPCM (S1)
Active Provisioning Module
Active WebClient Manager
iPlanetMonitor
UFTP Base Software
As shown in Ta ble 1 ,
Mapping of Kit NTVW01BD disks to servers (with times), Disks 1-5 have four copies each. Disk 6 only needs to go on the
Management/Accounting server. There are six Oracle disks, with one copy, going on the database server.
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006
19
MCS Base Platform System Software disks are loaded on the following servers as indicated in Ta ble 1 , Mapping of Kit NTVW01BD disks to
servers (with times)
Table 1 Mapping of Kit NTVW01BD disks to servers (with times)
V100 servers
MCS Base Platform System Software: Order code NTVW01BD
Approximate time to install
Database Server
Mgmt. / Acct. Server
Application Server
Management PC
IPCMProvWCM Server
CD1 (4 copies in each kit) Disk Partitioning & Solaris OS Kernel
CD2 (4 copies in each kit) Solaris OS Packages
CD3 (4 copies in each kit) Solaris Packages and Patches
CD4 (4 copies in each kit) MCP Installation & Commissioning
CD5 (4 copies in each kit) MCP Base Platform & 3rd Party Software
CD6 (1 copy in each kit) MCP Application Key coded S/W
CD7 (1 copy in each kit) MCP Element Manager Console
45 minutes X X X X
15 minutes X X X X
90 minutes X X X X
20 minutes +
XXXX disk mirroring, 10 minutes
30 minutes X X X X
20 minutes X
15 minutes X
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
20
Table 1 Mapping of Kit NTVW01BD disks to servers (with times)
V100 servers
MCS Base Platform System Software: Order code NTVW01BD
Approximate time to install
Database Server
Mgmt. / Acct. Server
Application Server
Oracle disks 1-6 90 minutes X
Management PC
IPCMProvWCM Server
Total (approximate) time per server.

Total estimated time to install

Refer to the following table for the estimated time to install the MCS 5100 servers.
Server Total I&C time
Management/accounting server 3.6 hours
Database server with 2 local hard drives 3.6 hours + 90 minutes
Application server with 2 local hard drives (Application servers include SIP Application servers, IP Client Managers, Provisioning Client, Web Client Manager, and H.323 Gatekeepers)
3.6 hours for each server, plus 90 minutes Oracle installation on Database server
for Oracle installation = 4+ hours total (approximate)
3.6 hours
Total installation time 5 hours (approximate)
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006

Setting up the baseline MCS hardware

MCS baseline checklist

See the following figure for an overview of hardware connections.
Figure 2 MCS hardware connections overview
ATTENTION
You need an uninterrupted power source (UPS).
If a power outage does occur, bring the database server into service before bringing the other servers into service. If other servers do not come up, restart the management server.
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
Recommended hardware for this configuration consists of four (4) Sun Fire V100 servers. The servers include:
• two (2), cat-5 Ethernet cables for each V100 server (for a total of eight (8) ethernet cables)
Note: Each V100 server uses two (2) ethernet cables to connect the V100 servers to the layer-2 switch.
• two (2) serial (NTVW01IM cable for Terminal server) cables for each V100 server (or a total of eight (8) serial cables)
Note: Serial cables are ordered with the MRV terminal server.
— one (1) cable for Serial Port A (LOM)
— one (1) cable for Serial Port B
• one (1) power cable
• LAN connection to the Layer-2 switch (Refer to layer-2 switch customer documentation for layer-2 switch settings.)
• Sun Fire V100 server documentation
22
• 40-GB hard drive (two [2] drives in each server for disk mirroring)
• 1-GB total memory
• Terminal server connected to the diag port
ATTENTION
You need to have the following:
• Business Policy Switch 2000 (BPS 2000) or Layer-2 switch
Check your vendor documentation for configuring your Layer-2 switch.
• one (1) additional cat-5 ethernet cable to connect the MRV terminal server to the layer-2 switch
• a PC for the management console, and access to the network
WARNING
Static electricity could be harmful to the server.
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006

Setting up rack to mount

Procedure 1 Setting up rack to mount
At the rack,
1 Mount all equipment on the rack: Refer to following diagram that
displays the mounting for the rack.
• Mount Layer-2 switch.
• Mount MRV terminal server.
• Mount Sun Fire V100s.
— Management/Accounting server
— Database server
— Application server
— IPCMProvWCM server
• (optional equipment) Mount conference server. Refer to the Media Application Server documentation for more information.
23
• (optional equipment) Mount gateway. Refer to customer-specific gateway installation documentation.
Note: All MCS 5100 equipment is 19-inch rack mountable.
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
Figure 3 MCS 5100 19-inch rack
24

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 4 Back view of Sun Fire V100 server
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006
Figure 5 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.
Do not power up the server at this time.
25
ATTENTION

Connecting the Sun Fire V100 server to the MRV terminal server

The MCS platform uses the Sun Fire V100 server medium configuration.
Note: This server is only available in an AC power configuration.
Procedure 3 Connecting the serial port on the V100 to the MRV terminal server
At the back of the Sun Fire V100 server,
1 Connect the Sun Fire V100 server A LOM serial port and B serial
port to the MRV terminal server:
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
Figure 6 Sun Fire V100 server network callouts
Note 1: 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 terminal server.
26
Figure 7 P1 and P2 custom cable connections to terminal server
See note
Note: This cable is only connected in order to configure the terminal server.
Following configuration, remove the cable.
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006

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.
Minimum and recommended requirements for the customer-provided management pc include (assuming you are not running anything else on the pc):
• processor:
— minimum: 600 MHz Pentium-class or equivalent processor.
— recommended: 1.0 GHz (or higher) Pentium-class or equivalent
processor.
• free RAM:
— minimum: 64MB of RAM. (This requirement is in addition to the
memory requirements of the operating system and other concurrent applications.)
— recommended: 64MB of RAM. (This requirement is in addition to
the memory requirements of the operating system and other concurrent applications.)
• free hard disk space:
— minimum: 50MB (If the System Management Console is
installed on a drive other than drive C, then 50MB of free space is required on that drive as well. In this case, the free 50MB on drive C will not be used, but is required for the installation to complete successfully.)
— recommended: 50MB (If the System Management Console is
installed on a drive other than drive C, then 50MB of free space is required on that drive as well. In this case, the free 50MB on drive C will not be used, but is required for the installation to complete successfully.)
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
• CD-ROM drive: required
• mouse: required
• Video Graphics Card:
— 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.x with Service Pack 5 (SP5)
— network connectivity: Ethernet network card
— web browser with Microsoft Internet Explorer 6.0, or later version
— web browser with Netscape Communicator 7.0, or later version
— cookies: enabled
28
— Javascript: enabled
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006

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.com.
Procedure 4 Connecting the MRV LX terminal server cable to the servers and management PC
At the terminal server,
1 Connect port 16 to the management PC using the console cable
and db9 connector that comes with the MRV LX terminal server.
Note: After the terminal server has been configured, the connection between the management PC and the terminal server is not needed, and the cable can be removed.
2 Connect the MRV terminal server 10 Base-T port to the layer-2
switch.
Refer to the Getting Started with the LX-4000 Series document in the CD that comes with your terminal server for specific information about the pinouts on your terminal server model.
Procedure 5 Accessing the MRV LX terminal server
At the browser address field,
1 Type in the IP address of your MRV LX terminal server. The LX
Series Configuration Console page appears, as shown.
MCS 4-server Sun Fire V100 Solaris Installation and Commissioning Guide
Figure 8 MRV Configuration Console window
2 Make sure you have the Java Plug-in installed.
30
3 When your browser connects to the terminal server, the Java
Security Warning window appears.
Figure 9 Java Security Warning pop-up window
NN10287-301 MCS 5100 3.5 Standard 5.0 December 2006
Loading...
+ 162 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use