Alcatel OmniPCX Enterprise

Blade Center

Installation Manual
NOTE:

Product specifications contained in this document are subject to change

without notice. Products and services described in this document may not be
offered in every country. For the most current information, please contact
your Alcatel representative or your Alcatel equipment provider.

Copyright (c) 2006 Alcatel. All rights reserved for all countries. This
document may not be reproduced in whole or in part without the express
written permission of Alcatel.

Alcatel® and the Alcatel logo are registered trademarks of Alcatel. All other
trademarks are the property of their respective owners.

The CE mark indicates that this product conforms to the following Council
Directives:
- 89/336/CEE (concerning electro-magnetic compatibility)
- 73/23/CEE (concerning electrical safety)
- 1999/5/CE (R&TTE)
   

 


Chapter 1
Overview

 Overview .................................................................................................... 1.1

Chapter 2
Hardware description

 Blade Center Components .................................................................. 2.1

 Power Supplies ....................................................................................... 2.2
 Blowers ...................................................................................................... 2.2
 Blade ........................................................................................................... 2.2
 Ethernet Access and Switch Module .............................................. 2.3

Management Module (MM) .................................................................. 2.4

 Switch KVM and USB Lane ......................................................................... 2.4

 Internal Management Network ................................................................... 2.5

 Serial Over LAN (SOL) ................................................................................ 2.6
 Media Tray ................................................................................................ 2.7

Chapter 3
Detailed description

 
 0-1
 
 




 Overview .................................................................................................... 3.1

 ESM Link Aggregation .......................................................................... 3.1
 Dividing the Network ............................................................................. 3.3
 Dividing the Network with ESM .................................................................. 3.3
 VLANs Created for Production Purposes ................................................. 3.4
 Configuring a VLAN for the OmniPCX Enterprise PC Installer ............... 3.4
 Voice Encryption ......................................................................................... 3.4
 Management VLAN ...................................................................................... 3.5
 Ethernet Redundancy and Load Balancing .................................. 3.8

Chapter 4
Specific Technical Data

 Dimensions ............................................................................................... 4.1

 Weight ........................................................................................................ 4.1
 Noise Emission ....................................................................................... 4.1
 Temperature ............................................................................................. 4.1

Chapter 5
Configuration procedure

 Configuring the Management Module (MM) ................................. 5.1

 Connecting to the MM ................................................................................. 5.1
 General Setting ............................................................................................ 5.1
 Configuring Network Interfaces ................................................................. 5.1
 Configuring Login Profiles ......................................................................... 5.3
 Rebooting the MM to New Configuration .................................................. 5.5

Configuration for MM Redundancy ............................................................ 5.5
 Recovering Default Network Configuration .............................................. 5.5
 Configuring SOL ..................................................................................... 5.5

0-2  

  
 




 Configure SOL in the MM ............................................................................ 5.5

 Configure SOL in the BIOS ......................................................................... 5.7
 Using SOL .................................................................................................... 5.9
 Using the Remote Control .................................................................. 5.10
 Starting the Remote Control ...................................................................... 5.10
 Ethernet Switch Configuration ......................................................... 5.11
 Connection .................................................................................................. 5.11
 Commands .................................................................................................. 5.11
 Downloading an OmniPCX Enterprise .......................................... 5.12
  Prerequisites ............................................................................................... 5.13
  Getting the MAC Address of the Blade .................................................... 5.13
  Blade Server Configuration for Network Boot ......................................... 5.14
  OmniPCX Enterprise Installer Configuration ........................................... 5.15
  Call Server OmniPCX Enterprise Boot ..................................................... 5.16
 
After Installation ......................................................................................... 5.17
  Installation of Call Server Patches ............................................................ 5.17

Firmware Update ................................................................................... 5.17

 Updating 8843 Blade Firmware ................................................................. 5.18

 Updating MM Firmware .............................................................................. 5.19

 Updating ESM Firmware ............................................................................ 5.20

Chapter 6
Configuration examples

 Basic Configuration .............................................................................. 6.1

 Configuration Information .......................................................................... 6.1

 ESM0 Switch Configuration ........................................................................ 6.2

 ESM0 Configuration Dump ......................................................................... 6.4

 EXTS0 External Switch Configuration ....................................................... 6.5

 Multi Enterprise Configuration .......................................................... 6.5

 Configuration Information .......................................................................... 6.6

 ESM0 Configuration .................................................................................... 6.8

 ESM0 Dump ................................................................................................. 6.11

 
 0-3
 
 




 ESM1 Configuration ................................................................................... 6.12

 ESM1 Dump ................................................................................................. 6.15


External Switch Configuration .................................................................. 6.17

 Blade Ethernet Interface Configuration .................................................... 6.17

0-4  

  

1 

1.1 Overview
A blade center is an IBM rack which can host up to 14 processor boards called blades. Each
blade can host a server.
Each blade is built around an Intel Xeon microprocessor. Each blade has its own RAM and its
own SCSI disks. In addition, a blade has two (1xGigabit) Ethernet interfaces.
The blade center can replace up to 14 separate servers. The blade center is more compact
and offers maintenance and redundancy facilities.
Alcatel applications, such as a Call Server or OmniVista 4760 server can be hosted on a
blade. Alcatel and non Alcatel applications can coexist in the same blade center.
___change-begin___
___change-end___
Figure 1.1: Example of Blade Center Integration in an Alcatel Voice Network
The blade center is intended to be used in a large PCX private network. It can be also used by
an operator providing telephony services to customer companies.
The present documentation describes the blade center selected by Alcatel only, it includes a
short description and information on how to load and operate a Call Server on a blade.
For more information on the blade center itself, see the IBM Blade Center documentation.

    ! "##$ 1-1

Chapter 1 "##$

1-2     ! "##$

  

2
   

2.1 Blade Center Components

___change-begin___
___change-end___
Figure 2.1: Components
Alcatel has selected the 8843 blade center from IBM. The selected configuration includes a 7
U standard chassis which can contain:
1. Up to 14 blades
2. Up to 4 Power supply Modules (PM)
3. Up to 2 fans modules - also called blowers
4. Up to 2 Ethernet Switch Modules (ESM) also called Embedded Switch Module or Switch
Module (SM). Alcatel has selected an ESM provided by Nortel
5. Up to 2 Management Modules (MM)
6. A media tray which supports a floppy disk drive, an optical drive and a USB port
___change-begin___
%    ! &$ % 
2-1
Chapter 2 &$ % 

