No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address:Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
This document describes the CX320 switch module (CX320) in terms of its features,
installation, removal, and configuration.
Intended Audience
About This Document
About This Document
This document is intended for:
lTechnical support engineers
lInstallation and commissioning engineers
lField maintenance engineers
lSystem maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates an imminently hazardous situation which, if
not avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if
not avoided, could result in death or serious injury.
Indicates a potentially hazardous situation which, if
not avoided, may result in minor or moderate injury.
Indicates a potentially hazardous situation which, if
not avoided, could result in equipment damage, data
loss, performance deterioration, or unanticipated
results.
NOTICE is used to address practices not related to
personal injury.
2.7 Internal Networking of a Chassis................................................................................................................................. 29
2.8 Software and Hardware Compatibility......................................................................................................................... 31
3 Installing and Removing the CX320........................................................................................ 35
3.1 Installing the CX320.....................................................................................................................................................35
3.2 Removing the CX320................................................................................................................................................... 43
4 Configuring the CX320............................................................................................................... 52
4.3 Setting an IP Address for the Management Network Port........................................................................................... 56
4.4 Logging In to the CLI of Each Switching Plane.......................................................................................................... 58
4.5 Checking the Switching Plane......................................................................................................................................62
4.6 Changing Initial User Passwords..................................................................................................................................64
4.7 Adding a User...............................................................................................................................................................69
4.8 Configuring Switching Service Data............................................................................................................................71
4.9 Backing Up the Configuration File.............................................................................................................................. 75
5 Restoring the Configuration File..............................................................................................79
6 Common Operations...................................................................................................................82
6.1 Logging In to or a Switch Module over MM910 SOL.................................................................................................82
6.2 Logging In to the MM910 CLI Over a Network Port by Using PuTTY......................................................................85
6.3 Logging In to a Device Over a Serial Port by Using PuTTY.......................................................................................87
6.4 Powering On or Off a Switching Plane........................................................................................................................ 90
6.5 Logging In to the MM910 WebUI................................................................................................................................ 91
6.6 Transferring Files Using WinSCP................................................................................................................................ 97
6.7 Using the MM910 WebUI to Collect converged switching plane Information............................................................99
6.8 Configuring an FTP Server...........................................................................................................................................99
6.9 Using the CLI to Collect converged switching plane Information.............................................................................101
A Appendix....................................................................................................................................106
A.1 Logging In to the CX320 BIOS.................................................................................................................................106
lUse the recommended power cables at all times.
lAlways use the power cables delivered with the devices.
lWear ESD clothing and gloves before handling a device. This prevents electrostatic
lWhen moving a device, make sure to hold the handles of the device (or the bottom of the
lExercise caution to prevent damage to the device when using tools during installation or
lConnect the power cables from the active power supply to one power distribution unit
lEnsure that a device is properly grounded before powering it on.
1 Safety Instructions
damage.
devices). Do not hold the handles of the installed modules, such as power modules, fan
modules, hard disks, or boards.
maintenance.
(PDU), and the cables from the backup power supply to another PDU.
Transportation Precautions
Exercise caution when transporting equipment.
lThe logistics company engaged to transport the equipment must be reliable and comply
with international standards for transporting electronics.
lEnsure that the equipment being transported is always upright. Take necessary
precautions to prevent collisions, corrosion, package damage, damp conditions and
pollution.
lTransport the equipment in its original packaging.
lPackage heavy, bulky parts (such as chassis and blades) and fragile parts (such as PCIe
GPUs and SSDs) separately.
NOTE
Use the Intelligent Computing Compatibility Checker for details about parts supported by a server.
lEnsure that all devices are powered off before transportation.
lDo not transport hazardous materials.
This topic describes the functions, protocols, and ports of the CX320 switch module (CX320).
2.2 Appearance
This section describes the appearances and panels of the CX320, MX517, and MX527, as
well as the installation positions of the CX320 in the chassis.
2.3 Ports
This topic describes the features, numbering rules, names, types, and quantity of the CX320
ports.
2.4 Indicators
This topic describes the names, meanings, colors, descriptions and working status of the
indicators on the CX320.
2.5 Physical Structure
This topic describes the components, mainboard layout, and connectors of the CX320.
2.6 Logical Structure
This topic describes the logical structure of the CX320.
2.7 Internal Networking of a Chassis
This topic describes connection relationships between the CX320 and mezzanine cards on
compute nodes.
2.8 Software and Hardware Compatibility
This topic describes the software and hardware supported by the CX320.
2.9 Technical Specifications
This topic describes the physical, environmental, power, and network switching specifications
of the CX320.
2.1 Functions
This topic describes the functions, protocols, and ports of the CX320 switch module (CX320).
The CX320 is a switching control unit that provides data switching functionality for compute
node slots in the system and centrally provides service and management ports to connect to
external devices.
The CX320 is installed in a rear slot of an E9000 chassis and are connected to compute nodes,
storage nodes, and management modules through the E9000 midplane. It exchanges data and
control packets in the E9000 chassis and provides high-speed data transmission.
Table 2-1 describes the functions of the CX320 converged switching plane.
Table 2-1 Ethernet switching plane function description
Function
Basic featuresEthernet
Description
l Full-duplex and autonegotiation working modes
l GE, 10GE, and 40GE (supported by Ethernet ports
on the panel)
NOTE
l 10GE optical ports support multi-mode and single-
mode optical modules (GE or 10GE).
l 10GE optical ports support GE or 10GE electrical
modules.
l 40GE optical ports on the panel support multi-mode
optical cables, single-mode optical cables, and passive
cables. Each 40GE optical port can be divided into
four 10GE optical ports.
l 10GE optical ports on the panel support multi-mode
optical cables, single-mode optical cables, and passive
cables, and can be merged into 40GE optical ports.
l MX517 PIC card with 10GE/8G FC unified ports.
NOTE
l 10GE optical ports support multi-mode and single-
mode optical modules (GE or 10GE).
l 10GE optical ports support SFP electrical modules.
l 10GE optical ports on the panel support multi-mode
optical cables, single-mode optical cables, and passive
cables.
l Port traffic control
l Jumbo frames
l Link aggregation
l Load balancing among links of a trunk
l Port isolation and forwarding restriction on ports
l 40G port splitting
l Protocol-based packet statistics on a port
l Broadcast storm suppression
l M-LAG
FC
l MX517 PIC card with 10GE/8G FC unified ports.
l MX527 PIC card with 16G FC ports
l Multiple access modes: access, trunk, and hybrid
l Port-based, MAC address-based, and IP subnet-
based VLAN assignment
l VLAN aggregation
l MUX VLAN
l Transparent transmission of protocol packets in a
VLAN
l Batch configuration of VLANs
QinQ
l Basic QinQ
l Flexible QinQ
VLAN
Mapping
l 1 to 1 VLAN mapping
l 2 to 1 VLAN mapping
l 2 to 2 VLAN mapping
GVRPGARP VLAN Registration Protocol (GVRP)
MAC
l Sticky MAC
l Automatic MAC address learning and aging
l Static, dynamic, and blackhole MAC address entries
l Filtering based on source MAC addresses
l Port-based MAC learning limiting
Ethernet loop
protection
Link Layer
LLDP
Discovery
Protocol
(LLDP)
Multiple
Spanning Tree
l Spanning Tree Protocol (STP)
l Rapid Spanning Tree Protocol (RSTP)
Protocol
(MSTP)
l MSTP
l VLAN-based Spanning Tree (VBST), with the
maximum number of protected VLANs of 128 and
maximum number of PVs of 16000
l Bridge protocol data unit (BPDU), root, and loop
protection
l Partitioned STP and layer-2 protocol transparent
l DHCP packet filtering (with the Option 82 field)
l Prevention of control packet attacks
l Attack defense
– Defense against flood attacks without IP
payloads, attacks from IGMP null payload
packets, LAND attacks, Smurf attacks, and
attacks from packets with invalid TCP flag bits
– Defense against attacks from many fragments,
attacks from many packets with offsets, attacks
from repeated packet fragments, Tear Drop
attacks, Syndrop attacks, NewTear attacks, Bonk
attacks, Nesta attacks, Rose attacks, Fawx
attacks, Ping of Death attacks, and Jolt attacks
– Defense against TCP SYN flood attacks, UDP
flood attacks (including Fraggle attacks and UDP
diagnosis port attacks), and ICMP flood attacks
l Logs about attacking MAC addresses
l URPF
l 802.1x authentication
Network
management
l ICMP-based Ping and Tracert
l Simple Network Management Protocol Version
1/2c/3 (SNMPv1/v2c/v3)
l Standard Management Information Base (MIB)
l Remote Network Monitoring (RMON)
l NETCONF interfaces
l Network Quality Analysis (NQA)
2.2 Appearance
This section describes the appearances and panels of the CX320, MX517, and MX527, as
well as the installation positions of the CX320 in the chassis.
1Connection status indicator2Data transmission status
indicator
3PIC card handle416G FC port
An Equipment Serial Number (ESN) uniquely identifies a server. An ESN is required when
you apply for technical support from Huawei.
Figure 2-8 ESN example
Callout No.
Description
1ESN ID (two characters), which is 21 by default.
2Material identification code (eight characters), that is, processing code.
3Vendor code (two characters). The code 10 indicates Huawei, and other
values indicate outsourcing vendors.
4Year and month (two characters).
l The first character indicates the year, where:
– Digits 1 to 9 indicate 2001 to 2009, respectively.
– Letters A to H indicate 2010 to 2017, respectively.
– Letters J to N indicate 2018 to 2022, respectively.
– Letters P to Y indicate 2023 to 2032, respectively.
NOTE
The years from 2010 are represented by upper-case letters excluding I, O, and Z
because the three letters are similar to the digits 1, 0, and 2.
l The second character indicates the month, where:
– Digits 1 to 9 indicate January to September, respectively.
– Letters A to C indicate October to December, respectively.
5Serial number (six characters).
6RoHS compliance (one character). Y indicates environmental protection
This topic describes the features, numbering rules, names, types, and quantity of the CX320
ports.
The CX320 provides ports for users to operate and configure. The ports are used to send and
receive data.
The CX320 Ethernet ports are numbered in the Slot number/Subcard number/Port number
format.
lSlot number indicates the slot number of the current switch module. The value ranges
from 1 to 4, mapping to slot numbers 1E, 2X, 3X, and 4E.
lSubcard number indicates the number of a subcard with ports. The value ranges from 1
to 22. For details, see Table 2-2, Table 2-3, and Table 2-4.
lPort number indicates the serial number of the port on the subcard. For details, see Table
2-2, Table 2-3, and Table 2-4.
For example, if the CX320 is in slot 2X, the first optical Ethernet port on the upper right of
the panel is numbered 40GE 2/20/2, as shown in Figure 2-9.
used to connect to the
BMC or converged
switching plane. During
the BMC startup, the
serial port is used by the
BMC. In other cases, the
serial port is used by the
10GE converged
switching plane by
default, and can be
switched to the BMC
over SOL.
NOTE
On the CLI, the serial port
corresponds to the
following options:
l bmccom: serial port
connecting to the
BMC.
l fabriccom: serial port
connecting to the
converged switching
plane.
The baud rate is 115200
bit/s when the serial port
is connected to the BMC
or converged switching
plane.
10GE
optical
port
SFP+8171 to 8The panel provides eight
10GE optical ports to
connect to external
networks.
40GE
optical
port
QSFP+2201 to 2The panel provides two
40GE optical ports to
connect to external
networks or serve as
stacking ports.
PIC 1--21-A flexible card can be
installed in slot PIC 1 for
port expansion. The
expanded ports depend
on the flexible PIC card
type.
related to the PIC slot.
For example, if the PIC
card is in slot 1, the first
Ethernet port number is
10GE x/21/1, and the
first FC port number is
FC x/21/1 (x indicates
the switch module slot,
and 21 indicates PIC slot
1.) The MX517 ports are
Ethernet ports by
default. To convert them
to FC ports, see the portmode fc command in
CX320 Switch Module
Command Reference.
NOTE
You can run the
corresponding command
to query the operating type
of the optical module
installed on the MX517
card. For details, see
"display interface
transceiver" in the CX320
Switch Module V100R001
Command Reference. The
Transceiver Type
information in the
command output indicates
the operating type of the
optical module.
MX527
PIC card
SFP+16G FC
port
41 to 4PIC port numbers are
related to the PIC slot.
For example, if the PIC
card is in slot 1, the first
FC port number is FC x/
21/1 (x indicates the
switch module slot, and
21 indicates PIC slot 1.)
It is difficult to identify the
difference between blinking
frequencies of 4 Hz and 5 Hz. If
the indicator is blinking red
quickly, check whether the
device has been installed
properly and then check whether
a critical alarm has been
generated.
l Off: The port is not
properly connected.
l Steady green: The port is
properly connected.
and
and
Data
transmission
status indicator
for the 10GE
optical port
4Flexible PIC cardPIC cards are used to expand ports and are
hot-swappable. The PIC cards in the figure
are MX517 cards with 10GE/8G FC unified
ports.
NOTE
l You can run the corresponding command to
query the type of the installed PIC card. For
details, see "display device card" in the
CX320 Switch Module V100R001 Command
Reference.
l The MX517 and MX527 cards can be
installed in the same CX320 switch module.
5Midplane signal connectorExchanges data between the CX320 and
compute nodes.
6Midplane power connectorSupplies 12 V DC power.
2.6 Logical Structure
This topic describes the logical structure of the CX320.
The BMC module is a management module that provides power control, system monitoring,
and component upgrade functions. The CPU system module is the controlling core that
processes network protocol packets and enables configurations. The converged switching
module is the data processing core that forwards data between internal data processing
modules and external network devices. PIC cards are hot-swappable and used to expand the
port types and quantity.
Figure 2-12 Mapping between the CX320 and mezzanine cards on compute nodes
The following describes the mapping between the CX320 switch modules and mezzanine
cards, assuming that the CX320 switch modules are installed in slots 2X and 3X and connect
to Mezz 1.
Mapping Between Switch Modules and Mezzanine Card Ports
Mapping between CX320 switch modules and ports on the MZ510
The MZ510 provides two 10GE ports (ports 1 and 2), which connect to the 10GE switching
planes of the CX320 switch modules in slots 2X and 3X respectively, as shown in Figure
Figure 2-13 Mapping between CX320 switch modules and ports on the MZ510
Mapping between CX320 switch modules and ports on the MZ512
The MZ512 provides four 10GE ports (ports 1 to 4). Ports 1 and 3 connect to the converged
switching plane of the CX320 in slot 2X, and ports 2 and 4 connect to the converged
switching plane of the CX320 in slot 3X, as shown in Figure 2-14.
Figure 2-14 Mapping between CX320 switch modules and ports on the MZ512
2.8 Software and Hardware Compatibility
This topic describes the software and hardware supported by the CX320.
For details about the software and hardware supported by the CX320, use the Intelligent
Figure 3-3 Removing the switch module filler panel
2.Raise the two handles on the switch module filler panel completely, and pull the filler
panel horizontally out of the chassis. See (2) and (3) in Figure 3-3.
3.Store the switch module filler panel for future use.
Step 4 Install the CX320.
1.Raise the two ejector levers on the CX320 completely and push the CX320 horizontally
into the chassis as far as it will go. See (1) and step (2) in Figure 3-4.
2.Lower the PIC card handle. See (3) and (4) in Figure 3-22.
An ESD bag can hold only one PIC card.
3.Place the removed PCIe card in an ESD bag.
NOTE
If you do not install a new PIC card immediately, install a PIC card filler panel.
Step 8 Install a PIC card filler panel.
1.Raise the handle on the PIC card filler panel completely and push the PIC card filler
panel horizontally into the PIC slot. See (1), (2), and (3) in Figure 3-23.
2.Completely lower the handle on the PIC card filler panel until the filler panel is installed
properly. See (4) in Figure 3-23.
Step 9 Install a switch module filler panel.
1.Raise the two handles on the switch module filler panel and push the filler panel
horizontally into the chassis as far as it will go. See (1) in Figure 3-24.
This topic describes the initial configuration process for the installed CX320 on a local PC to
implement the switching function.
4.1 Configuration Overview
4.2 Default Information
4.3 Setting an IP Address for the Management Network Port
Set the IP address for the converged switching plane management network port on the
CX320.
4.4 Logging In to the CLI of Each Switching Plane
4.5 Checking the Switching Plane
4.6 Changing Initial User Passwords
4.7 Adding a User
4.8 Configuring Switching Service Data
Configure the CX320 feature data after the converged switching plane meets the basic
configuration conditions.
4.9 Backing Up the Configuration File
This topic describes how to back up the configuration file. If configuration errors occur or the
CX320 is faulty, you can use the backup configuration file to restore configuration data.
Set the IP address for the management network port of the
converged switching plane.
You can log in to the CLI of the switching plane from a PC by
using the IP address of the management network port.
You can log in to the converged switching plane CLI over
Secure Shell (SSH), Serial Over LAN (SOL), or a serial port.
Page 60
CX320 Switch Module
User Guide
4 Configuring the CX320
StepDescription
Check the switching
plane.
Changing the Initial User
Passwords
Add a user.Add a user in the converged switching plane of the CX320.
Configure switch module
data.
Back up configuration
files.
Check the following items in the converged switching plane of
the CX320:
l Query versions and check whether the versions are the
required ones.
l Query alarms and check whether an alarm is generated.
Change the initial user passwords after the first login to the
CX320 to ensure the security of system operating and
maintenance.
This topic describes how to change the initial user passwords
of the BMC, converged switching plane, and BIOS.
You can log in to the switching plane CLI for routine
maintenance as the new user.
This topic describes the switching service data supported by
the converged switching plane of the CX320.
Back up the configuration file of the converged switching
plane for the CX320. If configuration errors occur or the
CX320 is faulty, you can use the backup configuration file to
restore configuration data.
Related Documents
The following lists the documents related to the converged switching plane of the CX320.
lTo query the converged switching plane commands, see CX320 Switch Module
V100R001 Command Reference.
lTo configure the converged switching plane feature data, see CX320 Switch Module
V100R001 Configuration Guide.
lTo handle the converged switching plane alarms, see E9000 Server V100R001 Alarm
Handling.
lTo handle converged switching plane faults or replace the CX320, see Huawei Servers
Switch modules have a virtual serial port COM1. The virtual serial port is used by the built-in software
system in a switch module to manage the switch module. Note the following about the virtual serial port:
l Users cannot log in to the virtual serial port.
l The default password is Huawei#123.
l Do not set or change the virtual serial port login password; otherwise, some switch module functions
fail.
l If the login password is changed, run the undo authentication-mode or undo set authentication
password command to delete the new login password.
4 Configuring the CX320
4.3 Setting an IP Address for the Management Network
Port
Set the IP address for the converged switching plane management network port on the
CX320.
The IP address of the management network port of the converged switching plane can be set
locally or on the MM910 as follows:
Prerequisites
lThe IP address of the converged switching plane management network port can be set on
the MM910 WebUI. For details, see the procedure section in this topic.
lOn the converged switching plane CLI, run the ip address command to set the IP
address of the converged switching plane management network port. For details, see the
CX320 Switch Module Command Reference.
lOn the MM910 CLI, run the swipcontrol command to set IP address of the converged
switching plane management network port. For details, see MM910 Management
Module V100R001 Command Reference.
Data
Table 4-3 Required data
Name
IP address, subnet mask, and
gateway of the converged
switching plane
management network port
DescriptionExample Value
You can log in to the
converged switching plane
CLI from a PC by using the
IP address of the
management network port.
– targetvalue: specifies the target network segment IP address of the switching plane.
– maskvalue: specifies the subnet mask of the switching plane.
– gatewayvalue: specifies the gateway IP address of the switching plane.
----End
4 Configuring the CX320
4.4 Logging In to the CLI of Each Switching Plane
Log in to the converged switching plane CLI of the CX320 over Secure Shell (SSH), Serial
Over LAN (SOL), or a serial port.
Log in to the CLI of the converged switching plane for the CX320 by using one of the
following methods:
lOver SSH: Remotely log in to the CLI of the converged switching plane over an
Ethernet.
lOver SOL: Log in to the serial port of the converged switching plane through the
MM910 SOL screen.
lOver a serial port: Connect a serial cable to the COM serial port of the CX320 and log in
to the CLI without using an IP address.
Prerequisites
Procedure
Data
Table 4-5 Default Data
Name
converged
switching plane
Tools
If you want to log in to a server CLI over a serial port, prepare the following hardware:
lPC with an RS232 serial port
lDB9-RJ45 cable
Default DataLogin Method
l User name: root
l Password: Huawei12#$
l No user name
l Password: Huawei12#$
SSH
l Serial port
l SOL
lLog in to the CLI of a switching plane over SSH.
Step 1 Connect the local PC to the MM910.
lConnect the network port of the local PC to the MGMT port of the active or standby
If the MGMT port on the active MM910 is already connected with a network cable, do
not remove the network cable from the MGMT port. Otherwise, an active/standby
switchover of the MM910s will be triggered, which may cause network interruption.
NOTE
The MM910 management port is provided by either of the following modes:
– An Ethernet port on the switch module in slot 2X or 3X.
However, if a CX910/CX911/CX912/CX913 is in slot 2X or 3X, only a GE port can be used;
if a CX920 is in slot 2X or 3X, only a 10GE port can be used. The CX910/CX911/CX912/
CX913 are not recommended for providing the management port of the management module.
– MGMT port on the MM910 panel
– For the MM910 (U54)2.25 or earlier, the management port is provided by the switch module
by default. For the MM910 (U54)2.26 or later, the management port is provided by the
MM910 by default. For details about how to query the MM910 version, see MM910
Management Module V100R001 User Guide.
– You can run the outportmode command to change the mode in which the MM910
management port is provided. If the switch module in slot 2X or 3X is used to provide the
management port, do not connect the MM910 MGMT port and the switch module ports to the
same network. Otherwise, a network storm will occur and the network will be interrupted. For
details, see MM910 Management Module V100R001 Command Reference.
lConnect the network port of the local PC to the MGMT or STACK port of the active
MM910.
– If the MGMT port of the active MM910 is available, use this port. Figure 4-3
Figure 4-3 Connection between the local PC and the active MM910 (in slot MM2
in this example)
– If the MGMT port of the active MM910 is unavailable, connect the PC to the
STACK port of the active MM910. If the STACK port is used to stack the MGMT
port in another chassis, connect the PC to an idle STACK port on an active MM910
in a chassis cascaded with the E9000 chassis. Figure 4-4 shows the connection.
If the MGMT port on the active MM910 is already connected with a network cable,
do not remove the network cable from the MGMT port. Otherwise, an active/
standby switchover of the MM910s will be triggered, which may cause network
interruption.
Step 2 Use an SSH connection tool to log in to the MM910 CLI by using the floating IP address of
Step 3 Log in to the CLI of a switching plane over MM910 SOL.
4 Configuring the CX320
l If the MGMT port on the active MM910 is already connected with a network cable, do
not remove the network cable from the MGMT port. Otherwise, an active/standby
switchover of the MM910s will be triggered, which may cause network interruption.
l If you want to connect your local PC directly to the MM910 using a network cable but the
MGMT port on the active MM910 is already connected with a network cable, connect the
network cable from the local PC to the STACK port of the active MM910 in the chassis. If
the STACK port on the active MM910 is also used, connect the network cable to an idle
STACK port on an active MM910 in a chassis cascaded with the E9000 chassis.
the MM910s.
This topic describes how to use PuTTY to log in over SSH. For details, see 6.2 Logging In to
the MM910 CLI Over a Network Port by Using PuTTY.
For details, see 6.1 Logging In to or a Switch Module over MM910 SOL.
----End
lLog in to the CLI of a switching plane over a serial port.
Step 1 Use a DB9-RJ45 cable to connect the RS232 serial port of the PC to the SYS serial port on
the CX320 panel.
Step 2 Use a serial port communication tool to log in to the CLI of a switching plane.
Set the key communication parameters as follows:
lSerial line to connect to: COMn
lSpeed (baud): 115200
lData bits: 8
lStop bits: 1
lParity: None
lFlow control: None
NOTE
n indicates the serial port number and is an integer.
In this document, PuTTY is used as an example for login over a serial port. For details, see
6.3 Logging In to a Device Over a Serial Port by Using PuTTY.
----End
4.5 Checking the Switching Plane
Check the converged switching plane operating status of the CX320.
lCritical: critical alarm
lMajor: major alarm
lMinor: minor alarm
lWarning: warning alarm
lSequence: alarm sequence
lAlarmId: alarm ID
lSeverity: alarm severity
lDate Time: date and time at which an alarm is generated
lDescription: alarm description
If no information is displayed, no alarm is generated.
Step 6 Handle the alarm. For details, see the E9000 Server V100R001 Alarm Handling.
----End
4.6 Changing Initial User Passwords
Change all the initial user passwords in the CX320, including changing the initial user
passwords of the BMC, converged switching plane, and BIOS after the first login to the
CX320 to enhance system O&M security..
NOTE
l The password complexity check is enabled by default.
l Use passwords that meet complexity requirements.
l For security purposes, change the initial password upon the first login, and then change the password
periodically.
4 Configuring the CX320
Prerequisites
The BIOS initializes hardware, such as serial ports or dual in-line memory modules
(DIMMs), reads the kernel image from the flash memory to the random access memory
(RAM), and starts the operating system (OS).
Conditions
lYou have logged in to the converged switching plane command-line interface (CLI).
lYou have logged in to the BMC CLI.
Data
Table 4-6 lists the default data required for the login.
Table 4-6 Default data
Name
converged
switching plane
Default DataDescription
l User name: root
l Password: Huawei12#$
A user who logs in to the
converged switching plane over
Secure Shell (SSH) and has all
rights of the converged switching
plane.
l No user name
l Password: Huawei12#$
A user who logs in to the
converged switching plane over a
serial port and has all rights of the
converged switching plane.
BIOS
l No user name
l Password: Huawei12#$
An anonymous BIOS user, who
has no user name. Enter only the
password to enter the BIOS.
Step 1 On the CLI of the converged switching plane, run the following command to go to the system
Step 2 Go to the user serial port view.
Step 3 Open the user interface (UI) for changing the password.
BMC
l User name: root
l Password: Huawei12#$
Default BMC user, who has all
rights of the BMC.
lChange the initial password for logging in to the GE switching plane over a serial port.
view:
<HUAWEI> system-view
The command output is as follows:
Enter system view, return user view with return command.
[~HUAWEI] user-interface console 0
[~HUAWEI-ui-console0] set authentication password
The command output is as follows:
Please configure the login password (8-16)
Enter Password:
Step 4 Enter a new password.
The password is case-sensitive and must meet the following requirements:
lContain at least two types of the following characters:
– Uppercase letters A to Z
– Lowercase letters a to z
– Digits 0 to 9
– At least one of the following special character: .`~!@#$%^&*()-_=+\|[{}];:'",<.>/
lCannot be the same as the user name or the user name in reverse order.
The following information is displayed:
Confirm Password:
NOTE
The entered password is not displayed on the terminal screen.
Step 5 Enter the new password again. The following information is displayed:
Info: The password of ui-console0 will be changed, please verify the old password.
Please enter old password:
Step 6 Enter the old password. The following information is displayed:
Warning: The current configuration will be written to the device. Continue? [Y/N]:
Enter Y to save the configuration. The following information is displayed:
Now saving the current configuration to the slot 1 .
Info: Save the configuration successfully.
begin synchronize configuration to SMM ...
slot 1: upload configuration to SMM successfully.
<HUAWEI>
----End
lChange the initial password for logging in to the converged switching plane over SSH.
Step 1 On the CLI of the converged switching plane, run the following command to go to the page
for changing a password:
<HUAWEI> local-user change-password
The command output is as follows:
Please enter old password:
Step 2 Enter the old password.
The following information is displayed:
Please enter new password:
Step 3 Enter a new password.
The password is case-sensitive and must meet the following requirements:
lContain at least two types of the following characters:
– Uppercase letters A to Z
– Lowercase letters a to z
– Digits 0 to 9
– At least one of the following special characters: .`~!@#$%^&*()-_=+\|[{}];:'",<.>/
lCannot be the same as the user name or the user name in reverse order.
The following information is displayed:
Please confirm new password:
Step 4 Enter the new password again.
If the following information is displayed, the password is successfully changed:
Warning: The current configuration will be written to the device. Continue? [Y/N]:
Enter Y to save the configuration. The following information is displayed:
Now saving the current configuration to the slot 1 .
Info: Save the configuration successfully.
begin synchronize configuration to SMM ...
slot 1: upload configuration to SMM successfully.
<HUAWEI>
----End
lChange the initial passwords of BIOS.
l If the software version of the switching plane is earlier than 6.30, log in to the switching
plane CLI through the serial port and then access the BIOS. There is no other way to
access the BIOS. If the software version of the switching plane is 6.30 or later, log in to
the switching plane CLI over SOL or serial port and then access the BIOS.
l For the switching plane versions from 6.30 to 6.56 (excluding 6.56), if you access the
switching plane CLI over SOL and then the BIOS, the operations such as changing the
password and system upgrade through disk formatting cannot be performed on the BIOS.
These operations are supported on the BIOS from switching plane version 6.56.
Step 1 Run the following command on the CLI of the converged switching plane to restart the GE
switching plane:
<HUAWEI> reboot
The command output is as follows:
Warning: Current configuration will be saved to the next startup savedconfiguration file! Continue? [Y/N]:
Enter Y to save the configuration. The command output is as follows:
Now saving the current configuration.
Save the configuration successfully.
begin synchronize configuration to SMM ...
slot 4: configuration is the same with SMM, needn't sync to SMM.
System will reboot! Continue? [Y/N]:
Enter Y to restart the converged switching plane.
Step 2 Press Ctrl+B when the system displays Press CTRL+B to enter BIOS menu.
lCannot be the same as the user name or the user name in reverse order.
Step 4 Enter the new password again.
If the following information is displayed, the initial user password is successfully changed.
Set user password successfully.
----End
4.7 Adding a User
Add a user in the converged switching plane of the CX320. The new user can log in to the
command-line interface (CLI) of the converged switching plane, and allocate operation
permissions to it based on actual requirements, to carry out routine maintenance.
Table 4-7 describes the command levels of the converged switching plane.
4 Configuring the CX320
Table 4-7 Command levels
Command
Level NameDescription
Level
0Visit levelNetwork diagnosis tool commands (such as ping and
tracert) and external device access commands
1Monitoring
level
2Configuration
level
System maintenance commands, such as display.
NOTE
Not all display commands are on the monitoring level. For
details about the command levels, see the CX320 Switch
Module V100R001 Command Reference.
Service configuration commands, including router
commands and the commands at different network
layers. The commands are used to provide direct
network services to users.
3Management
level
Commands of the management level are used for
basic system running to support services, for
example, file system commands, FTP commands,
Trivial File Transfer Protocol (TFTP) commands,
commands for switching configuration files,
commands for managing users, commands for setting
command levels, commands for setting internal
system parameters, and debugging commands for
diagnosing service faults.
Configure the CX320 feature data after the converged switching plane meets the basic
configuration conditions.
Feature configuration for the converged switching plane is as follows. For details, see CX320
Switch Module V100R001C10 Configuration Guide.
Table 4-9 List of configurable features
Configuration Type
Basic Configuration
Virtualization
Configuration
Configuration Item
l ZTP Configuration
l Logging In to the System for the First Time
l Configuring a User Interface
l Configuring User Login
l File Management
l Configuring System Startup
l Centralized Management for Configuration Files
l BIOS Menu
l Displaying the Device Status
l Hardware Management
l Information Center Configuration
l NTP Configuration
l Fault Management Configuration
l Maintenance Assistant Configuration
l OPS Configuration
l Basic Configuration for Interfaces
l Ethernet Interface Configuration
l Logical Interface Configuration
l MAC Address Table Configuration
l Link Aggregation Configuration
l M-LAG Configuration
l VLAN Configuration
l QinQ Configuration
l VLAN Mapping Configuration
l GVRP Configuration
l STP/RSTP Configuration
l MSTP Configuration
l VBST Configuration
l ERPS (G.8032) Configuration
l Loopback Detection Configuration
l Layer 2 Protocol Transparent Transmission Configuration
IP Service
l IP Address Configuration
l ARP Configuration
l DHCP Configuration
l DNS Configuration
l UDP Helper Configuration
l IP Performance Configuration
l Basic IPv6 Configuration
l DHCPv6 Configuration
l IPv6 DNS configuration
l IPv6 Transition Technology Configuration
l Static Route Configuration
l RIP Configuration
l RIPng Configuration
l OSPF Configuration
l OSPFv3 Configuration
l IPv4 IS-IS Configuration
l IPv6 IS-IS Configuration
l BGP Configuration
l Routing Policy Configuration
l IP Routing Table Management
l PBR Configuration
l IGMP Configuration
l MLD Configuration
l PIM (IPv4) Configuration
l IPv6 PIM Configuration
l MSDP Configuration
l IPv4 Multicast Route Management Configuration
l IPv6 Multicast Route Management Configuration
l IGMP Snooping Configuration
l Static Multicast MAC Address Configuration
l Multicast VLAN Replication Configuration
l Multicast Network Management
MPLS
l MPLS LDP Configuration
l MPLS QoS Configuration
VPN
l GRE Configuration Guide
l MCE Configuration
l IPv6 MCE Configuration
DCN and Server
Management
l TRILL Configuration
l VXLAN Configuration
l FC and FCoE Configuration
l Virtual Perception
l NLB Server Cluster Association
l BFD Configuration
l VRRP Configuration
l DLDP Configuration
l Smart Link and Monitor Link Configuration
l Smart Channel Configuration
l EFM Configuration
l AAA Configuration
l 802.1x Authentication Configuration
l ACL Configuration
l Local Attack Defense Configuration
l MFF Configuration
l Attack Defense Configuration
l Traffic Suppression and Storm Control Configuration
l ARP Security Configuration
l Port Security Configuration
l DHCP Snooping Configuration
l IPSG Configuration
l URPF Configuration
l SSL Configuration
l Keychain Configuration
l Separating the Management Port from the Service Plane
l Setting the System Root Key
QoS
l MQC Configuration
l Priority Mapping Configuration
l Traffic Policing, Traffic Shaping, and Interface-based Rate
Limiting
l Congestion Avoidance and Congestion Management
Configuration
l Packet Filtering Configuration
l Redirection Configuration
l Re-marking Configuration
l Traffic Statistics Configuration
l ACL-based Simplified Traffic Policy Configuration
l SNMP Configuration
l RMON Configuration
l NETCONF Configuration
l OpenFlow Agent Configuration
l LLDP Configuration
l NQA Configuration
l Mirroring Configuration
l Packet Capture Configuration
l NetStream Configuration
l sFlow Configuration
4.9 Backing Up the Configuration File
This topic describes how to back up the configuration file. If configuration errors occur or the
CX320 is faulty, you can use the backup configuration file to restore configuration data.
Back up the configuration file of the CX320 so that the configuration data can be restored if
faults occur.
Prerequisites
Procedure
Step 1 Log in to the converged switching plane command-line interface (CLI).
Step 2 Log in to the MM910 CLI.
Step 3 Configure the converged switching plane.
Step 4 Save the converged switching plane configuration file.
Software
WinSCP.exe (third-party free software)
1.Run the following command on the CLI of the converged switching plane to view the
configuration file required for the next startup of the converged switching plane:
<HUAWEI> display startup
The command output is as follows:
MainBoard:
Configured startup system software: flash:/xxx.cc
Startup system software: flash:/xxx.cc
Next startup system software: flash:/xxx.cc
Startup saved-configuration file: flash:/vrpcfg.zip
Next startup saved-configuration file: flash:/vrpcfg.zip
Startup paf file: default
Next startup paf file: default
Startup patch package: NULL
Next startup patch package: NULL
Next startup saved-configuration file indicates the configuration file for the next
startup. The displayed information indicates that the configuration file is in vrpcfg.zip
format.
NOTE
– The configuration file must be a *.zip or *.cfg file. If the configuration file is a *.dat file, this
file cannot be synchronized to the MM910.
– If the configuration file is a *.dat file, perform the following operations:
nRun the save Configuration file name command to convert the configuration file into a
*.zip or *.cfg file.
nRun the startup saved-configuration Configuration file name command to set the
configuration file used for the next startup to a *.zip or *.cfg file.
For details, see CX320 Switch Module V100R001C10 Configuration Guide.
2.Save the converged switching plane configuration file from CX320 to the MM910.
<HUAWEI> save
The command output is as follows:
Warning: The current configuration will be written to the device. Continue?
[Y/N]:Y
Now saving the current configuration to the slot 1
Info: Save the configuration successfully.
begin synchronize configuration to SMM ...
slot 1: upload configuration to SMM successfully.
<HUAWEI>
3.Check that the configuration file is synchronized to the MM910 successfully.
<HUAWEI> reboot
If the following information is displayed, the configuration file is successfully
synchronized.
slot 2:
Next startup system software: flash:/xxx.cc
Next startup saved-configuration file: flash:/vrpcfg.zip
Next startup paf file: default
Next startup patch package: NULL
begin synchronize configuration to SMM ...
slot 2: upload configuration to SMM successfully.
System will reboot! Continue? [Y/N]:
If a configuration file synchronization failure message is displayed, contact Huawei
technical support.
4.Enter N to not restart the converged switching plane.
5.Connect the Ethernet port on a PC to the MGMT network ports on the panels of the
active and standby MM910 over a local area network (LAN).
– If the MGMT port on the active MM910 is already connected with a network cable,
do not remove the network cable from the MGMT port. Otherwise, an active/standby
switchover of the MM910s will be triggered, which may cause network interruption.
– If you want to connect your local PC directly to the MM910 using a network cable
but the MGMT port on the active MM910 is already connected with a network cable,
connect the network cable from the local PC to the STACK port of the active
MM910 in the chassis. If the STACK port on the active MM910 is also used, connect
the network cable to an idle STACK port on an active MM910 in a chassis cascaded
with the E9000 chassis.
6.Use an SSH connection tool to log in to the MM910 CLI by using the floating IP address
of the MM910s.
This topic describes how to use PuTTY to log in over SSH. For details, see 6.2 Logging
In to the MM910 CLI Over a Network Port by Using PuTTY.
7.Query the version of the MM910.
smmget -l smm -d version
The information is displayed as follows:
SMM Version Information:
Uboot Version :(U54)012
CPLD Version :(U1082)008 121120
PCB Version :SMMA REV B
BOM Version : 003
FPGA Version :(U1049)007 121116
Software Version :(U54)2.0
IPMI Module Built:Mar 14 2013 22:31:44
The value of the parameter Software Version is the software version of the MM910.
8.Select an operation based on the MM910 software version.
– If the software version is earlier than (U54) 3.00, go to Step 4.9 to Step 4.11.
– If the software version is (U54) 3.00 or later, perform Step 4.10 to Step 4.11.
9.Use a cross-platform file transfer tool, and enter the floating IP address of the MM910 to
download the configuration file to the PC in binary file transmission mode.
For operation details, see E9000 Server V100R001 Upgrade Guide.
10. Run the following command on the MM910 CLI to export the configuration file of the
converged switching plane.
root@SMM:/# swiconfexport swiN
N: specifies the slot number of a switch module. Its value ranges from 1 to 4, mapping to
switch module slots 1E, 2X, 3X, and 4E respectively.
The following information is displayed with the configuration file name and directory.
11. Use a cross-platform file transfer tool, and enter the MM910 floating IP address to
download the configuration file shown in the command output to the PC in binary file
transmission mode.
This topic uses WinSCP as the cross-platform file transfer tool. For details, see 6.6
Set the WinSCP transfer mode to the binary mode as follows: Enter the shortcut keys Ctrl+Alt+P.
The Preferences window is displayed. In the navigation tree on the left, choose Transfer, and
click Binary and OK.
The configuration file is downloaded to the PC and decompressed. The converged
switching plane configuration file is 13_1_1.cfg.
This topic describes how to restore the configuration file to the CX320. If configuration errors
occur or the CX320 is faulty, you can use the backup configuration file to restore
configuration data.
Use one of the following methods to back up the converged switching plane configuration
file:
Procedure
Step 1 Log in to the converged switching plane command-line interface (CLI).
Step 2 Log in to the MM910 CLI.
Step 3 Restore the converged switching plane configuration file.
lPower on the converged switching plane to automatically use the configuration file in the
MM910 to restore configuration data. This topic does not describe the automatic
restoration.
lUpload and load the configuration file of the converged switching plane to the MM910
and restart the converged switching plane. The system automatically uses the
configuration file of the MM910 to restore configuration data. For details, see the
following procedures in this topic.
1.Connect the Ethernet port on a PC to the MGMT network ports on the panels of the
active and standby MM910 over a local area network (LAN).
– If the MGMT port on the active MM910 is already connected with a network cable,
do not remove the network cable from the MGMT port. Otherwise, an active/standby
switchover of the MM910s will be triggered, which may cause network interruption.
– If you want to connect your local PC directly to the MM910 using a network cable
but the MGMT port on the active MM910 is already connected with a network cable,
connect the network cable from the local PC to the STACK port of the active
MM910 in the chassis. If the STACK port on the active MM910 is also used, connect
the network cable to an idle STACK port on an active MM910 in a chassis cascaded
with the E9000 chassis.
Step 4 Select an operation based on the MM910 software version.
5 Restoring the Configuration File
2.Use an SSH connection tool to log in to the MM910 CLI by using the floating IP address
of the MM910s.
This topic describes how to use PuTTY to log in over SSH. For details, see 6.2 Logging
In to the MM910 CLI Over a Network Port by Using PuTTY.
3.Query the version of the MM910.
smmget -l smm -d version
The information is displayed as follows:
SMM Version Information:
Uboot Version :(U54)012
CPLD Version :(U1082)008 121120
PCB Version :SMMA REV B
BOM Version : 003
FPGA Version :(U1049)007 121116
Software Version :(U54)2.0
IPMI Module Built:Mar 14 2013 22:31:44
The value of the parameter Software Version is the software version of the MM910.
lIf the software version is earlier than (U54) 3.00, perform Step 5 to Step 7.
lIf the software version is (U54) 3.00 or later, perform Step 6 to Step 7.
Step 5 Upgrade the MM910 software to (U54) 3.00 or a later version.
For operation details, see E9000 Server V100R001 Upgrade Guide.
Step 6 Use a cross-platform file transfer tool and enter the floating IP address of the MM910 to
transfer the configuration file on the PC to the MM910 in binary file transmission mode.
NOTE
You are advised to create a new name for the existing configuration file and back it up in the MM910
before the uploading. Otherwise, the existing configuration file in the MM910 will be replaced by the
uploaded configuration file. For details about the configuration file backup, see 4.9 Backing Up the
Configuration File.
lConfiguration file name: 13_1_1.cfg.
lThe upload path of the configuration file is /tmp/exchang/swiN.
N ranges from 1 to 4, mapping to switch module slots 1E, 2X, 3X, and 4E respectively.
This topic uses WinSCP as the cross-platform file transfer tool. For details, see 6.6
Transferring Files Using WinSCP.
NOTE
Set the WinSCP transfer mode to the binary mode as follows: Enter the shortcut keys Ctrl+Alt+P. The
Preferences window is displayed. In the navigation tree on the left, choose Transfer, and click Binary
and OK.
Step 7 Run the following command on the MM910 CLI to load the configuration file of the
lplanenum: indicates the numbers of the switching planes. The value of the converged
switching plane is 1.
lfilename: indicates the name of the configuration file to be loaded.
The following information is displayed:
In this condition,if offline configuration success,the blade will
reboot.
Do you want to continue?[Y/
N]:y
Success
The MM910 restarts automatically after the configuration file is successfully loaded to
the converged switching plane, and the configuration file is automatically restored after
the restart.
6.1 Logging In to or a Switch Module over MM910 SOL
Log in to a switch module by using the serial over LAN (SOL) function provided by the
MM910.
6.2 Logging In to the MM910 CLI Over a Network Port by Using PuTTY
This topic describes how to use PuTTY to remotely log in to a server over a local area
network (LAN) and to configure and maintain the server.
6.3 Logging In to a Device Over a Serial Port by Using PuTTY
6.4 Powering On or Off a Switching Plane
This topic describes how to power on or off the converged switching plane of CX320.
6.5 Logging In to the MM910 WebUI
6.6 Transferring Files Using WinSCP
Transfer files on the local computer using WinSCP.
6.7 Using the MM910 WebUI to Collect converged switching plane Information
This topic describes how to use the MM910 WebUI (MM910 software version: 6.00 or later)
to collect logs of the converged switching plane (switching plane software version: 5.30 or
later).
6.8 Configuring an FTP Server
Configure an FTP server to transfer files from a PC to a switching plane.
6.9 Using the CLI to Collect converged switching plane Information
6.1 Logging In to or a Switch Module over MM910 SOL
Log in to a switch module by using the serial over LAN (SOL) function provided by the
MM910.
Prerequisites
Data
lUser name and password for logging in to the MM910
Default user name: root; default password: Huawei12#$
Step 1 Log in to the MM910 CLI by using PuTTY and the floating IP address of the MM910.
Step 2 Log in to the SOL CLI.
6 Common Operations
lPassword for logging in to the switch modules to be connected
Default password: Huawei12#$
For details about how to use PuTTY, see 6.2 Logging In to the MM910 CLI Over a
Network Port by Using PuTTY.
telnet 0 1101
The command output is as follows:
*=====================================================================*
* Welcome to SMM SOL Server *
* Please log in with SMM account and password. *
*=====================================================================*
user name:
Step 3 Enter the user name and password.
The following information is displayed:
Log in Success!
*=================================================================================
==========================
please input the SOL Blade1~Blade16(1 ~ 16), Blade1A~Blade16A(17 ~ 32),
Swi1~Swi4(33 ~ 36) and COM#(n)
press Ctrl+R to return
*=================================================================================
==========================
lYou want to perform initial configuration of the device.
lThe device is inaccessible over a network port.
NOTE
The device that is logged in to is a management module, compute node, or switch module in an
E9000 chassis.
When logging in to a management module, you must connect the serial port to the COM serial
port of the MM910.
When logging in to a compute node, you can connect the serial port to the SYS serial port or BMC
chip of the compute node.
lThe E9000 compute nodes do not provide serial ports. To log in to a compute node over a
serial port, connect a multi-port cable to a universal connector port (UCP) and log in through
the serial port of the multi-port cable. If the compute node does not provide a UCP, you can
log in to the compute node only through a network port. For details, see 6.1 Logging In to
or a Switch Module over MM910 SOL.
lOn the MM910 CLI, run the bmccomstate and switchcom commands to query and switch
the objects connected to the serial ports. For details, see the MM910 Management Module
V100R001 Command Reference.
When logging in to a switch module, you can connect the serial port to the Ethernet switching
plane, FC switching plane, or BMC chip.
l If the switch module panel has the BMC serial port and SYS serial port, the BMC serial port is
connected to the BMC chip, and the SYS serial port can be connected to the Ethernet
switching plane or FC switching plane.
l If the switch module panel has only the COM serial port, the COM serial port can be
connected to the Ethernet switching plane, FC switching plane, or BMC chip.
l If the switch module panel has only the BMC serial port, the BMC serial port is connected to
the BMC chip.
l On the MM910 CLI, run the bmccomstate and switchcom commands to query and switch the
objects connected to the serial ports. For details, see the MM910 Management Module
V100R001 Command Reference.
For details about serial ports of the CX920, see Table 2-2.
Prerequisites
Conditions
The connection varies depending on the target device:
lCompute node: Connect the local PC to the serial port of the multi-port cable of the
target compute node.
lSwitch module: Connect the local PC to the serial port of the target switch module.
lManagement module: Connect the local PC to the serial (COM) port of the target
MM910.
Data
User name and password for logging in to the target device
l If there are five consecutive attempts to log in to the MM910 WebUI with incorrect passwords, the
account is locked. It will be automatically unlocked after 10 minutes. If you enter a password within
this time, the lock is reset to 10 minutes even if the password is correct.
l An account can log in to the HMM WebUI only through one IP address at a time. If an account is
logged in and then logs in through another IP address, the account will be logged out.
l After logging in to the MM910 CLI or WebUI, you are logged out of the management UI if you do
not perform any operation within a specified time period. The default lockout duration of the CLI is
2 minutes and that of the WebUI is 5 minutes. You can change the values as required.
l The MM910 supports a maximum of 32 clients to log in to the WebUI and 100 clients to log in to
the CLI at the same time.
l "This is the standby MM" is displayed for the WebUI of the standby MM910. The standby MM910
WebUI does not display component installation status. On the WebUI of the standby MM910, you
can only view monitoring information about the active MM910, set the DHCP and static IP
addresses, and set and query the thresholds and hysteresis of the sensors of the standby MM910. To
perform other operations, log in to the WebUI of the active MM910.
l For details about the operations on the WebUI, see the Online Help.
Conditions
The client (a PC) used to access the HMM WebUI must meet the requirements listed in Table
6-1.
Table 6-1 Runtime environment requirements
OS
Window
s
l Windows 7 32-
bit/64-bit
l Windows 8 32-
bit/64-bit
l Windows Server
2008
Web BrowserJRE
l Internet Explorer 9 or
l JRE 1.6 or later if the
later
l Mozilla Firefox 19.0
to 31.0
l Chrome 22.0 to 31.0
l JRE 1.7 or later if the
MM910 version is
earlier than
(U54)5.51
MM910 version is
(U54)5.51 and later
l Windows Server
2012
LinuxRed Hat Enterprise
Linux (RHEL) 4.3 to 6.0
Mozilla Firefox 19.0 to
31.0
NOTE
This task uses Internet Explorer 11 in Windows 7 as an example.
Data
User name and password for logging in to the server
lConnect the network port of the local PC to the MGMT port of the active or standby
MM910.
Figure 6-5 shows the network connections.
Figure 6-5 Network connections
MGMT port on the active MM910 is already connected with a network cable, do
If the
not remove the network cable from the MGMT port. Otherwise, an active/standby
switchover of the MM910s will be triggered, which may cause network interruption.
NOTE
The MM910 management port is provided by either of the following modes:
– An Ethernet port on the switch module in slot 2X or 3X.
However, if a CX910/CX911/CX912/CX913 is in slot 2X or 3X, only a GE port can be used;
if a CX920 is in slot 2X or 3X, only a 10GE port can be used. The CX910/CX911/CX912/
CX913 are not recommended for providing the management port of the management module.
– MGMT port on the MM910 panel
– For the MM910 (U54)2.25 or earlier, the management port is provided by the switch module
by default. For the MM910 (U54)2.26 or later, the management port is provided by the
MM910 by default. For details about how to query the MM910 version, see MM910
Management Module V100R001 User Guide.
– You can run the outportmode command to change the mode in which the MM910
management port is provided. If the switch module in slot 2X or 3X is used to provide the
management port, do not connect the MM910 MGMT port and the switch module ports to the
same network. Otherwise, a network storm will occur and the network will be interrupted. For
details, see MM910 Management Module V100R001 Command Reference.
lConnect the network port of the local PC to the MGMT or STACK port of the active
– If the MGMT port of the active MM910 is available, use this port. Figure 6-6
shows the connection.
Figure 6-6 Connection between the local PC and the active MM910 (in slot MM2
in this example)
– If the MGMT port of the active MM910 is unavailable, connect the PC to the
STACK port of the active MM910. If the STACK port is used to stack the MGMT
port in another chassis, connect the PC to an idle STACK port on an active MM910
in a chassis cascaded with the E9000 chassis. Figure 6-7 shows the connection.
If the MGMT port on the active MM910 is already connected with a network cable,
do not remove the network cable from the MGMT port. Otherwise, an active/
standby switchover of the MM910s will be triggered, which may cause network
interruption.