RCMS2903-4E1-4GE (A) Configuration Guide (Rel - 02)

www.raisecom.
com
RCMS2903-4E1-4GE (A)
Configuration Guide
(Rel_02)
Raisecom Technology Co., Ltd. provides customers with comprehensive technical support and services. For any
assistance, please contact our local office or company headquarters.
Website: http://www.raisecom.com
Tel: 8610-82883305
Fax: 8610-82883056
Email: export@raisecom.com
Address: Building 2, No. 28, Shangdi 6th Street, Haidian District, Beijing, P.R.China
Postal code: 100085
-----------------------------------------------------------------------------------------------------------------------------------------
Notice
Copyright © 2013
Raisecom
All rights reserved.
No part of this publication may be excerpted, reproduced, translated or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in Writing from Raisecom
Technology Co., Ltd.
is the trademark of Raisecom Technology Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.
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 the warranty of any kind, express or implied.
Raisecom
RCMS2903-4E1-4GE (A) Configuration Guide Preface
Preface
Objectives
This document describes basic configurations, system management, SNMP, Ethernet access,
E1 access, and alarm management. Moreover, it provides some related configuration
examples.
Versions
The following table lists the product versions related to this document.
Product name Hardware version Software version

RCMS2903-4E1-4GE A.01 or later 1.2.0 or later
Conventions
Symbol conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a medium or low level of risk which, if
not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not avoided,

could cause equipment damage, data loss, and performance
degradation, or unexpected results.
Provides additional information to emphasize or supplement
important points of the main text.
Indicates a tip that may help you solve a problem or save time.
Raisecom Technology Co., Ltd. i

Raisecom
General conventions
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Arial Paragraphs in Warning, Caution, Notes, and Tip are in Arial.
Boldface Names of files, directories, folders, and users are in boldface.
For example, log in as user root.
Italic Book titles are in italics.
Lucida Console Terminal display is in Lucida Console.
Command conventions
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in square brackets [ ] are
optional.
{ x | y | ... } Alternative items are grouped in braces and separated by
vertical bars. Only one is selected.
[ x | y | ... ] Optional alternative items are grouped in square brackets and
separated by vertical bars. One or none is selected.
{ x | y | ... } * Alternative items are grouped in braces and separated by
vertical bars. A minimum of one or a maximum of all can be
selected.
[ x | y | ... ] * Optional alternative items are grouped in square brackets and
separated by vertical bars. A minimum of none or a maximum
of all can be selected.
Change history
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Issue 02 (2013-06-20)
Initial commercial release
 Added the description of the device_role { master | slave } command. The RCMS2903-
4E1-4GE can be configured with the master/slave mode. In master mode, the fourth
Ethernet interface of the device supports SNMP.
Raisecom Technology Co., Ltd. ii

Raisecom
 Added alarm management.

 Modified some description.
Issue 01 (2012-12-20)
Initial commercial release
Raisecom Technology Co., Ltd. iii

Raisecom
RCMS2903-4E1-4GE (A) Configuration Guide Contents
Contents
1 Basic configurations ..................................................................................................................... 1

1.1 CLI ................................................................................................................................................................... 1
1.1.1 Overview ................................................................................................................................................. 1
1.1.2 Command line modes.............................................................................................................................. 1
1.1.3 Shortcuts ................................................................................................................................................. 3
1.1.4 Seeking help ............................................................................................................................................ 4
1.2 Basic command ................................................................................................................................................ 6
1.2.1 Common operation command ................................................................................................................. 6
1.2.2 Terminal operation command.................................................................................................................. 7
1.2.3 Sysyem operation command ................................................................................................................... 7
1.3 Accessing the device ........................................................................................................................................ 7
1.4 Managing users ................................................................................................................................................ 9
1.4.1 Configuring users .................................................................................................................................... 9
1.4.2 Checking configurations ......................................................................................................................... 9
1.5 Managing log ................................................................................................................................................. 10
1.5.1 Preparing for configurations ................................................................................................................. 10
1.5.2 Enable log management ........................................................................................................................ 10
1.5.3 Checking configurations ....................................................................................................................... 10
1.6 Managing files ................................................................................................................................................ 10
1.6.1 Classifying files .................................................................................................................................... 10
1.6.2 Backing up files .................................................................................................................................... 11
1.6.3 Updating files ........................................................................................................................................ 12
1.7 Managing time ............................................................................................................................................... 12
1.7.1 Configuring time and time zone ............................................................................................................ 12
1.7.2 Configuring DST .................................................................................................................................. 12
1.8 Managing the device ...................................................................................................................................... 13
1.8.1 Configuring the mode ........................................................................................................................... 13
1.8.2 Synchronizing configurations on the Console interface ........................................................................ 14
1.8.3 Modifying the host name ...................................................................................................................... 14
1.8.4 Restoring/Checking the manufacture configuration .............................................................................. 14
1.8.5 Checking information about the device ................................................................................................ 14
Raisecom Technology Co., Ltd. iv

Raisecom
1.8.6 Checking the CPU ulilization ratio ....................................................................................................... 15

2 System management ................................................................................................................... 16

2.1 Configuring ALS ............................................................................................................................................ 16
2.2 Configuring failover ....................................................................................................................................... 17
2.2.2 Configuring failover .............................................................................................................................. 17
2.3 Configuring static routing .............................................................................................................................. 18
2.3.2 Configuring static routing ..................................................................................................................... 18
2.4 Configuring alarm masking for E1 idle tributary ........................................................................................... 18
2.4.2 Configuring alarm masking for E1 idle tributary .................................................................................. 19
2.5 Checking configurations ................................................................................................................................ 19
2.6 Maintenance ................................................................................................................................................... 19
2.7 Configuration examples ................................................................................................................................. 19
3 Network management ................................................................................................................ 25

3.1 Introduction .................................................................................................................................................... 25
3.2 Preparing for configurations ........................................................................................................................... 25
3.3 Configuring basic functions of SNMP ........................................................................................................... 26
3.4 Configuring Trap feature ................................................................................................................................ 26
3.5 Configuring static ARP .................................................................................................................................. 27
3.7 Maintenance ................................................................................................................................................... 27
4 Configuring Ethernet access ..................................................................................................... 28

4.1 Introduction .................................................................................................................................................... 28
4.1.1 Ethernet interface .................................................................................................................................. 28
4.1.2 Switching interface ............................................................................................................................... 29
4.1.3 VLAN ................................................................................................................................................... 29
4.1.4 QoS ....................................................................................................................................................... 30
4.1.5 Storm control ........................................................................................................................................ 31
4.2 Configuring the interface ............................................................................................................................... 31
4.2.2 Configuring GE electrial interface ........................................................................................................ 31
4.2.3 Configuring GF optical interface .......................................................................................................... 32
4.3 Configuring VLAN ........................................................................................................................................ 33
4.3.2 Configuring VLAN modes .................................................................................................................... 33
Raisecom Technology Co., Ltd. v

Raisecom
4.3.3 Configuring VLAN entries ................................................................................................................... 33

4.4 Configuring QoS ............................................................................................................................................ 34
4.4.2 Enabling QoS ........................................................................................................................................ 35
4.4.3 Configuring traffic classfication ........................................................................................................... 35
4.4.4 Configuring queue mapping .................................................................................................................. 35
4.4.5 Configuring queue scheduling .............................................................................................................. 36
4.5 Configuring rate limiting ................................................................................................................................ 36
4.5.2 Configuring interface-based rate limiting ............................................................................................. 36
4.5.3 Configuring VLAN-based rate limiting ................................................................................................ 37
4.6 Configuring storm control .............................................................................................................................. 37
4.6.2 Configuring storm control ..................................................................................................................... 38
4.6.3 Configuring the rate for strom control .................................................................................................. 38
4.7 Maintenance ................................................................................................................................................... 39
4.8 Configuration example ................................................................................................................................... 39
5 Configuring E1 access ................................................................................................................ 43

5.1 Introduction .................................................................................................................................................... 43
5.2 Configuring the interface ............................................................................................................................... 44
5.2.2 Configuring E1 interface ....................................................................................................................... 45
5.3 Configuring loopback ..................................................................................................................................... 45
5.3.2 Local loopback ...................................................................................................................................... 45
5.3.3 Remote loopback .................................................................................................................................. 46
5.3.4 Configuring BERT ................................................................................................................................ 46
5.4 Maintenance ................................................................................................................................................... 47
6 Alarm management..................................................................................................................... 48
6.1 Introduction .................................................................................................................................................... 48
6.2 Configuring alarm inhibition .......................................................................................................................... 51
6.3 Configuring alarm delay................................................................................................................................. 51
6.4 Configuring alarm saving ............................................................................................................................... 52
6.5 Configuring alarm auto-report........................................................................................................................ 52
6.6 Configuring alarm inverse reporting .............................................................................................................. 53
Raisecom Technology Co., Ltd. vi

Raisecom
6.7 Configuring alarm monitoring........................................................................................................................ 54

6.8 Configuring alarm masking ............................................................................................................................ 54
6.10 Maintenance ................................................................................................................................................. 55
7 Appendix ...................................................................................................................................... 56
7.1 Terms .............................................................................................................................................................. 56
7.2 Acronyms and abbreviations .......................................................................................................................... 57
Raisecom Technology Co., Ltd. vii

Raisecom
RCMS2903-4E1-4GE (A)Configuration Guide 1 Basic configurations
Figures
Figure 1-1 Login connection through the Console interface .................................................................................. 7
Figure 1-2 COM1 properties .................................................................................................................................. 8
Figure 2-1 Backing up or upgrading files............................................................................................................. 20
Figure 4-1 Ethernet access networking ................................................................................................................ 39
Figure 5-1 Local bidirectional loopback .............................................................................................................. 44
Figure 5-2 Remote internal loopback ................................................................................................................... 44
Raisecom Technology Co., Ltd. viii