___change-end___
Figure 2.2: Blade Center Components Location

Note: SM3 and SM4 are not present in the configuration selected by Alcatel.
This section is a brief overview of the different units of a blade center. For more information,
see: IBM: Blade Center HS20 Installation and User's Guide and IBM: Hardware maintenance
manual and troubleshooting guide.

2.2 Power Supplies

The blade center has up to 4 power supplies also called Power Modules (PM). The 2000W
power supply module has been selected by Alcatel.
The PM1 unit supplies the blades plugged in slots 1 to 7. The PM2 unit (optional) is the backup
power supply for PM1.
The PM3 unit, with its PM4 backup optional unit, supplies the blades in slots 8 to 14.

2.3 Blowers
A blower unit, and its optional backup cools down the blade center. The blower throughput
depends on the internal and external temperature and on electric consumption.

2.4 Blade
A blade is a processor board. The blade selected by Alcatel has:
- A bi processor central unit built around an Intel Xeon microprocessor
- Up to 8GB DIMM RAM
- Up to 2x 73 GB SCSI hard disk
- 2x 1 GigaBit Ethernet ports

2-2 %    ! &$ % 

 &$ % 

2.5 Ethernet Access and Switch Module

___change-begin___
___change-end___
Figure 2.3: Internal and External Ethernet Network
Each ESM has:
- Fourteen 1 Gigabit interfaces (called internal connections) connected to the blades through
the backpanel
- Four 1 Gigabit interfaces (called external connections) for connections to external switches
- One 100base T interface to connect the internal management network
Each blade has two 1 Gigabit Ethernet interfaces. Blades have the following working mode:
- Basic Ethernet network: in this mode, only one interface is configured. The second ESM is
not used.
- Redundant Ethernet network: in this mode (also called failover), one interface is active and
the other one is in standby. The blade checks the active interface status. When the active
interface fails, the blade switches to the standby interface. This working mode requires a
customer network allowing the rapid spanning tree facility.
- Load balancing Ethernet network: in this mode, the two Ethernet interfaces are active. The
network load is shared between these two interfaces.
An ESM supports the following facilities:
- VLAN: frames tagging and frames filtering according to the 802.1q standard
- Link aggregation: several Ethernet link can be aggregated in a trunk in order to increase

%    ! &$ % 

2-3
Chapter 2 &$ % 

throughput. The aggregation is performed according to the Lacp (802.3ad) standard.

- Rapid spanning tree: the ESM can be connected to an Ethernet network supporting
redundancy and load balancing. In this case, the 802.1w: Rapid Spanning Tree standard
must be used between internal and external switches.
In addition, the Ethernet redundancy allows firmware upgrade, reboot, and test of an Ethernet
module with no impact on service.

2.6 Management Module (MM)

The Management Module allows the configuration of the blade center.
The Management Module has the following external accesses:
- A 100 base T Ethernet port to connect to the external management network
- Connectors for a Video monitor, a USB keyboard, a USB mouse
In the blade center, the MM is connected to the internal management network.
A second optional module can be plugged for redundancy.

2.6.1 Switch KVM and USB Lane

The MM acts as a switch KVM (Keyboard, Video, Mouse), i.e. the monitor, the keyboard and
the mouse can be connected to a given blade for maintenance purpose.
The management module can also switch the media tray, i.e. the optical drive, the floppy drive
or the USB port can be connected to a given blade for maintenance purpose.
___change-begin___
2-4 %    ! &$ % 

 &$ % 

___change-end___
Figure 2.4: Management Module Maintenance Facilities
For redundancy purpose, a second keyboard, monitor, mouse can be connected to the
standby management module. Only one management module is active at a given time.

2.6.2 Internal Management Network

The management module allows the blade center manager to connect to the internal
management network (also called management LAN). Through the internal management
network, the manager can reach ESMs.
There is no connection between the internal management LAN and the blade LAN.
___change-begin___
%    ! &$ % 
2-5
Chapter 2 &$ % 

___change-end___
Figure 2.5: Internal Management Network Access
Alcatel recommends to connect the management module to a management network.
The SMB bus (Serial Measuring Bus) is used for hardware features, such as temperature
measurements or hardware resets.

2.6.3 Serial Over LAN (SOL)

The MM allows a serial access to a blade. On a blade, a serial port emulation offers similar
facilities to those of a COM2 port. The SOL uses the internal management network to access
blades.
___change-begin___
2-6 %    ! &$ % 

 &$ % 

___change-end___
Figure 2.6: SOL Architecture
The serial information is sent over the internal management network. The ESM is used and
must be operational. A specific VLAN is created to avoid network conflict.
When a Nortel switch is used as an ESM, the VLAN 4095 (default VLAN, factory installed)) is
used for SOL.
Restrictions:
- The SOL access does not support a modem or UPS monitor
- The eth0, 19200, 8n1, COM2 SOL characteristics cannot be modified
- Only one SOL session per blade is available
- A SOL session is lost at:
• Blade reboot
• ESMO reboot
• Configuration of the blade Ethernet interface

2.7 Media Tray

The media tray supports:
- A USB port

%    ! &$ % 

2-7
Chapter 2 &$ % 

- A USB floppy disk

- A USB optical disk (DVD drive)
The media tray can be connected to a blade under the control of the MM.

2-8 %    ! &$ % 

  

3   

3.1 Overview
The blade center has been designed to host servers (voice or data). Each server has:
- A loading and maintenance phase. In this phase, the blade center administrator works with
specific blade center tools (e.g. MM).
- A production phase. In this phase, the server administrator is connected to the server
hosted on the blade. Blade Center maintenance facilities are no longer used.

3.2 ESM Link Aggregation

The ESM is a switch built to connect the blades to the IP network. The ESM switch must be
connected to an external switch or router.
Up to 4 Ethernet links can be aggregated in a trunk to increase throughput. The LACP 802.ad
standard is used to aggregate the links. The external switch must be configured to accept
these trunks.
___change-begin___
'    ! ( % 
3-1
Chapter 3 ( % 

___change-end___
Figure 3.1: Link Aggregation with or without Redundancy

3-2 '    ! ( % 

 ( % 

Note: A direct connection between the ESM and a host is technically possible, but not recommended as it
requires the use of an external port on the switch.

3.3 Dividing the Network

VLAN facilities are used to divide the network according to applications.
The VLAN facilities allow to:
- Divide traffic
- Limit flooding
- Improve security

3.3.1 Dividing the Network with ESM

The ESM allows VLAN filtering and tagging by port:
- VLAN filtering: only the frames tagged with one of the defined VLANs can access the port
- VLAN tagging: the incoming frames are tagged with the VLAN defined for the port used
___change-begin___
___change-end___
Figure 3.2: Example of VLAN by Port

'    ! ( % 

3-3
Chapter 3 ( % 

3.3.2 VLANs Created for Production Purposes

Alcatel recommends to divide the network into several VLANs:
- VLAN(s) for voice. In multi-tenancy cases, one VLAN must be created for each company
- One or more VLAN for data applications
- VLAN for management purposes

3.3.3 Configuring a VLAN for the OmniPCX Enterprise PC Installer

A specific VLAN must be created between the blade and the OmniPCX Enterprise PC server.
The boot server discovery frame reaches the PC Installer without broadcasting to the rest of
the network. This VLAN works as a point to point line.
___change-begin___
___change-end___
Figure 3.3: VLAN Created for Loading Purposes
When the Call Server is loaded, the segment of the VLAN between the blade and the ESM
must be deleted. This segment must be switched to the production VLAN. Other segments can
be kept for a new loading session, an upgrade for example.

3.3.4 Voice Encryption

3-4 '    ! ( % 

 ( % 

On a secured telephone network, voice and signaling are encrypted. Encryption is performed
by external modules: the SSM (Server Security Module) and the MSM (Media Security
Module) provided by Thales. For more information on IP security, see: module IP Touch
Security - Overview .
A VLAN is created between the Call Server and the SSM for the clear segment of the
communication. This VLAN acts as a point to point line. The clear text segment must be
located in a trusted area.
Another VLAN is created for the encrypted segment.
___change-begin___
___change-end___
Figure 3.4: VLAN Creation for Voice Encryption

Note: The SSM and MSM do not support redundancy: there is no backup for SSM or MSM.
Configurations with a redundant Ethernet network do not support encryption.

3.3.5 Management VLAN

Creating a management VLAN is recommended for security reasons. Only authorized staff

'    ! ( % 

3-5
Chapter 3 ( % 

must be allowed to reach the management network.

The OmniVista 4760 application is the management tool for Call Servers. This application is
included in the management VLAN and must also be connected to the Call Servers located in
the blade center. As Call Servers belong to an operational VLAN, a router must be located
between the OmniVista 4760 and the Call Servers. This router enables VLAN conversion. To
improve security, this router must filter calls, using static routes, static NAT (Network Address
Translation) or Access Control Lists.

3-6 '    ! ( % 

 ( % 

___change-begin___
___change-end___
Figure 3.5: Example of Management VLAN (Simplified)
In the example above, the management VLAN (in dotted lines) includes management stations,
the MM and OmniVista 4760.
The router/firewall is connected to the management VLAN. This router allows VLAN
conversion to connect the OmniVista 4760 to Call Servers. This router prevents external calls
from reaching the management VLAN.
A management VLAN, including an OmniVista 4760, can coexist with a redundant or load

'    ! ( % 

3-7
Chapter 3 ( % 

balancing configuration.

3.4 Ethernet Redundancy and Load Balancing

The blade hardware provides two Ethernet controllers. On the blade, the redundancy and the
load balancing features are performed by the operating system: an additional driver manages
the two controllers through the Ethernet driver.
___change-begin___
___change-end___
Figure 3.6: Ethernet Interface Software Architecture
On the blade, the operating system must be managed. Three configurations are allowed:
- Basic configuration: only one interface is configured and active.
- Redundancy: one interface is active, the other one is in standby. The blade monitors
interfaces. In case of failure, the system switches to the operational interface. This working
mode requires a redundant customer network allowing rapid spanning tree.
___change-begin___
3-8 '    ! ( % 

 ( % 

___change-end___
Figure 3.7: Example of a Redundant Configuration:
1. When all the units are operational, route 1 is used (according to the link cost
configuration)
2. The alternate route 2 is used in case of External Switch 0 failure. The spanning tree
function opens the blocked link ESM0 - External Switch 1.
3. The alternate route 3 is used in case of ESM0 failure. The blade system detects a
failure on Ethernet interface Eth0 and switches to Ethernet interface Eth1.
- Load Balancing: the two interfaces are active at the same time. The bonding driver shares
the load between the two interfaces.
This working mode requires a customer network divided in 2 network branches. The 2
network branches must be independent and lead to the same router. This router must
support the network load balancing feature.
___change-begin___
'    ! ( % 
3-9
Chapter 3 ( % 

___change-end___
Figure 3.8: Example of a Load Balancing Configuration
Route 1 and route 2 use two different network branches. A frame is routed through the left
or the right branch according to the share policy defined on the router and on the blade.
The two network branches can also support rapid spanning tree (redundancy). The links
(in dotted lines) provide redundancy in case of failure on a branch and/or an ESM.

3-10 '    ! ( % 

  

4   

Caution:
The Blade Center follows specific installation rules as described in the document:
Planning and Installation Guide from IBM available on IBM web site. Specific
considerations must be taken into account concerning dimensions, weight distribution,
noise and thermal dissipation.

4.1 Dimensions
- Width 444 mm (17.5 in.)
- Height 304.2 mm (12 in.)
- Depth 711.2 mm (28 in.)
A Blade Center unit uses 7U of vertical rack space. The following clearances are required
inside the rack:
- 50 mm (1.96 in.) on each side of the chassis
- 100 mm (3.93 in.) at the back of the chassis for cables

4.2 Weight
Up to 140Kg (310lbs) according to configuration.
For more information, see: Planning and Installation Guide from IBM.

4.3 Noise Emission

Up to 7.4 bels per Blade Center. An optional acoustics module is available to dampen the
noise generated by the blowers.
For more information, see: Planning and Installation Guide from IBM.

4.4 Temperature
0 to 32°C (32-89°F). The electric power is up to 4 x 2000W (according to configuration), a
cooling room can be required.
For more information, see: Planning and Installation Guide from IBM.

!)    ! * %+% ,%-

% ( 4-1
Chapter 4 * %+% ,%-
% (

4-2 !)    ! * %+% ,%-

% (
  

5  

This document presents a basic configuration. For more information, see: Blade Center
Management Module User's Guide.

5.1 Configuring the Management Module (MM)

This configuration is done the first time the MM is started or after the network parameters have
been erased. This can be achieved by pressing the reset button for 3 seconds.

5.1.1 Connecting to the MM

Connect a cable from your PC to the MM Ethernet port. The MM uses the default IP address:
192.168.70.125/24. Change the IP settings of your PC to netmask 255.255.255.0 and the IP
address to 192.168.70.100 (for example).
Open a web browser and enter the URL: http://192.168.70.125. When the MM is accessed the
first time, or after a version upgrade, the browser prompts for a certificate that must be
accepted to start a session.
Use the default login and password to connect to the MM. Enter USERID in the login field, and
PASSW0RD in the password field.

5.1.2 General Setting

Set the name, location and person to contact in this tab. Check that date and time are
accurate.

5.1.3 Configuring Network Interfaces

Four IP addresses (in the same subnet) are required to configure blade center modules:
- 2 IP addresses for MM (external and internal interfaces)
- One IP address for each ESM
___change-begin___
    ! 
+.
% 5-1
Chapter 5 
+.
%

___change-end___
Figure 5.1: Management Interface Configuration
On the MM web interface, go to: MM Control -> Network Interfaces -> External Network
Interface (eth0).
___change-begin___
5-2     ! 
+.
%
 
+.
%

___change-end___
1. DHCP mode: select Disable
2. Enter hostname
3. Enter IP address, subnet mask, Gateway address for the external interface if DHCP is
disabled
4. Enter the IP address, subnet mask, Gateway address for the internal interface eth1
5. Click save. The configuration takes effect after the reboot of the MM.
Note: The standby MM is automatically configured by copy. The IP addresses for the 2 MM interfaces are
identical but these interfaces are not active at the same time.
To configure the ESM IP addresses, go to the I/O Module Tasks -> Configuration panel.
___change-begin___
___change-end___
1. Enter the IP address, subnet mask, default gateway for Bay 1 (ESM0) and Bay2 (ESM1).
2. Save the configuration

5.1.4 Configuring Login Profiles

Logins cannot be shared among connections from web browsers: it is necessary to create a
login profile for each WEB session.
On the MM web interface, go to MM Control -> Login Profiles -> Login Profiles. Up to 12
profiles can be configured. Click on a login profile to open the login profile dialog box.
___change-begin___
    ! 
+.
% 5-3
Chapter 5 
+.
%

___change-end___
___change-begin___
___change-end___
1. Enter login and password

5-4     ! 

+.
%
 
+.
%

2. Select role
3. When the option Custom is selected, specify Assigned roles
4. Set the access scope of user profile
5. Save this configuration
Note: The MM password cannot be reset. If the management password is forgotten, the MM must be
replaced by IBM.

5.1.5 Rebooting the MM to New Configuration

1. Check the configuration (see note below)
2. Go to MM Control -> Restart MM -> Restart
3. Close the web browser, open it again and try to reconnect (with the address configured
above) after a few minutes
Note: The default (or factory) network configuration can be recovered as described: § Recovering Default
Network Configuration .

5.1.6 Configuration for MM Redundancy

Redundancy of MMs is provided when 2 modules are installed.
The two modules are connected to the same management network. Only one management
module must be configured. Its configuration is automatically copied to the redundant MM.
In case of failure of the primary MM, the redundant MM takes over on the same IP address.
Note: Each MM must be connected to a KVM, or a KVM switch

5.1.7 Recovering Default Network Configuration

If the network configuration has been improperly performed, it may be necessary to reset the
network configuration to default values. This is done by holding the reset button of the MM for
3 seconds.
The procedure is described: IBM: BladeCenter Management Module User’s Guide.

5.2 Configuring SOL

5.2.1 Configure SOL in the MM

Open a web browser in the web interface of the management module. Go to the Blade task ->
Serial Over LAN page.
___change-begin___
    ! 
+.
% 5-5
Chapter 5 
+.
%

___change-end___
From the Serial Over LAN Status page, it is possible to enable/disable the SOL feature:
1. Select the blade by clicking in the checkbox
2. Click on Enable Serial Over LAN or Disable Serial Over LAN
3. Click on Save
Configuring SOL Interface:
___change-begin___
5-6     ! 
+.
%
 
+.
%

___change-end___
- Serial over LAN: select Enabled/Disabled
- SOL VLAN ID: enter the VLAN identifier for SOL. This identifier must be the same for all
blades. When a Nortel switch is used, the VLAN ID must be 4095.
- BSMP IP address range: enter the IP address for the SOL port. Ensure that this address
does not conflict with the IP addresses used by the blade servers
Other parameters: Alcatel recommends not to change default values.
Note: Serial emulation characteristics: eth0, 19200, 8n1, COM2 cannot be modified. The blade processor
must be configured to accept these characteristics. The COM2 port configuration is done according to the
operating system loaded on the blade, see the operating system documentation, if need be.

5.2.2 Configure SOL in the BIOS

Reboot the blade server and use the F1 key to access the BIOS. Enter the "Devices and I/O
Ports" menu.
- Set the "Serial Port A" and "Serial Port B" to Autoconfigure as shown on the screen
below.
___change-begin___
    ! 
+.
% 5-7
Chapter 5 
+.
%
___change-end___
- Enter the "Remote Console Redirection" menu and configure the remote console as the
scree below: Enable the remote console, set port to COM2 speed and framing format to
19200, 8N1.
This configuration is mandatory, SOL is neither supported at other speed, nor on COM1.
___change-begin___
5-8     ! 
+.
%
 
+.
%
___change-end___
5.2.3 Using SOL
The SOL session is started with a telnet (or ssh) session on the MM.
The command console –T system:blade[X] starts a SOL session with blade number X.
The SOL has an inactivity timeout that can be disabled with the command: telnetcfg –t 0 –T
system:mm[1].
Example: opening a SOL session on blade 8, on the blade server management module
bcmm10.
 
 
 


 
 



  !"!
#$ %&'() 
*$ ++++++++++

 , $ -. /
0
 1234 
 $ 5

1. Starting a telnet session to bcmm10 (MM)

2. Authentication on bcmm10
3. Starting a SOL session on blade 8 (OmniPCX Enterprise)
4. Authentication on OmniPCX Enterprise

    ! 

+.
% 5-9
Chapter 5 
+.
%

5.3 Using the Remote Control

A VGA video, a keyboard and a mouse can be connected to the MM. These devices can be
connected to the blades using the KVM (Keyboard, Video, Mouse) switch embedded on the
MM. This feature is called Remote Control.
The remote control is shared between the 14 blade servers.
The remote control cannot be shared between users. It is recommended to use the Remote
Control for installation stages and to opt for a network remote connection as soon as possible
(SSH, telnet, remote desktop), once the network is configured.

5.3.1 Starting the Remote Control

The remote control is started from the MM web interface: Blade Tasks -> Remote Control ->
Start Remote Control.
___change-begin___
___change-end___
The remote control applets are downloaded the first time it is used. Ensure that the Java
Runtime Environment is installed on your workstation.
e.g. Windows XP SP1, Firefox or Internet Explorer browser require a Java environment of
1.4.2 or higher.
Remote control window:
___change-begin___
5-10     ! 
+.
%
 
+.
%

___change-end___
1. Select the blade owner of the KVM and of the media tray
2. The CTRL, ALT, TAB, F1, Insert, Caps Lock, Num Lock, Scroll Lock are emulated on the
remote console panel
3. The keyboard layout of the remote console must be configured to match the keyboard
layout of the workstation.

5.4 Ethernet Switch Configuration

This section describes basic commands of the ESM through the command line interface. For
more information, see: the ESM manufacturer documentation.

5.4.1 Connection
The Ethernet switch is addressed through the connection to the management module. To
connect to the switch: open a telnet session to the IP or DNS name of the switch.
The default login is admin and the password is admin.

5.4.2 Commands
5.4.2.1 Specific Commands
- Assigning an IP address to an interface :
6
7
7 87
 # 
 999999999999 :(2  7   7

; 999999999999 :&#  ;
< 8<  :=>0? 7 *  7
  

 :#  
* :7# *
 999999999999 :(2  7   *
< 8<  :=>0? 7 *  7# *  


- Port tagging (802.1q):

    ! 

+.
% 5-11
Chapter 5 
+.
%

6
7
 8 
< 8=  :=>0? 
  
 : 
<

- Creating a VLAN:
6
7

 8 :=>0? 
7 8  :      =>0?
  :=>0? 
<

- Link aggregation (definition of 802.3ad by IEEE):

6
7



 8 # 
 
< : 
< 7   
; 8; #  :; 

- Rapid spanning tree (802.1w) activation:

6
7
 8 
77*   :77* 
< 7   '  



 8@@#  :
 7  # 7   &2
 :# 
<
 8  :     &2

 8
  :
    ;

5.4.2.2 List Commands

- List port configuration
66

- List vlans
666<

- List trunks
666#

5.4.2.3 General Commands

- Telnet cli inactivity timer, set to 60 min.
6
766 A

- Reset to retrieve default values.

6 6
767

6 6

- Save configuration to flash

6<

5.5 Downloading an OmniPCX Enterprise

Downloading an OmniPCX Enterprise on a blade and downloading an OmniPCX Enterprise on
a crystal CPU (or common hardware CPU) is rather similar, with the difference that direct

5-12     ! 

+.
%
 
+.
%

access to the blade is not possible. However, a specific VLAN can be created as described:
module Blade Center - Detailed description § Configuring a VLAN for the PC Installer .
For more information on OmniPCX installation, see: module Standard Call Server installation -
Overview .

5.5.1 Prerequisites
You will need:
- Console access to MM (KVM connected to the MM or a remote Web browser connected to
the MM)
- The OmniPCX PC Installer software with
- A Call Server R7.0 or higher
- The PC Installer and the blade must be in the same VLAN. A temporary VLAN move may
be necessary. No router is allowed between the PC Installer and the blade (the DHCP
protocol is used)
- The Call Server installation requires the use of the first Ethernet interface (eth0) of the
blade server. The default path goes through ESM0. To use the path going through ESM1,
for the installation and the operation of the Call Server, the Ethernet controller 1 must be
disabled in the BIOS. The procedure is “F1” to enter the BIOS, select Device and I/O Ports
and disable Planar Ethernet 1
- Open a SOL session on the Call Server blades before starting installation

5.5.2 Getting the MAC Address of the Blade

The MAC addresses of the blade server are found in the Hardware VPD tab.
___change-begin___
    ! 
+.
% 5-13
Chapter 5 
+.
%

___change-end___
Note: In the default BIOS configuration, MAC Address 1 of Ethernet port 1 must be used to instal the call
server. Installation through Ethernet Port 2 is possible, if Ethernet port 1 has been disabled in the BIOS.

5.5.3 Blade Server Configuration for Network Boot

In the Blade Tasks -> Configuration select the blade server to install. In the example below,
blade 8 is installed.
___change-begin___
___change-end___
Set the boot sequence to Network – PXE and save.
___change-begin___
5-14     ! 
+.
%
 
+.
%

___change-end___
Blade server 8 is ready for network installation. When installation is finished, set the boot
sequence to Hard Drive 0 in order to boot from the disk.

5.5.4 OmniPCX Enterprise Installer Configuration

The version of OmniPCX Enterprise installer must be above 2.20.
Start the OmniPCX Enterprise PC Installer and select the Linux + Call handling installation
type.
On the installation parameters panel, select the Call Server as Blade Server, the installation
type as standard, the Network type as Company network. Set the IP address for the system
and the Ethernet MAC address of the blade.
Restart the blade (Blade Tasks -> Power/Restart on the MM console) to start network boot.
___change-begin___
    ! 
+.
% 5-15
Chapter 5 
+.
%

___change-end___
5.5.5 Call Server OmniPCX Enterprise Boot
___change-begin___
___change-end___
Select Standard installation and enter the path of the telephonic application on the installer.
Note: The default keyboard layout is QWERTY.
___change-begin___
5-16     ! 
+.
%
 
+.
%

___change-end___
5.5.6 After Installation
The remote console (KVM) is used during the Call Server installation process.
The console of production systems is SOL by default. When the installation is over, a SOL
session must be opened on the blade to complete Call Server configuration.
The security configuration of the Call Server must be performed via the SOL console.

5.5.7 Installation of Call Server Patches

Call Server patches are first downloaded on the OmniPCX Enterprise installer, then
transferred via the network to the Call Server.

5.6 Firmware Update

The firmware version can be displayed from a web browser connected to the MM.
Select Monitors -> Firmware VPD
___change-begin___
    ! 
+.
% 5-17
Chapter 5 
+.
%

___change-end___
___change-begin___
___change-end___
This page lists the revision numbers of BIOS, Ethernet switch modules and the MM.
The firmware update can be obtained from the IBM support site: http://www.ibm.com/support

5.6.1 Updating 8843 Blade Firmware

This update can be done with the BIOS update floppy inserted in the floppy drive of the blade

5-18     ! 

+.
%
 
+.
%

center, or remotely with the MM web interface.

For remote update(s) of the BIOS, insert the BIOS update floppy in the Windows workstation
and proceed as follows.
1. In the MM Remote control, set the KVM and media tray owner to the blade server to
update.
___change-begin___
___change-end___
2. In the Remote Disk panel select Removable Drive A
3. Click yes in the Remote Disk On Card dialog box
4. Wait until the floppy is loaded, then boot the blade server on the floppy
5. Once the BIOS update terminates, change the boot configuration of the blade server

5.6.2 Updating MM Firmware

1. Download the MM firmware on your workstation and the accompanying release notes from
the IBM support site
2. Unpack the ZIP file in a directory on the Windows workstation. The MM firmware is split in
2 files, which must be flashed, in the following order:
• CNETMNUS.PKT
• CNETRGUS.PKT
3. In the MM web interface, select MM Control -> Firmware Update
4. Select the first firmware file. Click Open, then click Update
___change-begin___
    ! 
+.
% 5-19
Chapter 5 
+.
%
___change-end___
5. Once the three files have been flashed, the MM must be restarted using the MM Control
-> Restart MM -> Restart button

5.6.3 Updating ESM Firmware

A tftp server on the management network is required. The new ESM firmware must be loaded
on this tftp server.
For security reasons, the ESM Bios has 2 partitions (image1 and image2): one active and one
standby. When download is completed on the standby partition, switch partitions and reboot.
1. From the workstation web browser, connect to the ESM to update
2. Use the /boot/gtimg command to download the firmware from the tftp server
Example:

5-20     ! 

+.
%
 
+.
%

 B 1: gtimg

  7 *
7*    

-CCDCCDC C.$ image2
   (2  7 E2 <$ 172.25.54.158
  7 7  E2 <$
/bootp/nortel/GbESM-AOS-20.2.2.2-os.img
 
# 
?* * * 
  *   7
C6 66F &G,01&, ,C
7 E2 < 5
37 *  -6.$y
& *
E  <
)* 

( *
 //5H 
I  7   ;  # H 
 2 *
I
 //5H J * <7 E>0&K
=7
 7 *   E>0&K #

7#
 *
 &7* =  
%   &*
(  =  IG   
%   &*
(  ? 01& (
%   &*
(  )  6 H6 &*

# 
 
7* 
) # * 
      * L -6. y
M  $H$/ (?E1 $  * 7  5J
7
!6 66F &G,01&, ,!J 7* <  

3. Reboot the ESM with the /boot/reset command

    ! 

+.
% 5-21
Chapter 5 
+.
%

5-22     ! 

+.
%
  

6  

6.1 Basic Configuration

This configuration example applies to:
- One company (no multi-tenancy feature)
- Single network (no Ethernet redundancy)
- Several VLANs
___change-begin___
___change-end___
Figure 6.1: Basic Configuration Layout

6.1.1 Configuration Information

Active Equipment IP Addressing:
ESM0 : 192.168.20.1
ExtS0 : 192.168.20.2
Gateway : 192.168.20.254
Mask : 255.255.255.0
VLANs (802.1q):

)    ! 

+.
  6-1
Chapter 6 
+.
 

ID Name Subnet IP/mask

1 Default
2 Management 192.168.20.0/24
3 Entreprise 1 Voice 192.168.30.0/24
4 Entreprise 1 Data 192.168.40.0/24

Link Aggregation (lacp 802.3ad):

ID Src Dst Key Port src Port dst
Lag0 ESM0 ExtS0 5 EXT1 EXT2 EXT3 EXT4 1/3 1/5 1/7 1/9

Server Interface Addressing:

Server eth0 - eth1 (bonding 0) mask
4760 192.168.20.1 255.255.255.0
E1-voix 192.168.30.1 255.255.255.0
E1-data 192.168.40.1 255.255.255.0
Router VLAN 2 192.168.20.254 255.255.255.0
Router VLAN 3 192.168.30.254 255.255.255.0
Router VLAN 4 192.168.40.254 255.255.255.0

Ports Tagging (802.1q):

Switch Port List of VLAN
ESM0 INT1 3
ESM0 INT2 4
ESM0 INT10 2
ESM0 Lag0 1234
EXTS0 1/2 1234
EXTS0 Lag0 1234

6.1.2 ESM0 Switch Configuration

Create Link Aggregation:

6-2 )    ! 

+.
 
 
+.
 

6
766

 9
 
<
; 

 9
 
<
; 

 9/
 
<
; 

 95
 
<
; 


Create Different VLANs:

6
76
<   NGO
7 9 9 9/ 95  :7$  9 95   *   =>0? 
 

< /  N  =
O
7 9 9 9/ 95  :7$  9 95   *   =>0? /
 

< 5  N  )O
7 9 9 9/ 95  :7$  9 95   *   =>0? 5
 


Ports Tagging and Rapid Spanning Tree:

)    ! 

+.
  6-3
Chapter 6 
+.
 

6
7
 9
  
77*  
 

 9
  
77*  
 

 9/
  
77*  
 

 95
  
77*  
 

 
77*  
< / :  7 
       *   =>0? 7 /
 

 
77*  
< 5 :  7 
       *   =>0? 7 5
 

 
77*  
< :  7 
       *   =>0? 7 
 


ESM0 IP Interface Parameters:

6
76/67 
 HA 
; 
< 


*
 HA 5
< 


<

6.1.3 ESM0 Configuration Dump

6-4 )    ! 

+.
 
 
+.
 

,,,,,,,,,,,,,
676/6
,,,,,,,,,,,,,
(2 7$
0& # 
(7
 7$
$ HA   HA  J < J #
)7# * 7$ 


/$ HA 5J < J #
3# (2 7* $ 1?J    
3# 
 *;$
3# (2  $
0    < 7* 1?
3# *; 7 $


,,,,,,,,,,,,,
6766<
,,,,,,,,,,,,,
=>0? ? &# M#  2
 )7# =>0?   (?,(?H (?,(?5 4,45
 G   4,45 (?
/   =
   (? 4,45
5   )   (? 4,45
5 H G =>0?   (?,GF

,,,,,,,,,,,,,
6766
6#
,,,,,,,,,,,,,
 
 ; ; 
 

 #;

,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
4 
<    /A  H
4 
<    /A  H
4/ 
<    /A  H
45 
<    /A  H

6.1.4 EXTS0 External Switch Configuration

The External switch must be configured according to the data above. For more information,
see the manufacturer documentation.

6.2 Multi Enterprise Configuration

This configuration example applies to:
- Multi-tenancy
- Ethernet redundancy network
- Multiple VLANs with a dedicated management VLAN
___change-begin___
)    ! 
+.
  6-5
Chapter 6 
+.
 

___change-end___
6.2.1 Configuration Information
Active Equipment IP Addressing:
&G $ HA 
&G $ HA 
9& $ HA /
9& $ HA 5
F* $ HA 5
G; $ 

VLANs (802.1q):
ID Name Subnet IP/mask
1 Default
2 Management 192.168.20.0/24
3 Entreprise 1 Voice 192.168.30.0/24
4 Entreprise 1 Data 192.168.40.0/24

6-6 )    ! 

+.
 
 
+.
 

5 Entreprise 2 Voice 192.168.50.0/24

6 Entreprise 2 Data 192.168.60.0/24

Link Aggregation (lacp 802.3ad):

ID Src Dst Key Port src Port dst
Lag0 ESM0 ExtS0 5 EXT1 EXT2 1/3 1/5
Lag1 ESM0 ExtS1 6 EXT3 EXT4 1/3 1/5
Lag2 ESM1 ExtS0 7 EXT1 EXT2 1/7 1/9
Lag3 ESM1 ExtS1 8 EXT3 EXT4 1/7 1/9

Server Interface Addressing:

Server eth0 - eth1 (bonding 0) mask
4760 192.168.20.1 255.255.255.0
E1-voix 192.168.30.1 255.255.255.0
E1-data 192.168.40.1 255.255.255.0
E2-voix 192.168.50.1 255.255.255.0
E2-data 192.168.60.1 255.255.255.0
Router VLAN 2 192.168.20.254 255.255.255.0
Router VLAN 3 192.168.30.254 255.255.255.0
Router VLAN 4 192.168.40.254 255.255.255.0
Router VLAN 5 192.168.50.254 255.255.255.0
Router VLAN 6 192.168.60.254 255.255.255.0

Ports Tagging (802.1q):

Switch port List of VLAN
ESM0 INT1 3
ESM0 INT2 4
ESM0 INT3 5
ESM0 INT4 6
ESM0 INT10 2
ESM0 Lag0 123456
ESM0 Lag1 123456
ESM1 INT1 3
ESM1 INT2 4
ESM1 INT3 5
ESM1 INT4 6
ESM1 INT10 2
ESM1 Lag2 123456
ESM1 Lag3 123456

)    ! 

+.
  6-7
Chapter 6 
+.
 

EXTS0 1/2 123456

EXTS0 Lag0 123456
EXTS0 Lag2 123456
EXTS1 1/2 123456
EXTS1 Lag1 123456
EXTS1 Lag3 123456

Spanning Tree:
Link Cost
Lag0 100
Lag1 200
Lag2 300
Lag3 400

Routing:
0# P
=>0?    
=>0?    
=>0? /  =>0? 5
=>0?   =>0? A
) 

6.2.2 ESM0 Configuration

Create Link Aggregation:
6
766

 9
 
<
; 

 9
 
<
; 

 9/
 
<
; A

 95
 
<
; A


Create Different VLAN:

6-8 )    ! 

+.
 
 
+.
 

6
76
< 
 NGO
7 9 9 9/ 95 
 

< /
 N  =
O
7 9 9 9/ 95 
 

< 5
 N  )O
7 9 9 9/ 95 
 

< 
 N  =
O
7 9 9 9/ 95 /
 

< A
 N  )O
7 9 9 9/ 95 5
 


Ports Tagging and Rapid Spanning Tree:

)    ! 

+.
  6-9
Chapter 6 
+.
 

6
7
 9
  
77*  
 

 9
  
77*  
 

 9/
  
77*  
 

 95
  
77*  
 

 
77*
 
< /
 

 
77*
 
< 5
 

 /
77*
 
< 
 

 5
77*
 
< A
 

 
77*
 
< 
 


Spanning Tree:

6-10 )    ! 

+.
 
 
+.
 

6
766 

 9

 
 9

 
 9/

 
 95

 


ESM0 IP Interface Parameters:

6
76/67 
 HA 
; 
< 


*
 HA 5
< 


<

6.2.3 ESM0 Dump

,,,,,,,,,,,,
676/6
,,,,,,,,,,,,
(2 7$
0& # 
(7
 7$
$ HA   HA  J < J #
)7# * 7$ 


/$ HA 5J < J #
3# (2 7* $ 1?J    
3# 
 *;$
3# (2  $
0    < 7* 1?
3# *; 7 $


,,,,,,,,,,,,,,
6766<
,,,,,,,,,,,,,,
=>0? ? &# M#  2
,,,, ,,,,,,,,,,,,,,,,,, ,,,,,, ,,,,, ,,,,,,,,,,,,,,,,
 )7# =>0?   (?,(?H (?,(?5 4,45
 G   4,45 (?
/   =
   (? 4,45
5   )   (? 4,45
   =
   (?/ 4,45
A   )   (?5 4,45
5 H G =>0?   (?,GF

)    ! 

+.
  6-11
Chapter 6 
+.
 

,,,,,,,,,,,,,,,,,,,
6766
6#
,,,,,,,,,,,,,,,,,,,
 
 ; ; 
 

 #;

,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
4 
<    /A  H
4 
<    /A  H
4/ 
< A A  /A H 
45 
< A A  /A H 

,,,,,,,,,,,,,
6766
,,,,,,,,,,,,,
&2 #; 7 $  
F  7@#; $ J  5
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
&  F# $ 1
3# '$ 2 ,3 2 K G90 E*) 0
 $$7H$7$
$ 5 4    /
2$ 2 K G90 E*) 0
/A    /
2 2 3 & ) B ) 2
,,,,, ,,,,,,,, ,,,, ,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,
(? E1'I0')(?F +
(? E1'I0')(?F +
(?/ E1'I0')(?F +
(?5 E1'I0')(?F +
(? )(&0B>) +
(?A )(&0B>) +
(? )(&0B>) +
(? E1'I0')(?F +
(?H E1'I0')(?F +
(? E1'I0')(?F +
(? )(&0B>) +
(? )(&0B>) +
(?/ )(&0B>) +
(?5 )(&0B>) +
4   E1'I0')(?F  , $ $H$ $7$ HAH
4   E1'I0')(?F  , $ $H$ $7$ HAH
4/   E1'I0')(?F  , $$7H$7/$
$ /
45   E1'I0')(?F  , $$7H$7/$
$ /

Note: * = STP turned off for this port.

6.2.4 ESM1 Configuration

Create Link Aggregation:

6-12 )    ! 

+.
 
 
+.
 

6
766

 9
 
<
; 

 9
 
<
; 

 9/
 
<
; 

 95
 
<
; 


Create Different VLAN:

6
76
< 
 NGO
7 9 9 9/ 95 
 

< /
 N  =
O
7 9 9 9/ 95 
 

< 5
 N  )O
7 9 9 9/ 95 
 

< 
 N  =
O
7 9 9 9/ 95 /
 

< A
 N  )O
7 9 9 9/ 95 5
 


Ports Tagging and Rapid Spanning Tree:

)    ! 

+.
  6-13
Chapter 6 
+.
 

6
7
 9
  
77*  
 

 9
  
77*  
 

 9/
  
77*  
 

 95
  
77*  
 

 (?
77*  
< /
 

 (?
77*  
< 5
 

 (?/
77*  
< 
 

 (?5
77*  
< A
 

 
77*
 
< 
 


Spanning Tree:

6-14 )    ! 

+.
 
 
+.
 

6
766 

 9

 /
 9

 /
 9/

 5
 95

 5


ESM1 IP Interface Parameters:

6
76/67 
 HA 
; 
< 


*
 HA 5
< 


<

6.2.5 ESM1 Dump

,,,,,,,,,,,,
676/6
,,,,,,,,,,,,
(2 7$
0& # 
(7
 7$
$ HA   HA  J < J #
)7# * 7$ 


/$ HA 5J < J #
3# (2 7* $ 1?J    
3# 
 *;$
3# (2  $
0    < 7* 1?
3# *; 7 $

3# #  $

)    ! 

+.
  6-15
Chapter 6 
+.
 

,,,,,,,,,,,,,,
6766<
,,,,,,,,,,,,,,
=>0? ? &# M#  2
,,,, ,,,,,,,,,,,,,,,,,,, ,,,,,, ,,,,, ,,,,,,,,,,,,,,,,
 )7# =>0?   (?,(?H (?,(?5 4,45
 G   4,45 (?
5   =
   (? 4,45
   )   (? 4,45
A   =
   (?/ 4,45
   )   (?5 4,45
5 H G =>0?   (?,GF

,,,,,,,,,,,,,,,,,,,
6766
6#
,,,,,,,,,,,,,,,,,,,
 
 ; ; 
 

 #;

,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
4 
<    /A  H
4 
<    /A  H
4/ 
<    /A H 
45 
<    /A H 

,,,,,,,,,,,,,
6766
,,,,,,,,,,,,,
&2 #; 7 $  
F  7@#; $ J  5
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
&  F# $ 1
3# '$ 2 ,3 2 K G90 E*) 0
 $$7H$7$
$ #    /
2$ 2 K G90 E*) 0
/A    /
2 2 3 & ) B ) 2
,,,,, ,,,,,,,, ,,,, ,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,
(? E1'I0')(?F +
(? E1'I0')(?F +
(?/ E1'I0')(?F +
(?5 E1'I0')(?F +
(? )(&0B>) +
(?A )(&0B>) +
(? )(&0B>) +
(? E1'I0')(?F +
(?H E1'I0')(?F +
(? E1'I0')(?F +
(? )(&0B>) +
(? )(&0B>) +
(?/ )(&0B>) +
(?5 )(&0B>) +
4  / E1'I0')(?F  , $$7H$7$
$ /
4  / E1'I0')(?F  , $$7H$7$
$ /
4/  5 E1'I0')(?F  , $$7H$7$
$ /
45  5 E1'I0')(?F  , $$7H$7$
$ /

Note: * = STP turned off for this port.

6-16 )    ! 

+.
 
 
+.
 

6.2.6 External Switch Configuration

The External switch must be configured according to the data above. For more information,
see the manufacturer documentation.

6.2.7 Blade Ethernet Interface Configuration

The Ethernet interface must be configured according to either Ethernet load balancing or
redundancy. . The blade operating system allows to configure Ethernet interfaces.
For more information, see the operating system documentation.
For more information on loading an OmniPCX Enterpriseon a blade, see: module netadmin -
Overview .

)    ! 

+.
  6-17
Chapter 6 
+.
 

6-18 )    ! 

+.