Raisecom
Tables
Table 1-1 List of File Types.................................................................................................................................. 11
Raisecom Technology Co., Ltd. ix

Raisecom
1 Basic configurations
This chapter describes the basic configurations of the RCMS2903-4E1-4GE.

 CLI
 Basic command
 Accessing the device
 Managing users
 Managing log
 Managing files
 Managing time
 Managing the device
1.1 CLI
1.1.1 Overview
Command Line Interface (CLI) is a way of interaction between you and the RCMS2903-4E1-
4GE. You can complete device configuration, monitoring and management by executing
related commands.
The features of CLI:
 Local configuration via the Console interface is available.
 Remote configuration via Telnet is available.
 Different command types belong to different command modes. You can only execute a
type of configuration in its related command mode.
 You can operate the commands by shortcut keys.
 You can view or execute a history command by transferring history record.
 You can seek online help is available by inputting "?" at any time.
 CLI provides smart analysis methods, such as incomplete matching and context
association, etc. to facilitate users' input.
1.1.2 Command line modes

The RCMS2903-4E1-4GE supports the following command line modes:
Raisecom Technology Co., Ltd. 1

Raisecom
Mode Description Access methods Identification

User EXEC You can configure Enter the user name Raisecom>
mode basic information about and password to
the terminal in this access the
mode. RCMS2903-4E1-
4GE.
Privileged You can configure In user EXEC mode, Raisecom#
EXEC mode basic information about enter enable and the
the RCMS2903-4E1- password.
4GE, such as the
system time rather than
the operation
information in this
mode.
Global You can configure In privileged EXEC Raisecom(config)#
configuration operation parameters of mode, enter the
mode the RCMS2903-4E1- config command.
4GE in this mode.
Remote You can remotely In global Raisecom(config-
configuration configure operation configuration mode, remote/*/*)#
mode parameters of the enter the remote slot-
RCMS2903-4E1-4GE id device-id
in this mode. command.
GE electrical You can configure In global Raisecom(config-
interface properties of the GE configuration mode, ge/*)#
configuration electrical interface in enter the interface ge
mode this mode. interface-number
command.
GF optical You can configure In global Raisecom(config-
interface properties of the GF configuration mode, fx-ge/*)#
configuration optical interface in this enter the interface
mode mode. fx-ge interface-
number command.
PDH optical You can check In global Raisecom(config-
interface properties of the PDH configuration mode, pdh-opt/1)#
configuration optical interface in this enter the interface
mode mode. pdh-opt interface-
number command.
PDH SFP You can configure In global Raisecom(config-
optical properties of the PDH configuration mode, sfp-pdh-opt/1)#
interface SFP optical interface in enter the interface
configuration this mode. sfp pdh-opt sfp-
mode number command.
E1 interface You can check In global Raisecom(config-
configuration properties of the E1 configuration mode, e1/*)#
mode interface in this mode. enter the interface e1
interface-number
command.

Raisecom
Mode Description Access methods Identification

Switching You can check In slot configuration Raisecom(config-
interface properties of the mode, enter the esw/*)#
configuration Switching interface in interface switchport
mode this mode. interface-number
command.
1.1.3 Shortcuts
The RCMS2903-4E1-4GE supports the following command line shortcuts:
Shortcut Description
Up cursor key (↑) Show previous command if there is any command input
earlier; the display has no change if the current command is
the earliest one in history records.
Down cursor key (↓) Show next command if there is any newer command; the
display has no change if the current command is the newest
one in history records.
Left cursor key (←) Move the cursor one character to left; the display has no
change if the cursor is at the beginning of command.
Right cursor key (→) Move the cursor one character to right; the display has no
change if the cursor is at the end of command.
Backspace Delete the character before the cursor; the display has no
change if the cursor is at the beginning of command.
Tab Click Tab after inputting a complete keyword, cursor will
automatically appear a space to the end; click Tab again, the
system will show the follow-up inputting keywords.
Click Tab after inputting an incomplete keyword, system
automatically executes partial helps:
 System take the complete keyword to replace input if the
matched keyword is the one and only, and leave one word
space between the cursor and end of keyword;
 In case of mismatch or matched keyword is not the one and
only, display prefix at first, then click Tab to check words

circularly, no space from cursor to the end of keyword, click
Space key to input the next word;
 If input incorrect keyword, click Tab will change to the next
line and prompt error, the input keyword will not change.
Ctrl+A Move the cursor to the head of line.
Ctrl+D or Delete Delete the cursor location characters
Ctrl+E Move the cursor to the end of line.
Ctrl+K Delete all characters behind the cursor (including cursor
location).

Raisecom
Ctrl+X Delete all characters before the cursor (except cursor
location).
Ctrl+Z Return to privileged EXEC mode from other modes (except
for user EXEC mode).
1.1.4 Seeking help
Complete help
You can get complete help in the below three conditions:
 Click "?" in any command mode to get all commands and their brief description under
the command view.
Raisecom> ?
Display as below:
Raisecom>
chinese Help message in chinese.
clear Clear screen
enable Turn on privileged mode command
english Help message in english
exit Exit current mode and down to previous mode
help Message about help
history Show most recent history command
list List command
no Negate a command or set its defaults
quit Exit current system
show Show running system information
terminal Configuration of terminal
trace-dest trace destination
 Input a keyword followed by a "?" after one character space, if the position of "?" is
keyword, list all keyword and brief description.
Raisecom(config)# interface ?
Display as below:
Raisecom(config)# interface

Raisecom
e1 E1 interface mode
fx-ge fx-ge interface mode
ge ge interface mode
pdh-opt Optical inetrface
sfp sfp interface mode
snmp Interface type
switchport esw interface mode
 Input a keyword followed by a "?" after one character space, if the position of "?" is a
parameter, list the range and brief description.
Raisecom(config)# interface e1 ?
Display as below:
Raisecom(config)# interface e1
<1-4> ID
Partial help
You can get partial help in the below three conditions:
 Input a character string and start with a "?", the RCMS2903-4E1-4GE will list all
keywords starting with the character string under current mode.
Raisecom(config)#a?
Display as below:
Raisecom(config)# a
als Config OPT ALS
arp ARP command
assert-dest assert destination
 Input a command followed by a character string with "?", the RCMS2903-4E1-4GE will
list all keywords start with the character string in the command of current mode.
Raisecom(config)# show in?
Display as below:

Raisecom
Raisecom(config)# show in
info Device information
interface Interface information
Error prompt messages

The RCMS2903-4E1-4GE prints out the following error prompt according to error type when
you input incorrect commands:
% " * " Incomplete command. Command line is incomplete.
% Invalid input at '^' marked. Keyword marked with "^" marked is illegal or
does not exist.
% Ambiguous input at '^' marked, Keyword marked with "^" is ambiguous.
follow keywords match it.
% " * " Unconfirmed command. Command line is not exclusive.
% " * " Unknown command. Command line does not exist.
% You Need higher priority! Command line cannot be executed due to limited
authority.
1.2 Basic command

1.2.1 Common operation command
The following commands can be executed in any command line modes.
Command Description
clear Delete prompt information on the screen.
end Return to the privileged mode.
english Display the help and prompt information in
English.
exit Return to the upper-level mode.
help Check the help information.
history Check the history records.
list Check the list of all commands in current mode.
quit Log out.

Raisecom
1.2.2 Terminal operation command

The following commands can be executed in common EXEC mode.
Command Description
Raisecom> terminal line Configure line numbers of the terminal.
{ number | unlimited }
Raisecom> terminal time-out Configure the maximum no-operation timeout of
time the terminal.
Raisecom> terminal history Configure the number of the recorded history
number commands.
1.2.3 Sysyem operation command

The following commands can be executed in privileged EXEC mode.
Command Description
Raisecom# hostname hostname Modify the system name.
Raisecom# logout Exit from the current login, which can also be
realized by entering quit or exit.
Raisecom# reboot Restart the device.
Raisecom# show rotp-cpu- Show the utilization ratio of CPU.
utilization-ratio
1.3 Accessing the device

Use a configuration line to connect the serial port of the PC to the Console interface of
the.RC3000-15, as shown in Figure 1-1.
Figure 1-1 Login connection through the Console interface

Raisecom
When accessing the RCMS2903-4E1-4GE through the Console interface, use the
CBL-RS232-DB9F/RJ45-2m Console cable delivered with the RCMS2903-4E1-4GE.
Step 1 Run the terminal emulation program on the PC.
1. Choose Start > All Programs > Accessories > Communications > Hyper Terminal.
2. Input a name, and click OK.
3. Select COM1, and click OK.
4. Configure COM1 properties as shown in Figure 1-2, and click OK.
Figure 1-2 COM1 properties
Step 2 If the device is starting, it displays login information dynamically on the terminal software.
When a welcome prompt is displayed, press Enter to enter the login interface. If the device
has completed the login, it displays blank on the terminal software. Press Enter to enter the
login interface.
Step 3 Input the user name and password. By default, both the user name and password are raisecom.
When being inputting, the password is not displayed as plain text.
Login: raisecom
Password:

Raisecom
Step 4 Enter the privileged ECEX mode. By default, the user name is enable and the password is
raisecom.
Raisecom> enable
Password:
Step 5 After entering privileged ECEX mode, you can log in to the RCMS2903-4E1-4GE
successfully. Then, you can configure it as needed.
Raisecom#
1.4 Managing users

1.4.1 Configuring users
Configure the RCMS2903-4E1-4GE as below.
Step Command Description

1 Raisecom# user user-name password { no- Create a user and configure the password.
encryption | md5 } password
Use the no user user-name command to delete
the user.
2 Raisecom# user user-name privilege Configure user privilege.
{ administrant | limited | normal }
3 Raisecom# password (Optional) modify the user name and
password.
4 Raisecom# save user Save user information.
1.4.2 Checking configurations


1 Raisecom# show user Show information about all users.
2 Raisecom# who Show information about the current user.
3 Raisecom# show terminal Show information about the terminal user.

Raisecom
1.5 Managing log

1.5.1 Preparing for configurations
Scenario
After the system log is enabled, the login and alarm information will be recorded in the log.
You can search for related information through the log.
Prerequisite
N/A
1.5.2 Enable log management


1 Raisecom# config Enter global configuration mode.
2 Raisecom(config)# log enable Enable system log.
By default, it is enabled.

Check configurations on the RCMS2903-4E1-4GE by using the commands as below.
No. Command Description

1 Raisecom# show log [ key1 string ] Show contents of the system log.
[ key2 string ] [ key3 string ]
1.6 Managing files

1.6.1 Classifying files
Files of the RCMS2903-4E1-4GE contain system software and startup configuration files.

Raisecom
Table 1-1 List of File Types

File type Description
System software  The suffix of system software is .z.
 Use the upload and download commands to back up or update system
software by uploading to the server or downloading to the system through
FTP or TFTP protocol.
 Use the show version command to check the version information of the
system software.
Startup configuration file  The Default name of the startup configuration file is startup_config.conf.
 Use the write command to write the configuration file to Flash file
system. The stored new configuration will execute automatically when the
system restarts.
 Use the erase startup-config command to delete the startup configuration
files.
 Use upload and download commands to back up or update the
configuration by uploading to the server or download to the system
through FTP or TFTP.
 Use the show startup-config command to check the stored startup
configuration information.
 Use the show running-config command to check the current running
configuration information of the system.
 Use the show this command to check the configuration information of the
current system and command node.
1.6.2 Backing up files

The RCMS2903-4E1-4GE supports the File Transfer Protocol (FTP) and Trivial File Transfer
Protocol (TFTP) when backing up and upgrading files.

1 Raisecom# updata-system-software Connect the Ethernet interface and CPU of
the device.
2 Raisecom# upload { system-boot | startup- Upload files to the server for backing up.
config | default-startup-config | fpga-
image } { ftp | tftp }

Raisecom
1.6.3 Updating files
Upgrading files in privileged EXEC mode

1 Raisecom# download { fpga-image | license- Download files from the server for
dat | system-boot | startup-config | upgrading.
default-startup-config | bootrom } { ftp |
tftp }
Upgrading files in BootROM mode

1 [Raisecom]: u Download files from the server.
1.7 Managing time

1.7.1 Configuring time and time zone
To coordinate the RCMS2903-4E1-4GE with other devices, you need to configure system
time and time zone precisely as follows.
Step Configuration Description

1 Raisecom# clock set hour minute second year Configuring system time.
month day
2 Raisecom# clock timezone { + | - } hour Configuring system time zone. By default,
minute it is GMT +8:00.
1.7.2 Configuring DST

Daylight Saving Time (DST) is set locally to save energy. About 110 countries around the
world apply DST in summer, but vary in details. Thus, you need to consider detailed DST
rules locally before configuration.

1 Raisecom# clock summer-time enable Enable DST.
By default, DST is disabled.
2 Raisecom# clock summer-time recurring start- Configuring the period of DST.
week { sun | mon | tue | wed | thu | fri |
sat } start-month start-hour start-minute end-
By default, DST is set forward 60
week { sun | mon | tue | wed | thu | fri | minutes.
sat } end-month end-hour end-minute offset-mm

Raisecom
For example, if DST starts from 02:00 am second Monday of April to 02:00 am
second Monday of September, the clock is moved forward 60 minutes. Thus, the
period between 02:00 and 03:00 second Monday of April is skipped. Configuring time
during this period will fail.
DST in the Southern Hemisphere is opposite to that in the Northern Hemisphere. It is
from September this year to April next year. If the starting month is later than the
ending month, the RCMS2903-4E1-4GE judges that it is located in the Southern
Hemisphere.

No. Item Description

1 Raisecom# show clock [ summer-time-recurring ] Show configurations of the system time,
time zone, and DST.
1.8 Managing the device

1.8.1 Configuring the mode
The RCMS2903-4E1-4GE works in the following two modes:
 Master mode: the fourth GE interface is configured as the SNMP interface to achieve the
out-of-band network management. At this time, the interface can serve as the
management interface only and cannot transmit service data.
 Slave mode: in this mode, the device can be connected uplink to the RCMS2903-4E1-
4GE in master mode, the iTN2100, the OPCOM3500E, and other central office devices
to achieve the Network Element (NE) management.

1 Raisecom# device_role { master | slave } Configure the mode of the RCMS2903-4E1-
4GE.
By default, the device works in slave mode.
After the configurations, you need to restart the RCMS2903-4E1-4GE. Otherwise,

configurations of master/slave mode will not take effect.

Raisecom
1.8.2 Synchronizing configurations on the Console interface


2 Raisecom(config)# remote 1 2 Enter remote configuration mode.
3 Raisecom(config)# sync-configuration Synchronize configurations on the Console
interface to the network management
configurations.
1.8.3 Modifying the host name


1 Raisecom# hostname hostname Modify the host name.
By default, the host name of is Raisecom.
1.8.4 Restoring/Checking the manufacture configuration


1 Raisecom# show manufacture info Show the manufacture information of the local device.
2 Raisecom# show manufacture info Show the manufacture information of the remote
remote 0 device1-id [ device2-id ] device.
[ device3-id ] [ device4-id ]
3 Raisecom# show manufacture info Show the manufacture information of all devices.
all
5 Raisecom(config)# restore-default- Restore to the default manufacture configurations.
configuration
1.8.5 Checking information about the device


2 Raisecom(config)# show info Show information about the local device.

Raisecom

3 Raisecom(config)# show device Show information about the remote device.
4 Raisecom(config)# show device verbose Show detailed configurations of the remote device.
1.8.6 Checking the CPU ulilization ratio


1 Raisecom# show rotp-cpu-utilization-ratio Show the current CPU utilization ratio.


2 Raisecom(config)# show info Show information about the local device.

Raisecom
RCMS2903-4E1-4GE (A)Configuration Guide 2 System management
2 System management
This chapter describes system management of the RCMS2903-4E1-4GE.

 Configuring ALS
 Configuring failover
 Configuring static routing
 Configuring alarm masking for E1 idle tributary
 Checking configurations
 Maintenance
 Configuration examples
2.1 Configuring ALS

Scenario
After configuring the Automatic Laser Shutdown (ALS), you can effectively protect the
performance of the optical interface. Moreover, when the maintenance personnel remove the
fiber out, the laser will be stopped if ALS is enabled. Thus, it can avoid eye damage. And the
service will be automatically recovered when the fiber is plugged in.
Prerequisite
N/A



Raisecom

2 Raisecom(config)# als enable Enable ALS on the optical interface.
By default, ALS is disabled.
2.2 Configuring failover

Scenario
Configure failover from the local optical interface and remote electrical interface to the local
electrical interface.
Failover from the optical interface to the Ethernet electrical interface refers to shutting down
the Ethernet electrical interface when Loss of Signal (LOS) and Loss of Frame (LOF) alarms
are generated on both the local and remote optical interfaces, until the optical interface
recovers on both ingress and egress directions.
Failover from the Ethernet electrical interface to the electrical interface refers to shutting
down the local Ethernet electrical interface when status of all remote Ethernet electrical
interfaces is changed to Link down from Link up, until at least one remote Ethernet interface
recovers to Link up.
Prerequisite
N/A
2.2.2 Configuring failover


1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)# fault-pass enable Enable failover.
Failover from the optical interface to the electrical
interface and from the electrical interface to the
electrical interface of the RCMS2903-4E1-4GE is
enabled or disabled simultaneously.
By default, failover is disabled.

Raisecom
2.3 Configuring static routing

Scenario
The routing is used to select a path and forward packets. The routing is realized through
routing protocols. Routing protocols are rules to maintain the routing table between devices. It
is used to discover routes, generate the routing table, and instruct packet forwarding.
Static routing refers to a type of routing that is manually configured. It has fewer requirements
on the system. The static routing is mainly applied to small-and medium network. However,
the static routing cannot automatically adapt to the network topology changes.
To configure static routing for simple topology network, you need to configure static routing
manually to create an intercommunication network.
Prerequisite
Configure the IP address of the Layer 3 interface properly.
2.3.2 Configuring static routing


2 Raisecom(config)#ip route ip-address ip-mask Configure static routing to the
ip-gate destination network with the IP address
of ip-address.
4 Raisecom(config)#show ip route Show configurations of the static
routing table.
2.4 Configuring alarm masking for E1 idle tributary

Scenario
After alarm masking for the E1 idle tributary is configured, alarms will not be reported to the
network management server if any alarm is generated on the idle E1 tributary.
Prerequisite
N/A

Raisecom
2.4.2 Configuring alarm masking for E1 idle tributary


2 Raisecom(config)# e1tributary-lost- Mask alarms on the E1 idle tributary.
alarm mask
By default, alarm masking for the E1 idle tributary
is disabled.
2.5 Checking configurations


1 Raisecom# show version Show version information about the device.
2 Raisecom(config)# show info Show configurations and status of the device.
3 Raisecom(config)# show this Show operation information on the current node.
2.6 Maintenance
Maintain the RCMS2903-4E1-4GE by using the commands as below.
Command Description
Raisecom(config)# clear statistic Clear all statistics of the device.
Raisecom(config)# reset Reset the device.
Raisecom(config)# restore-default- Restore to the default manufacture configurations.
configuration
2.7 Configuration examples

To back up or upgrade files, you need to connect any GE interface (as the SNMP interface)of
the RCMS2903-4E1-4GE with the Ethernet interface of the PC, as shown in Figure 2-1.

Raisecom
Figure 2-1 Backing up or upgrading files
In the configuration examples, take FTP for example to back up or upgrading files.
You can choose either of the two modes: FTP or TFTP.
Backing up system software

Step 1 Run the FTP client, and configure user name, password, and path for uploading files.
Step 2 Configure the IP address of the SNMP interface of the RC3000-15 and make sure the IP
address of the SNMP interface can ping through the IP address of the PC. For example, the IP
address of RC3000-15 is 192.168.27.98 and the IP address of the PC is 192.168.27.72.
Raisecom# config
Raisecom(config)# interface snmp
Raisecom(config-snmp)# ip address 192.168.27.98 255.255.255.0
Step 3 Connect the Ethernet interface and CPU of the RCMS2903-4E1-4GE.
Raisecom(config-snmp)# end
Raisecom# updata-system-software
Set successfully
Step 4 Upload system software to the PC.
Raisecom# upload system-boot ftp
Step 5 Input the IP address of the PC.
Please input server IP Address : 192.168.27.72

Raisecom
Step 6 Input the user name and password of FTP.
Please input FTP User name : 111111

Please input FTP Password : 111111
Step 7 Input a file name, which can be a string of any valid characters and does not conflict with an
existing file in the saving path. Take rcms2903.z for example.
Please input FTP Server File Name : rcms2903.z
Step 8 Input "y", and press Enter.
Are you sure[Y/N]:y
Step 9 Input "1", and press Enter.
Please select the file for uploading image

1. core:rcms2903.z
2. exit
Please input the number:1
Step 10 Wait until uploading is complete.

When you see the following prompt, it indicates uploading is successful. You can find a
system software file named "rcms2903.z" in the specified path of FTP.
uploading, please wait... finish

Copy file successfully!
Updating system software ( in privileged EXEC mode)

Step 1 Run the FTP client, and configure user name, password, and path for uploading files. For
example, user name and password are the same 111111.
Step 2 Configure the IP address of the SNMP interface of the RC3000-15 and make sure the IP
address of the SNMP interface can ping through the IP address of the PC.
For example, the IP address of RC3000-15 is 192.168.27.98 and the IP address of the PC is
192.168.27.72.
Raisecom# config

Raisecom
Raisecom(config)# interface snmp

Raisecom(config-snmp)# ip address 192.168.27.98 255.255.255.0
Set successfully
Step 3 Download the system software.
Raisecom#download system-boot ftp
Please input server IP Address : 192.168.27.72
Step 5 Input the user name and password of the FTP.
Please input FTP User name : 111111

Please input FTP Password : 111111
Step 6 Input a file name.
Please input FTP Server File Name : rcms2903.z
Are you sure[Y/N]:y
Loading, please wait...

file length = 7154206
Please select the disk for saving image
1. core/
2. exit
Please input the number:1
Step 9 Wait until downloading is complete. When you see the following prompt, it indicates
downloading is successful.

Raisecom
Writing to core disk, please wait.........................

time = 41 s
Copy file successfully!
Please reboot device!
Step 10 Input "y", and press Enter to reboot the RCMS2903-4E1-4GE.
Raisecom# reboot
Do you reboot the device?(Y/N)y
Updating system software (in BootROM mode)

Step 1 Power on or reboot the RCMS2903-4E1-4GE.
Raisecom# reboot
Step 2 When a prompt "booting….Press Space to Enter Bootrom menu......" is displayed, press
Space to enter the BootROM configuration mode.
Step 3 Input "i" to configure the IP address of the RCMS2903-4E1-4GE in the same network
segment with the IP address of the PC.
[Raisecom]: i
Step 4 Input the IP address and subnet mask of the RCMS2903-4E1-4GE.
start look up old ip addr...
old ip address: 192.168.4.28

old ip mask address: 255.255.255.0
new ip address: 192.168.27.98
new ip mask address: 255.255.255.0
Step 5 Input "u", and press Enter to upgrade system software.
[Raisecom]: u

This allows you to transmit files in FTP, which is faster than the serial port transmission if
you input "1".

Raisecom
choose mode for updating core file.
-----------------------------------
- 1. | serial -
-----------------------------------
- 2. | network -
-----------------------------------
please input mode choose...

2
starting config network infor ...

host ip address: 192.168.27.72
Step 8 Input the user name, password, and file name of FTP.
usr: 111111
passwd: 111111
filename: rcms2903.z
starting connect host,please waiting...

Do you want to update image file?<Y/N>y
Step 10 Wait until downloading is complete.

When you see the following prompt, it indicates downloading is successful.
start update core , please wait some minutes.
Step 11 Input "r", and press Enter to reboot the RCMS2903-4E1-4GE.
[Raisecom]: r

Raisecom
RCMS2903-4E1-4GE (A)Configuration Guide 3 Network management
3 Network management
This chapter describes network management of the RCMS2903-4E1-4GE.

 Introduction
 Preparing for configurations
 Configuring basic functions of SNMP
 Configuring static ARP
 Maintenance
3.1 Introduction
Simple Network Management Protocol (SNMP) is designed by the Internet Engineering Task
Force (IETF) to resolve problems in managing network devices connected to the Internet.
Through SNMP, a network management system can manage all network devices that support
SNMP, including monitoring network status, modifying configurations of a network device,
and receiving network alarms. SNMP is the most widely used network management protocol
in TCP/IP networks.
SNMP is separated into two parts: Agent and Network Management System (NMS). In the
SNMP network, the Agent is a managed device while the NMS is a manager. The Agent and
NMS communicate through SNMP packets transmitted through UDP.
3.2 Preparing for configurations

Scenario
When you need to log in to the RCMS2903-4E1-4GE through the NView NNM system, you
should configure basic SNMP functions on the RCMS2903-4E1-4GE.
Prerequisite
Before configuring SNMP, you should perform the following operations:
 Configure the IP address of the SNMP interface.

Raisecom
 Configure a routing protocol, making the route between the RCMS2903-4E1-4GE and
the NView NNM system reachable.
3.3 Configuring basic functions of SNMP


2 Raisecom(config)# snmpd Enable SNMP.
By default, SNMP is enabled.
3 Raisecom(config)# snmp-server Configure the name of SNMP community and read-
community community-name { ro | write privilege.
rw }
4 Raisecom(config)# interface snmp Enter SNMP interface configuration mode.
5 Raisecom(config-snmp)# ip address Configure the IP address and subnet mask of the
ip-address [ mask-address ] SNMP interface.
By default, the IP address is 192.168.4.28 and the
subnet mask is 255.255.255.0.
6 Raisecom(config-snmp)# description (Optional) configure descriptions of the SNMP
string interface.
7 Raisecom(config-snmp)# speed { 10 | Configure the rate and duplex mode of the SNMP
100 } duplex { full- duplex | half- interface.
duplex }
3.4 Configuring Trap feature


2 Raisecom(config)# snmp trap- Configure the IP address of the SNMP Trap target server
server ip-address [ port-id ] and the ID of the interface for receiving Trap message.
By default, the ID of the interface for receiving Trap
message is 162.
3 Raisecom(config)# snmp trap-bind Configure the bound interface for sending Trap message.
{ any | snmp }
By default, the bound interface for sending Trap message
is the SNMP interface.

Raisecom
3.5 Configuring static ARP


2 Raisecom(config)# arp add ip- Configure the static ARP mapping from the IP address to
address mac-address the physical address.
By default, the system ARP table is empty.


1 Raisecom# show interface snmp Show SNMP interface configurations.
2 Raisecom# show snmp-server Show SNMP community name list.
community
3 Raisecom# show snmp trap-server Show information about the SNMP Trap target server.
4 Raisecom# show snmp-server Show statistics of SNMP.
statistics
5 Raisecom# show snmp trap-bind Show information about the bound interface for
sending Trap message.
6 Raisecom# show arp Show information about the ARP mapping table.
3.7 Maintenance
Command Description
Raisecom(config-snmp)# shutdown Shut down the current SNMP interface.

Raisecom
RCMS2903-4E1-4GE (A)Configuration Guide 4 Configuring Ethernet access
4 Configuring Ethernet access
This chapter describes Ethernet access configurations of the RCMS2903-4E1-4GE.

 Introduction
 Configuring the interface
 Configuring VLAN
 Configuring QoS
 Configuring rate limiting
 Configuring storm control
 Maintenance
 Configuration example
4.1 Introduction
4.1.1 Ethernet interface
Duplex modes
The Ethernet interface can work in the following two duplex modes:
 In half duplex mode, an interface can receive or send packets at a time.
 In full duplex mode, an interface can both receive and send packets concurrently.
Duplex mode auto-negotiation refers that the duplex mode is decided based on the automatic
negotiation between the local interface and peer interface.
Interface rate
The RCMS2903-4E1-4GE provides four 1000 Mbit/s Ethernet interfaces. The rate varies
from 10 Mbit/s to 100 Mbit/s to 1000 Mbit/s, which can be configured or automatically
negotiated.
Interface rate auto-negotiation refers that the interface rate is automatically negotiated by the
local and peer interfaces.

Raisecom
Flow control
When the received flow on the interface exceeds the processing and forwarding capability of
the device, the line will be congested. In order to decrease the packet loss rate due to the
buffer overflow, the upstream device is notified of slowing down or stopping sending data to
relieve the congestion.
Flow control can be divided into two types: back pressure flow adopted by the half duplex
Ethernet interface and the Institute of Electrical and Electronics Engineers (IEEE) 802.3x
flow control adopted by the full duplex Ethernet interface.
4.1.2 Switching interface

The switching interface is a logical interface and does not exist physically. Through the
switching interface, you can achieve data switching. The switching interface is corresponding
to the physical interface. The RCMS2903-4E1-4GE provides 5 switching interfaces. The
corresponding relationship between the switching interface and the physical interface is as
below:
 Switching interfaces 1–4: GE interfaces 1–4
 Switching interface 5: optical interface 1
4.1.3 VLAN
Virtual Local Area Network (VLAN) is a Layer 2 isolation technology that is used to partition
devices in a LAN logically instead of physically to a network segment. Therefore, multiple
distinct virtual broadcast domains are created.
VLAN entries
For the RCMS2903-4E1-4GE, each VLAN entry is corresponding to one VLAN ID. You can
configure the status and member interfaces of multiple VLAN entries at the same time.
In different network management modes, the number of the VLAN entries is different:
 In mode 1: the RCMS2903-4E1-4GE can be managed by the OPCOM3500E and
iTN2100 and supports 64 VLAN entries.
 In mode 2: the RCMS2903-4E1-4GE can be managed by the RC002 and supports 16
VLAN entries.
You can use the bit 4 of SW1 to configure the network management modes.
 Mode 1: bit 4 is configured to OFF.
 Mode 2: bit 4 is configured to ON.
VLAN modes
The RCMS2903-4E1-4GE supports 4 working modes:
 novlan: VLAN is not configured, that is, the device works in full switching mode.
 portvlan: partition VLAN based on the interface, that is, different interfaces are isolated
from each other.
 tagvlan: partition VLAN based on the VLAN ID, that is, the device works in signal Tag
mode.

Raisecom
 QinQ: double Tag mode
QinQ
QinQ encapsulates the VLAN Tag of users' private network into the VLAN Tag of the public
network and enables the packet to transmit through the public network of the Internet Service
Provider (ISP) carrying double VLAN tags. In the public network, the packet is transmitted
according to the outer VLAN Tag (public VLAN Tag) and the VLAN Tag of users' private
network is shielded.
QinQ effectively relieve the shortage of VLAN ID in the public network. At the same time,
you can plan the VLAN ID of their private network without conflicting with the VLAN ID of
the public network.
TPID
Tag Protocol Identifier (TPID) is a filed in the VLAN Tag. IEEE 802.1Q protocol defines the
value of this field as 0x8100.
Different manufactures may set different values to the TPID of the outer Tag of the QinQ
packet. To use devices provided by different manufactures compatibly, you can configure the
TPID of the outer Tag.
4.1.4 QoS
Quality of Service (QoS) can ensure you to obtain expected service levels in the following
aspects in the transmission: packet loss ratio, time delay, jittering, and bandwidth, etc.
Priority trust
The RCMS2903-4E1-4GE supports the following three priority trust modes:
 Interface-based: partition packets according to the default CoS priority and interfaces are
isolated from each other.
 CoS-based: trust the CoS priority of the VLAN packet header and partition packets
according to the CoS priority of the ingress packet Tag. For the Untagged packet, use the
default CoS priority of the interface.
 DSCP-based: trust the DSCP priority of the IP packet.
Queue mapping
Queue mapping refers to mapping packets of the same kind to the same interface queue.
The RCMS2903-4E1-4GE supports mapping CoS priority, DSCP priority, and interface
default priority to the queue. Moreover, it supports 4 interface queues.
Queue scheduling
Queue scheduling refers to extracting packet from the interface queue for transmission
according to specified policies.
The RCMS2903-4E1-4GE supports the following four QoS queue scheduling modes:

Raisecom
 Strict Priority (SP): the device strictly schedules packets in a descending order of priority.
Packets with lower priority cannot be scheduled until packets with higher priority are
scheduled.
 Weight Round Robin (WRR): on the basis of scheduling packets in a polling manner
according to the priority, the device schedules packets according to the weight of the
queue. The queue with a higher priority obtains more resources and the queue with a
lower priority obtains fewer resources to avoid the situation that the packet with a lower
priority will not be scheduled for a long time in the fixed priority scheduling.
 1SP-3WRR: The queue with the highest priority is scheduled according to the SP mode.
Other three queues are scheduled in a polling manner according to the WRR mode.
 2SP-2WRR: The two queues with the higher priority are scheduled according to the SP
mode. Other two queues are scheduled in a polling manner according to the WRR mode.
4.1.5 Storm control

When the interface receives a great deal of broadcast, unknown multicast, and unknown
unicast packets, a broadcast storm will be generated, which may lead to network congestion.
Storm control prevents the generation of broadcast storm through limiting the rate of the
broadcast packets on the interface.
4.2 Configuring the interface

Scenario
The Ethernet interface includes the GE electrical interface and GF optical interface. Through
configuring the interface, you need to make sure that parameters of interfaces on both ends
are consistent and services are transmitted normally.
Prerequisite
N/A
4.2.2 Configuring GE electrial interface

Configure the RCMS2903-4E1-4GE as below. Step 3 and Step 4 are in conflict with each
other, so you should choose only one of them during the configuration.

2 Raisecom(config)# interface ge Enter GE electrical interface configuration mode.
interface-number
3 Raisecom(config-ge/*)# autonegotiate (Optical) enable auto-negotiation on the GE
electrical interface.
By default, auto-negotiation on the GE electrical
interface is enabled.

Raisecom

4 Raisecom(config-ge/*)# speed { 10 | (Optical) configure the rate and duplex mode of the
100 | 1000 } duplex { full-duplex | GE electrical interface.
half-duplex }
By default, GE electrical interface works in auto-
negotiation mode. After auto-negotiation is
disabled, the default rate is1000 Mbit/s and the
duplex mode is full duplex mode.
5 Raisecom(config-ge/*)# flow-control Enable flow control on the GE electrical interface.
on
By default, flow control on the GE electrical
interface is enabled.
6 Raisecom(config-ge/*)# shutdown (Optical) disable the Ethernet interface.
By default, the GE electrical interface is enabled.
You can use the no shutdown command to enable
the interface.
4.2.3 Configuring GF optical interface


2 Raisecom(config)# interface fx-ge Enter GF optical interface configuration mode.
interface-number
3 Raisecom(config-fx-ge/*)# flow- Enable flow control on the GF optical interface.
control on
By default, flow control on the GF optical interface
is enabled.


1 Raisecom(config-ge/*)# show interface Show GE electrical interface configurations.
2 Raisecom(config-ge/*)# show statistic Show GE electrical interface statistics.
3 Raisecom(config-fx-ge/*)# show Show GF optical interface configurations.
interface
4 Raisecom(config-fx-ge/1)# show Show GF optical interface statistics.
statistic

Raisecom
4.3 Configuring VLAN

Scenario
VLAN can partition different users and services logically.
Prerequisite
N/A
4.3.2 Configuring VLAN modes


2 Raisecom(config)# vlan-type { novlan Configure the working mode of VLAN.
| portvlan | tagvlan | qinq }
By default, VLAN works in novlan mode.
3 Raisecom(config)# double-tagging tpid Configure the TPID of the outer Tag when VLAN
tpid works in QinQ mode.
By default, the TPID of the outer Tag is 0x9100.
4 Raisecom(config)# interface Enter switching interface configuration mode.
switchport interface-number
5 Raisecom(config-esw/*)# pvid vlan-id Configure the default VLAN ID when VLAN
works in portvlan mode.
By default, the PVID of five switching interfaces is
1.
6 Raisecom(config-esw/*)# tag-mode Configure the Tag mode on the egress direction of
{ tag | untag } the switching interface.
By default, packets on the egress direction of five
switching interfaces carry Tag. Packets on the
egress direction of other switching interfaces do not
carry Tag.
4.3.3 Configuring VLAN entries



Raisecom

2 Raisecom(config)# vlan-entry-list Create one or multiple VLAN entries and configure
entry-index { active | suspend } the status.
By default, only VLAN entry 1 is active and other
VLAN entries are in suspending status.
3 Raisecom(config)# vlan-entry-list Add the switching interface to one or multiple
entry-index port-list { port-list | VALN entries.
none }
By default, the port list of VLAN entry 1 is 1–5
and port list of other VLAN entries is none.
4 Raisecom(config)# vlan-entry entry- Configure the allowed VLAN ID for the VLAN
index vid vlan-id entry.
By default, the allowed VLAN ID is 1 only.
5 Raisecom(config)# vlan-entry entry- (Optional) add a switching interface to the VLAN
index vid vlan-id portlist port-list entry and specify its VLAN ID.
6 Raisecom(config)# vlan-entry-list (Optional) configure rate limiting of the VLAN
entry-index rate-limit rate burst entry.
By default, rate limiting of the VLAN entry is
disabled.


1 Raisecom(config-esw/*)#show esw Show configurations and status of the switching
interface.
2 Raisecom(config)# show vlan-entry- Show information about one or multiple VLAN
list entry-index entries.
4.4 Configuring QoS

Scenario
QoS provides differentiated network services according to different kinds of packets and
customers' requirements. QoS ensures that services demanding high real-time and reliability
will be transmitted high-efficiently at the first priority.

Raisecom
Prerequisite
Configure the interface-based VLAN.
4.4.2 Enabling QoS


2 Raisecom(config)# qos { enable | Enable global QoS.
disable }
4.4.3 Configuring traffic classfication


2 Raisecom(config)# qos trust { port | Configuring the mode to divide the QoS priority.
cos | dscp }
By default, QoS priority is divided based on the
interface.
4 Raisecom(config-esw/*)# qos default- Configure the default CoS priority of the switching
cos cos-value interface (for use of dividing priority based on the
interface).
By default, the value of CoS priority is 0.
4.4.4 Configuring queue mapping


2 Raisecom(config)# qos queue cos-map Configure the mapping relationship between the
{ queue-id cos-value | default } CoS priority and queue.
By default, the mapping relationship is as below:
 CoS 1 and 2: Queue 1

Raisecom
4.4.5 Configuring queue scheduling


2 Raisecom(config)# qos queue { sp | Configure the QoS scheduling mode.
wrr | lsp-3wrr | 2sp-2wrr }
By default, the QoS scheduling mode is SP.
3 Raisecom(config)# qos queue wrr Configure the weight of each queue in WRR mode.
weight-1 weight-2 weight-3 weight-4


1 Raisecom(config)# show qos Show basic information about QoS.
4.5 Configuring rate limiting

Scenario
The RCMS2903-4E1-4GE supports interface-based and VLAN-based rate limiting. You can
choose either of them based on the needs.
Prerequisite
N/A
4.5.2 Configuring interface-based rate limiting



Raisecom

3 Raisecom(config-esw/*)# rate-limit Configure rate limiting on the switching interface.
{ egress | ingress | both } rate-
value By default, rate limiting is disabled.
We do not recommend you to configure

storm control and rate limiting on the same
interface.
4.5.3 Configuring VLAN-based rate limiting


2 Raisecom(config)# vlan-entry-list Configure rate limiting for one or multiple VLAN
entry-index rate-limit rate burst entries.
By default, VLAN-based rate limiting is disabled.


1 Raisecom(config-esw/*)#show esw Show configurations and status of the switching
interface.
2 Raisecom(config)# show vlan-entry- Show rate limiting information about the VLAN entry.
list entry-index rate-limit
4.6 Configuring storm control

Scenario
When the interface receives a great deal of broadcast, unknown multicast, and unknown
unicast packets, a broadcast storm will be generated, which may lead to network congestion.
Storm control prevent the generation of broadcast storm through limiting the rate of the
broadcast packets on the interface.

Raisecom
Prerequisite
N/A
4.6.2 Configuring storm control


3 Raisecom(config-esw/*)# storm-control Configure storm control.
{ broadcast | multicast | dlf | all }
By default, storm control is disabled.
We do not recommend you to configure

storm control and rate limiting on the same
interface.
4.6.3 Configuring the rate for strom control


3 Raisecom(config-esw/*)# storm-control Configure the rate for storm control on the
rate rate switching interface.
By default, storm control is disabled. After storm
control is enabled, the default rate for storm control
is 256 Kbit/s.


1 Raisecom(config-esw/*)# show storm- Show storm control information on the switching
control interface.

Raisecom
4.7 Maintenance
Command Description
Raisecom(config-ge/*)# clear statistic Clear statistics on the GE electrical interface.
Raisecom(config-fx-ge/*)# clear Clear statistics on the GF optical interface.
statistic
4.8 Configuration example

Networking requirements
As shown in Figure 4-1, services of VLAN 100 are transmitted through Ethernet interfaces 1
and 2 of the RCMS2903-4E1-4GE and services of VLAN 200 are transmitted through
Ethernet interfaces 3 and 4 of the RCMS2903-4E1-4GE. Egress packets from switching
interfaces 1–4 do not carry Tag. Egress packets from switching interface 5 carry Tag.
Moreover, configure storm control on switching interface 1 and the rate for storm control is
256 Kbit/s.
Figure 4-1 Ethernet access networking
Configuration steps
Step 1 Configure the VLAN mode to Tag VLAN mode.
Raisecom# config
Raisecom(config)# vlan-type tagvlan
Set successfully

Raisecom
Step 2 Configure the VLAN ID of the VLAN entry 1 as 100 and add switching interfaces 1 and 2 to
the VLAN entry 1.
Raisecom(config)# vlan-entry 1 vid 100 port-list 1-2

Set successfully
Step 3 Configure the VLAN ID of the VLAN entry 2 as 200 and add switching interfaces 3 and 4 to
the VLAN entry 2.
Raisecom(config)# vlan-entry 2 vid 200 port-list 3-4

Set successfully
Step 4 Configure the PVID of switching interfaces 1 and 2 as 100 and PVID of switching interfaces
3 and 4 as 200.
Raisecom(config)# interface switchport 1

Raisecom(config-esw/1)# pvid 100
Set successfully
Raisecom(config-esw/1)# interface switchport 2
Set successfully
Set successfully
Set successfully
Step 5 Configure the Tag mode of switching interfaces 1–4 to Untag mode (taking switching
interface 1 for example), and configure the switching interface 5 to the Tag mode.

Raisecom(config-esw/1)# tag-mode untag
Set successfully
Raisecom(config-esw/5)# tag-mode tag
Set successfully
Step 6 Configure storm control on switching interface 1 and the rate for storm control is 256 Kbit/s.

Raisecom(config-esw/1)# storm-control broadcast
Set successfully

Raisecom
Raisecom(config-esw/1)# storm-control rate 256

Set successfully
Checking results
 Show configurations of VLAN entries 1 and 2.
Raisecom(config)# show vlan-entry-list 1-2

VLAN entry index: 1
VLAN active config: activated
VLAN active status: activated
VID config: 100
VID status: 100
VLAN member config: 1 2
VLAN member status: 1 2
VLAN rate limit config is: none
VLAN rate limit status is: none
VLAN burst config is: none
VLAN burst status is: none
VLAN entry index: 2

VLAN active config: activated
VLAN active status: activated
VID config: 200
VID status: 200
VLAN member config: 3 4
VLAN member status: 3 4
VLAN rate limit config is: none
VLAN rate limit status is: none
VLAN burst config is: none
VLAN burst status is: none
 Show configurations of switching interface 1.
Raisecom(config-esw/1)# show esw

Interface ID: 1
PVID config: 100
PVID status: 100
tag mode config: untag
tag mode status: untag
default cos config: 0
default cos status: 0
storm-control type config: broadcast
storm-control type status: broadcast
storm-control rate config is: 256
storm-control rate status is: 256
rate-limit egress config is: none
rate-limit ingress config is: none
rate-limit egress status is: none
rate-limit ingress status is: none

Raisecom
 Show configurations of switching interface 5.
Raisecom(config-esw/5)# show esw

Interface ID: 5
PVID config: 1
PVID status: 1
tag mode config: tag
tag mode status: tag
default cos config: 0
default cos status: 0
storm-control type config: disable
storm-control type status: disable
storm-control rate config is: 256
storm-control rate status is: 256
rate-limit egress config is: none
rate-limit ingress config is: none
rate-limit egress status is: none
rate-limit ingress status is: none

Raisecom
RCMS2903-4E1-4GE (A)Configuration Guide 5 Configuring E1 access
5 Configuring E1 access
This chapter describes E1 access configurations of the RCMS2903-4E1-4GE.

 Introduction
 Configuring the interface
 Configuring loopback
 Maintenance
5.1 Introduction
E1
E1 is one of the two hierarchies of the Plesiochronous Digital Hierarchy (PDH). It includes
features as below:
 The rate of E1 link is 2.048 Mbit/s and E1 uses Pulse Code Modulation (PCM).
 The length of E1 frame is 256 bits. It consists of 32 timeslots and each timeslot consists
of 8 bits.
 8K E1 frames are transmitted through the interface per second, so the interface rate is
2048 Kbit/s (8 K/s × 256 bit). Each timeslot consists of 8 bits in the E1 frame, so the rate
of each timeslot is 64 Kbit/s (8 K/s × 8 bit) and rate of each E1 frame is 32 × 64 Kbit/s.
Structure of E1 frame
E1 frame is in three modes: unframed, framed and multiframed.
 In an unframed E1, all 32 timeslots are used to transmit valid data.
 In a framed E1, TS0 transmits Frame Alignment Signal (FAS), CRC-4, and peer alarm
indication; other 31 timeslots transmit valid data.
 In a multiframed E1, TS0 transmits overhead; TS16 transmits Channel Associated
Signaling (CAS), multi-FAS, and multiframe peer alarm indication; those 30 timeslots
TS1–TS15 and TS17–TS31 transmit voice or data.
In an E1 channel, a timeslot consists of 8 bits while 32 timeslots compose a frame (F). A
multiframed (MF) consists of 16 frames.

Raisecom
The E1 interface of the RCMS2903-4E1-4GE has two modes: balanced and unbalanced.
Moreover, it supports transparent transmission, that is, unframed mode.
E1 loopback
Loopback detection is a frequently-used method to test and analyse interface or link problems.
The RCMS2903-4E1-4GE supports local internal loopback, external loopback, bidirectional
loopback, and remote internal loopback at the E1 side.
 Local internal loopback: signals sent by the Tx of an interface are received by the Rx of
the same interface. You can know the working status of the interface by checking the
sending and receiving of data.
 Local external loopback: the interface sends signals sent by the peer to the Rx of the peer
to form a detection loop. It is mainly used for checking the line status.
 Local bidirectional loopback: local internal loopback and local external loopback is
enabled at the same time.
 Remote internal loopback: the interface sends signals to the peer, and then the peer sends
the received signals to the local, thus forming a detection loop.
Figure 5-1 and Figure 5-2 show local bidirectional loopback and remote internal loopback.
Figure 5-1 Local bidirectional loopback
Figure 5-2 Remote internal loopback
5.2 Configuring the interface

Scenario
You can configure alarm masking for the E1 interface by CLI and the type of the E1 interface
by DIP.

Raisecom
Prerequisite
N/A
5.2.2 Configuring E1 interface


2 Raisecom(config)# interface e1 Enter E1 interface configuration mode.
interface-number
3 Raisecom(config-e1/*)# alarm-mask all Mask all alarms on the current E1 interface.
By default, alarm masking on the E1 interface is
disabled.


1 Raisecom(config-e1/*)# show interface Show configurations and status of the E1 interface.
5.3 Configuring loopback

Scenario
You can configure the loopback mode for each way of E1 on the E1 interface. The
RCMS2903-4E1-4GE supports automatical discharge, that is, loopback will be disabled when
the configured hold-time expires.
Prerequisite
N/A
5.3.2 Local loopback



Raisecom

2 Raisecom(config-e1/*)# loopback Configure local internal, external, or bidirectional
{ external | internal | bidirection } loopback at the E1 side.
[ hold-time time ]
Configure the hold-time of loopback by using the
hold-time parameter. Otherwise, loopback will not
be disabled automatically.
By default, loopback is disabled.
5.3.3 Remote loopback


2 Raisecom(config-e1/*)# loopback Configure remote internal loopback at the E1 side.
remote-internal [ hold-time time ]
Configure the hold-time of loopback by using the
hold-time parameter. Otherwise, loopback will not
be disabled automatically.
By default, loopback is disabled.
5.3.4 Configuring BERT


2 Raisecom(config-e1/*)# bert { line | Configure BERT for the E1 channel.
client }
By default, BERT is disabled.
You can enable BERT for only one E1

channel at the same time. If you want to
configure BERT for another E1 channel, you
need to disable BERT for the first E1
channel.


Raisecom

1 Raisecom(config-e1/*)# show loopback Show loopback information on the E1 interface.
2 Raisecom(config-e1/*)# show interface Show configurations and status of the E1 interface.
5.4 Maintenance
Command Description
Raisecom(config-e1/*)# clear statistic Clear statistics on the E1 interface.

Raisecom
RCMS2903-4E1-4GE (A)Configuration Guide 6 Alarm management
6 Alarm management
This chapter describes alarm management of the RCMS2903-4E1-4GE.

 Introduction
 Configuring alarm inhibition
 Configuring alarm delay
 Configuring alarm saving
 Configuring alarm auto-report
 Configuring alarm inverse reporting
 Configuring alarm monitoring
 Configuring alarm masking
 Maintenance
6.1 Introduction
Alarm means when a fault is generated on the RCMS2903-4E1-4GE or some working
condition changes, the RCMS2903-4E1-4GE will generate alarm information according to
different faults.
Alarm information is used to report some urgent and important events and must be sent to the
network administrator promptly, which provides strong support for monitoring device
operation and diagnosing faults.
Alarm information is stored in the alarm buffer. Meanwhile, if a NMS is established, the
alarm information will be sent to NMS through SNMP. The information sent to the NMS is
called Trap information.
Classification of alarm information

There are three types of alarm information according to properties of an alarm:
 Fault alarm: alarms for some hardware fault or some abnormal important functions, such
as port Down alarm
 Recovery alarm: alarms that are generated when device failure or abnormal function
returns to normal, such as port Up alarm

Raisecom
 Event alarm: prompted alarms or alarms that are generated because of failure in relating
the fault to the recovery, such as alarms generated by failing to Ping
Alarms can be divided into four types by function:
 Service quality alarm: alarms caused by service quality degradation, including
congestion, performance degradation, high resource utilization rate, and the bandwidth
reducing
 Processing error alarm: alarms caused by software or processing errors, including
software errors, memory overflow, version mismatching, and the abnormal program
aborts
 Environmental alarm: alarms caused by equipment location-related problems, including
the environment temperature, humidity, ventilation and other abnormal working
conditions
 Device alarm: alarms caused by failure of physical resources, including power, fan,
processor, clock, input/output ports and other hardware
Alarm information output

There are three alarm information output modes:
 Alarm buffer: alarm information is recorded in tabular form, including the current alarm
table and history alarm table.
– Current alarm table, recording alarm information which is not cleared, acknowledged
or restored.
– History alarm table, consisting of acknowledged and restored alarm information,
recording the cleared, auto-restored or manually acknowledged alarm information.
 Trap information: alarm information sent to NMS when the NMS is configured.
Alarms will be broadcasted according to various terminals configured by the RCMS2903-
4E1-4GE, including CLI terminal and NMS.
Related concepts
Related concepts about alarm management are displayed as follows:
 Alarm inhibition
When alarm inhibition is enabled, the RCMS2903-4E1-4GE records root alarms only without
affiliated alarms. For example, alarm A absolutely generates alarm B; when alarm inhibition
is enabled, alarm B will be inhibited, not sent to the alarm buffer, and not logged.
When alarm inhibition is enabled, the number of alarms to be reported is reduced sharply.
When alarm inhibition is disabled, the root alarms and their affiliated alarms are recorded on
the RCMS2903-4E1-4GE.
 Alarm auto-report
Auto-report refers that an alarm is reported to NMS automatically with its generation and you
do not need to initiate inquiries or synchronization.
You can set auto-report function to some alarm, some alarm source, or the specified alarm
from specified alarm source.

Raisecom
The alarm source refers to an entity that generates related alarms, such as ports,
devices, or cards.
 Alarm monitoring
Alarm monitoring is used to process alarms generated by modules:
− When alarm monitoring is enabled, the alarm module will receive alarms generated
by modules, and process them according to the configurations of the alarm module,
such as recording alarm in alarm buffer, or recording system logs, etc;
− When alarm monitoring is disabled, the alarm module will discard alarms generated
by modules without follow-up treatment. In addition, alarms will not be recorded on
You can perform the alarm monitoring function on some alarm, alarm source or specified
alarm on from specified alarm source.
 Alarm inverse reporting
Alarm inverse reporting refers that alarms reported by the device are inverse to the actual
situation. No alarms are reported when the interface is out of use; related alarms are reported
when the interface is in use. The alarm reports are cleared if the interface returns to the out-of
use status.
The RCMS2903-4E1-4GE supports interface-based alarm inverse reporting only. You can set
the alarm inverse reporting in three modes:
− Non-inverse reporting
In this mode, alarms are reported properly.
− Manual recovery reporting
In this mode, the alarms to be reported on an interface are inverse to the actual situation. For
example, recovery alarms are reported when there are actually alarms; alarms are reported
when there are no alarms.
− Automatical recovery reporting
When changing the inverse reporting to this mode, you will fail when there are no inverse
alarms and succeed when there are inverse alarms. In this mode, the alarms to be reported on
an interface are inverse to the actual situation. After alarms are eliminated, the mode changes
to the non-inverse reporting mode, and then alarms are reported normally before the mode
changes again.
 Alarm delay
Alarm delay refers that the RCMS2903-4E1-4GE will record alarms and report them to NMS
after a delay but not immediately when alarms are generated. Delays for recording and
reporting alarms are identical.
By default, the delay is 5s for both delayed recording and delayed reporting.
 Alarm saving
Alarm saving refers to how to record new alarms when the alarm buffer is full. There are two
types:
– Stop: in this mode, new alarms are discarded without being recorded.

Raisecom
– Loop: in this mode, new alarms overwrite existing alarms in a loop.

The RCMS2903-4E1-4GE can record up to 2000 alarms in the alarm table and up to 500
alarms in the historical alarm table. When the table is full of alarms, alarms are processed as
configured.
 Clearing alarms
Clear the current alarm, which means deleting current alarms from the current alarm table.
The cleared alarms will be saved to the history alarm table.
 Checking alarms
The administrator can check alarms and monitor alarm information directly on the
RCMS2903-4E1-4GE. If the RCMS2903-4E1-4GE is configured with NMS, the
administrator can monitor alarms on the NMS.
6.2 Configuring alarm inhibition

When alarm inhibition is enabled, the RCMS2903-4E1-4GE records root alarms only without
affiliated alarms. For example, alarm A absolutely generates alarm B; when alarm inhibition
is enabled, alarm B will be inhibited, not sent to the alarm buffer, and not logged.
When alarm inhibition is enabled, the number of alarms to be reported is reduced sharply.
When alarm inhibition is disabled, the root alarms and their affiliated alarms are recorded on

2 Raisecom(config# alarm Enter alarm configuration mode.
3 Raisecom(config-alarm)# alarm inhibit Enable alarm inhibition.
enable
By default, alarm inhibition is enabled on the
RCMS2903-4E1-4GE.
6.3 Configuring alarm delay

Alarm delay can be divided into the following two types:
 Alarm generation delay refers to the time interval to be delayed for the generation time
of an alarm.
 Alarm clearing delay refers to the time interval to be delayed for the clearing time of an
alarm.
2 Raisecom(config)# alarm Enter alarm configuration mode.

Raisecom

3 Raisecom(config)# alarm delay Enable alarm delay.
enable
By default, alarm delay is disabled.
4 Raisecom(config-alarm)# alarm Configure alarm generation delay. After alarm delay
active delay second is enabled, when an alarm still exists after the alarm
generation delay time, the RCMS2903-4E1-4GE will
report this alarm.
By default, alarm generation delay time is 5 seconds.
5 Raisecom(config-alarm)# alarm Configure alarm clearing delay. After alarm delay is
clear delay second enabled, the RCMS2903-4E1-4GE will check
whether the alarm has been cleared. This can avoid
mistaken reporting. If an alarm still exists within
alarm clearing delay time, the RCMS2903-4E1-4GE
will report this alarm.
By default, alarm generation delay time is 5 seconds.
6.4 Configuring alarm saving

Alarm saving refers to saving alarm data on the alarm register of a Network Element (NE). It
has two modes:
 Stop: in this mode, new alarms are discarded without being recorded.
 Loop: in this mode, new alarms overwrite existing alarms in a loop.
3 Raisecom(config-alarm)# alarm active Configure saving mode for alarms.
storage-mode { loop | stop }
By default, the saving mode for alarms is
loop.
4 Raisecom(config-alarm)# alarm auto-save Configure automatical alarm saving.
By default, automatical alarm saving is
disabled.
6.5 Configuring alarm auto-report

Alarm auto-report refers to that alarms are automatically reported to the NMS without being
queried or synchronized. Trap information is sent by the device to the NMS to report urgent
and important events (such as reboot of a managed device).

Raisecom

3 Raisecom(config-alarm)# alarm auto- Enable alarm auto-report.
report enable index index
By default, alarm auto-report is enabled.
4 Raisecom(config-alarm)# alarm auto- Enable alarm auto-report on the next-hop
report enable 0 device-id [ module_name device.
interface-number ] [ index index ]
By default, alarm auto-report on the next-hop
device is enabled.
5 Raisecom(config-alarm)# alarm auto- Enable alarm auto-report on functional modules.
report enable 0 [ module_name interface-
number ] [ index index ] By default, alarm auto-report on functional
Raisecom(config-alarm)# exit modules is enabled.
6 Raisecom# show alarm auto-report config Show alarm auto-report configurations on the
RCMS2903-4E1-4GE.
6.6 Configuring alarm inverse reporting

Alarm inverse reporting refers that alarms reported by the device are inverse to the actual
situation. No alarms are reported when the interface is out of use; related alarms are reported
when the interface is in use. The alarm reports are cleared if the interface returns to the out-of
use status.

3 Raisecom(config-alarm)# alarm inverse enable 0 Enable alarm inverse reporting on
{ all | module_name interface-number } functional modules.
4 Raisecom(config-alarm)# alarm inverse enable 0 Enable alarm inverse reporting on
device-id { all | module_name interface-number } the next-hop device.
5 Raisecom(config-alarm)# alarm inverse-mode Configure alarm inverse reporting.
{ auto | manual | none }
By default, alarm inverse reporting is
automatical reverse.
6 Raisecom(config-alarm)# end Show configurations of alarm
Raisecom# show alarm inverse config inverse reporting.

Raisecom
6.7 Configuring alarm monitoring

Alarm monitoring is used to process alarms generated by modules:
 When alarm monitoring is enabled, the alarm module will receive alarms generated by
modules, and process them according to the configurations of the alarm module, such as
recording alarm in alarm buffer, or recording system logs, etc.
 When alarm monitoring is disabled, the alarm module will discard alarms generated by
modules without follow-up treatment. In addition, alarms will not be recorded on the
RCMS2903-4E1-4GE.

3 Raisecom(config-alarm)# alarm monitor enable Enable alarm monitoring on the
index index RCMS2903-4E1-4GE.
4 Raisecom(config-alarm)# alarm monitor enable Enable alarm monitoring on the next-hop
0 device-id [ module_name interface-number ] device.
[ index index ]
5 Raisecom(config-alarm)# alarm monitor enable Enable alarm monitoring on a specified
0 [ module_name interface-number ] [ index module.
index ]
6 Raisecom# show alarm monitor config Show configurations of alarm monitoring.
6.8 Configuring alarm masking


3 Raisecom(config-alarm)# alarm-trap-disable Mask a specified alarm.
[ index index ]


Raisecom

1 Raisecom# show alarm active module_name Show information about current
alarms.
2 Raisecom# show alarm auto-report config Show configurations of alarm
auto-report.
3 Raisecom# show alarm cleared Show information about history
alarms.
4 Raisecom# show alarm config Show alarm configurations on the
RCMS2903-4E1-4GE.
5 Raisecom# show alarmindex [ module_name | index ] Show alarm index and
configurations.
6 Raisecom# show alarm inverse config Show configurations of alarm
inverse reporting.
7 Raisecom# show general-alarm Show general alarm information.
6.10 Maintenance

1 Raisecom(config-alarm)# alarm clear { all | Clear the alarm table or a specified alarm.
index index }

Raisecom
RCMS2903-4E1-4GE (A)Configuration Guide 7 Appendix
7 Appendix
This chapter describe terms and abbreviations involved in this guide, including the following
sections:
 Terms
 Acronyms and abbreviations
7.1 Terms
A
Alarm masking The NMS does not display alarms of a specified element or does not
monitor some unimportant alarms.
Automatic When the fiber of the optical interface is pulled out or when the output
Laser Shutdown power of the optical transmitter is over great, the optical interface shuts
(ALS) down the laser automatically to avoid maintenance and operation risks.
C
(Class of Classify data and attach different priorities to the data through
Service) CoS comparison of the service type filed and indicator of the data packet.
E
Error code Bits of the received and sent signals are inconsistent with each other.
F
Frame It is a data transmission unit.
H
Half duplex Perform bidirectional electronic communicate in one direction only at
same time.

Raisecom
L
Loopback A process that a signal returns to the place where it is sent. It can be
used to detect and analyze the fault that may exist in the ring network.
M
Multiplexing It is used to adapt multiple Lower-order Path (LP) signals to a HP or
multiple HP signals to a multiplexing section.
Multiplexer The device integrates multiple tributary channels to several bearer
channels.
T
Timeslot Time is divided into periodical frames. Each frame is divided into
multiple timeslots. Each timeslot is a communication channel which
can be assigned to a user.
V
VLAN is a protocol proposed to solve broadcast and security issues for
Virtual Local
Ethernet. It divides devices in a LAN into different segment logically
Area Network
rather than physically, thus implementing virtual work groups which
(VLAN)
are based on Layer 2 isolation and do not affect each other.
7.2 Acronyms and abbreviations

A
ALS Automatic Laser Shutdown
C
CAS Channel Associated Signaling
CRC Cyclic Redundancy Check
F
FAS Frame Alignment Signal
FTP File Transfer Protocol
G

Raisecom
GE Gigabit Ethernet
L
LOF Loss of Frame
LOS Loss of Signal
P
PDH Plesiochronous Digital Hierarchy
Q
QoS Quality of Service
S
SFP Small Form-factor Pluggable
T
TFTP Trivial File Transfer Protocol
TPID Tag Protocol Identifier
V
VLAN Virtual LAN

Address: Building 2, No. 28, Shangdi 6th Street, Haidian District, Beijing, P.R.China.
Postal code: 100085 Tel: +86-10-82883305
Fax: 8610-82883056 http://www.raisecom.com Email: export@raisecom.com

RCMS2903-4E1-4GE (A) Configuration Guide (Rel - 02)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RCMS2903-4E1-4GE (A) Configuration Guide (Rel - 02)

Uploaded by

Copyright:

Available Formats

www.raisecom.

is the trademark of Raisecom Technology Co., Ltd.

Product name Hardware version Software version

Indicates a potentially hazardous situation that, if not avoided,

Raisecom Technology Co., Ltd. i

Raisecom Technology Co., Ltd. ii

 Added alarm management.

Raisecom Technology Co., Ltd. iii

1 Basic configurations ..................................................................................................................... 1

Raisecom Technology Co., Ltd. iv

1.8.6 Checking the CPU ulilization ratio ....................................................................................................... 15

2 System management ................................................................................................................... 16

3 Network management ................................................................................................................ 25

4 Configuring Ethernet access ..................................................................................................... 28

Raisecom Technology Co., Ltd. v

4.3.3 Configuring VLAN entries ................................................................................................................... 33

5 Configuring E1 access ................................................................................................................ 43

Raisecom Technology Co., Ltd. vi

6.7 Configuring alarm monitoring........................................................................................................................ 54

Raisecom Technology Co., Ltd. vii

Figure 1-1 Login connection through the Console interface .................................................................................. 7

Figure 1-2 COM1 properties .................................................................................................................................. 8

Figure 2-1 Backing up or upgrading files............................................................................................................. 20

Figure 4-1 Ethernet access networking ................................................................................................................ 39

Figure 5-1 Local bidirectional loopback .............................................................................................................. 44

Figure 5-2 Remote internal loopback ................................................................................................................... 44

Raisecom Technology Co., Ltd. viii

Table 1-1 List of File Types.................................................................................................................................. 11

Raisecom Technology Co., Ltd. ix

This chapter describes the basic configurations of the RCMS2903-4E1-4GE.

1.1.2 Command line modes

Raisecom Technology Co., Ltd. 1

Mode Description Access methods Identification

Raisecom Technology Co., Ltd. 2

Mode Description Access methods Identification

only, display prefix at first, then click Tab to check words

Raisecom Technology Co., Ltd. 3

1.1.4 Seeking help

Raisecom Technology Co., Ltd. 4

Raisecom(config)# show in?

Raisecom Technology Co., Ltd. 5

Error prompt messages

1.2 Basic command

Raisecom Technology Co., Ltd. 6

1.2.2 Terminal operation command

1.2.3 Sysyem operation command

1.3 Accessing the device

Figure 1-1 Login connection through the Console interface

Raisecom Technology Co., Ltd. 7

Figure 1-2 COM1 properties

Raisecom Technology Co., Ltd. 8

1.4 Managing users

Step Command Description

1.4.2 Checking configurations

Step Command Description

Raisecom Technology Co., Ltd. 9

1.5 Managing log

1.5.2 Enable log management

Step Command Description

1.5.3 Checking configurations

No. Command Description

1.6 Managing files

Raisecom Technology Co., Ltd. 10