ISCOM Series Switch EMS User Manual 070809

www.raisecom.com

ISCOM Series Switch EMS User Manual RC-A553-V50-070809-EN

Legal Notices

Raisecom Technology Co., Ltd makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Raisecom Technology Co., Ltd shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.

Warranty.

A copy of the specific warranty terms applicable to your Raisecom product and replacement parts can be obtained from Service Office.

Restricted Rights Legend.

All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without the prior written consent of Raisecom Technology Co., Ltd. The information contained in this document is subject to change without notice.

Copyright Notices.

Copyright ©2007 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.

Trademark Notices

is the trademark of Raisecom Technology Co., Ltd.

Java™ is a U.S. trademark of Sun Microsystems, Inc.

Microsoft® is a U.S. registered trademark of Microsoft Corporation.

Windows NT® is a U.S. registered trademark of Microsoft Corporation.

Windows® 2000 is a U.S. registered trademark of Microsoft Corporation.

Windows® XP is a U.S. registered trademark of Microsoft Corporation.

Windows® and MS Windows® are U.S. registered trademarks of

Microsoft Corporation.

Contact Information

Technical Assistance Center

The Raisecom TAC is available to all customers who need technical assistance with a Raisecom product, technology, or, solution. You can communicate with us through the following methods:

Address: 2nd Floor, South Building of Rainbow Plaza, No.11 Shangdi Information Road,

Haidian District, Beijing 100085

Tel: +86-10-82883305

Fax: +86-10-82883056

World Wide Web

You can access the most current Raisecom product information on the World Wide Web at the following URL:

http://www.raisecom.com

Feedback

Comments and questions about how the ISCOM series switch EMS works are welcomed. Please review the FAQ in the related manual, and if your question is not covered, send email by using the following web page:

http://www.raisecom.com/en/xcontactus/contactus.htm.

If you have comments on the EMS system specification, instead of the web page above, please send comments to:

[email protected]

We hope to hear from you!

CONTENTS Chapter 1 Overview ------------------------------------------------------------------------------------- 1

1.1 Overview ------------------------------------------------------------------------------------------------------------------------1 1.2 Compliance --------------------------------------------------------------------------------------------------------------------1 1.3 Launch the view of the EMS ---------------------------------------------------------------------------------------------2

1.3.1 Launch the view of switch management --------------------------------------------------------------------------------------------- 2 1.3.2 Launch the view for card management----------------------------------------------------------------------------------------------- 4

1.4 Network topology list-------------------------------------------------------------------------------------------------------6 1.5 Configuration panel---------------------------------------------------------------------------------------------------------8

Chapter 2 Configuration and Monitoring Operations ---------------------------------------- 9

2.1 Port settings-------------------------------------------------------------------------------------------------------------------9 2.2 Switch configuration -------------------------------------------------------------------------------------------------------9 2.3 Cluster -------------------------------------------------------------------------------------------------------------------------13 2.4 OAM protocol ---------------------------------------------------------------------------------------------------------------16 2.5 SNMP parameters----------------------------------------------------------------------------------------------------------17 2.6 Performance-----------------------------------------------------------------------------------------------------------------19 2.7 Remote card configuration ---------------------------------------------------------------------------------------------22

Chapter 3 Operation and Maintenance-----------------------------------------------------------23

3.1 Device system information ---------------------------------------------------------------------------------------------23 3.2 Save current configuration ---------------------------------------------------------------------------------------------23 3.3 Erase the configuration file --------------------------------------------------------------------------------------------23 3.4 Reboot the system --------------------------------------------------------------------------------------------------------24 3.5 Set the trap target address ---------------------------------------------------------------------------------------------24 3.6 Upgrade/backup file ------------------------------------------------------------------------------------------------------25

Chapter 4 Alarm and Event Management -------------------------------------------------------28

4.1 View current alarm information ---------------------------------------------------------------------------------------28 4.2 View historical alarm information ------------------------------------------------------------------------------------31

Appendix A Alarm Type -------------------------------------------------------------------------------34

Preface

About This Manual

This manual is for ISCOM series switches EMS with version V5.0.

Who Should Read This Manual

This manual is a valuable reference for sales and marketing staff, after service staff and telecommunication network designers. For those who want to have an overview of the features, applications, structure and specifications of ISCOM series switches, this is also a recommended document.

Relevant Manual

《Raisecom NView System User Manual》

《Raisecom Nview System Installation and Deployment Manual》

《Raisecom Switches Software Command Reference》

《Raisecom Switches Software Configuration Guide》

Organization

This manual is an introduction of the main functions of ISCOM series switches EMS. To have a quick grasp of the using of the EMS of ISCOM series switches, please read this manual carefully. The manual is composed of the following chapters

Chapter 1 Overview

This chapter briefly introduces the standards ISCOM series switches are compliant to, and the basic function of the EMS of ISCOM series switches.

Chapter 2 Configuration and Monitoring Operations

This chapter mainly introduces the configuration and monitoring operations of the devices.

Chapter 3 Operation and Maintenance

This chapter focuses on the running and maintaining operation of the system.

Chapter 4 Alarm and Event Management

This chapter shows the way of viewing current alarms and historical alarms of the system.

Appendix A Alarm Type

This part lists and describes the types of alarms the EMS is in support of.

www.raisecom.com User Manual

1

Chapter 1 Overview

This chapter briefly introduces the relevant MIB standards ISCOM series switches are compliant to, the features of the EMS, and the interface style of the EMS.

1.1 Overview

ISCOM series switches EMS adopts GUI device management interface, enables users to manage the device through a management interface identical to the outline of the device, reflects the factual status of the device, and provides excellent device monitoring and maintenance function. In the main interface of the ISCOM series switches EMS, users can obtain the real-time running status of device by renewing the device panel information and port status information. The configuration and real-time monitoring operations of the device can be realized through the function menu of the EMS.

Installing the NView NNM platform and ISCOM series switches EMS, users can monitor and control all ISCOM series switches.

1.2 Compliance

ISCOM series switch products of Raisecom strictly comply with the following standards as well as ITU-T, IEEE, IETF and related standards from other international telecommunications standardization organizations:

IEEE 802.1Q Virtual LANs IEEE 802.1P The bridging of service types in Ethernet and dynamic multicast filtering

service. IEEE 802.3 CSMA/CD Media access and physical layer explanation.

The MIB standards that ISCOM series switches are compliant to:

EtherLike-MIB RFC1213-MIB RMON-MIB BRIDGE-MIB P-BRIDGE-MIB BRIDGE-MIB Q-BRIDGE-MIB IF-MIB RAISECOM-BASE-MIB RAISECOM-SYSTEM-MIB RAISECOM-COMMON-MANAGEMENT-MIB RAISECOM-ACL-MIB RAISECOM-SYSLOG-SERVICE-MIB RAISECOM-RCMP-MIB RAISECOM-TOPODISCOVERY-MIB RAISECOM-SCHEDULE-MIB RAISECOM-EXTOAM-MIB RAISECOM-EXTEND-OAM-UPGRADE-MIB RAISECOM-REMOTE-MANAGEMENT-LOCAL-MIB RAISECOM-OPTICAL-MONITOR-MIB


2

RAISECOM-VCT-MIB SWITCH-SYSTEM-MIB SWITCH-RATELIMIT-MIB SWITCH-MACCONFIG-MIB SWITCH-PORTMIRROR-MIB RAISECOM-QOS-MIB SWITCH-TRUNK-MIB SWITCH-PORTSTATISTIC-MIB SWITCH-SNTP-MIB SWITCH-RSTP-MIB SWITCH-SNMP-MIB SWITCH-IGMPSNOOP-MIB DHCP-SERVER-MIB DHCP-RELAY-MIB SWITCH-FILTER-MIB SWITCH-L3FILTER-MIB SWITCH-L3-MIB RAISECOM-RIP-MIB RAISECOM-OSPF-MIB SWITCH-VLAN-MIB SWITCH-IFEXTEND-MIB SWITCH-MVR-MIB DOT3-OAM-MIB SNMP-FRAMEWORK-MIB SNMP-MPD-MIB SNMP-TARGET-MIB SNMP-NOTIFICATION-MIB SNMP-PROXY-MIB SNMP-VIEW-BASED-ACM-MIB

1.3 Launch the view of the EMS

1.3.1 Launch the view of switch management Launch from the topology view: select the device node to be managed on the topology view

of the NView NNM system, right-click on the selected node and click [Device View] on the shortcut menu or double-click the selected node directly to launch the view of the EMS (see Figure 1-1).


3

Figure 1-1 Launch the switch device view from the topology view of the NView NNM system

Launch from the topology list: select the device node to be managed on the topology list on the left of the main view of NView NNM system, right-click on the selected node and click [Device View] on the shortcut list or double-click the selected node directly to launch the view of the EMS (see Figure 1-2).

Figure 1-2 Launch the switch device view from the topology list of NView NNM system.

Device Node

Topology View

Topology List


4

The launched switch EMS view should be as is shown in Figure 1-3.

Figure 1-3 The main view of the EMS for switches

1.3.2 Launch the view for card management Launch from the topology view: select the card node to be managed on the topology view

(device sub graph) of the NView NNM system, right-click the node and click [Card View] on the shortcut menu, or double-click the selected node directly to launch the card configuration view (see Figure 1-4).

The main menu of the EMS

Device panel

Interfaces and status indicators

Current alarm list


5

Figure 1-4 Launch the configuration view of card from the topology view

Launch from the topology list: select the card node to be managed on the topology list of the NView NNM system, right-click on the selected node and click [Card View] on the shortcut menu, or double-click the selected node directly to launch the card configuration view (see Figure 1-5).

Figure 1-5 Launch the card configuration view from the topology list


6

The launched card management view should be as is shown in Figure 1-6.

Figure 1-6 The main view for card management

1.4 Network topology list

The network topology list is composed of network nodes. All shortcuts of the network element node and its connected remote cards will be listed under the node. Users can launch EMS view and remote card configuration view directly from the topology list, and can also execute service related commands from the node on the topology list.

Card panel

Interface and status indicator Configuration panel


7

Figure 1-7 The topology list

The table below shows the description of the icons on the topology list and function of the buttons on the toolbar.

Icon or button Title Description

Display device

nodes Display all network element nodes

Unfold Unfold the topology list

Fold Fold the topology list

Refresh the

network topology Refresh the network topology

Search Input the keywords for searching and search

for matching items in the network topology

Network element node icon

Right-click on the icon, a shortcut menu will appear, on which users can launch operations like “Open Subgraph”, “Locate in Topo”, “Add Device”, and etc. Double-click on the icon, the Agent module configuration window for the device will open up.

Chassis node icon Right-click on the icon, a shortcut menu will appear, on which users can execute

Toolbar

Search box

Shortcut

Remote card

Network element node


8

operations like “Topology Management”, “Alarm Management”, “Chassis View”, and etc. The chassis view can be opened up by double-clicking on the icon.

Remote card node icon

Right-click on the icon, a shortcut menu will appear, on which users can execute operations like “Topology Management”, “Alarm Management”, “Card Configuration”, and etc. The interface for card configuration can be opened up by double-clicking on the icon.

1.5 Configuration panel

Switch configuration panel: click a function menu button on the main view of the switch EMS, all configuring and monitoring commands relevant to the selected function menu button will be shown in the configuration panel.

Card configuration panel: select a card node on the topology view or topology list, basic information and relevant configuring and monitoring commands corresponding to the selected node will be shown in the configuration panel.


9

Chapter 2 Configuration and Monitoring Operations

2.1 Port settings

Click [Port\Port Settings] on the menu of the main view of the switch EMS to pop up the “Port Settings” dialog box. Users can configure the most commonly-used functions of the port, including administrative status, duplex/speed, loopback detection, flow control, and etc., in the “Port Settings” dialog box. Different models of switches have different configurable parameters in this window. Take ISCOM2828F as example, its “Port Settings” dialog box is shown in Figure 2-1.

Figure 2-1 “Port Settings” dialog box

2.2 Switch configuration

Click [Device] on the menu of the main interface of the switch EMS, a drop-down menu from which users can configure switch relevant services and protocols will appear. Clicking a menu item, the dialog box for the configuration of the corresponding function will pop up. The switch configuration items on the menu includes: “RFC1213 System Group”, “System Time”, “Switch Info.”, “Device Setting”, “Flooding Control”, “VLAN configuration”, “ARP configuration”, “IP addresses configuration”, “STP configuration”, “DHCP configuration”, “RMON configuration”, “Trunk configuration”, “Rate Limit”, “Access Control List”, “Port Mirroring”, “IGMP Snooping”, “MVR configuration”, “IGMP Filter configuration”, “QoS configuration”, “SNTP Client”, “SysLog configuration”, User configuration, “KeepAlive configuration”, and etc. The items on the menu changes as the switch model under management changes. We take VLAN configuration as an


10

example to explain the VLAN configuration process of a switch.

Set the TPID of the outer Tag: Some ISCOM series switches are in support of Q-in-Q function. Users can specify the global outer VLAN ID by setting the TPID of the outer Tag. Open up the “VLAN” dialog box for VLAN configuration by clicking the corresponding menu item and enter the TPID (range: 0x0~0xFFFF), click <Save> and the network management system will save the specified TPID on the device. See Figure 2-2.

Figure 2-2 Set the TPID for outer Tag

Add a VLAN: Click the button <VLAN Static Table> on the top of the “VLAN” dialog box and the “VLAN Static Table” page will turn up. Click <Add> and input the VLAN ID and VLAN Name (see Figure 2-3), then click <Apply> to add the VLAN to the device.


11

Figure 2-3 Add a VLAN

Modify a VLAN: Select the VLAN whose parameters are to be modified on the “VLAN Static Table” page, and click <Modify>, a “Modify” dialog box will pop up (see Figure 2-4). Input the parameters to be modified (for example: modify the “Active Status” from “Suspend” to “Active”), and click <Apply>, the modification will be saved on to the device.


12

Figure 2-4 Modify the parameters of a VLAN

Delete a VLAN: Select the VLAN to be deleted on the “VLAN Static Table” page and click <Delete>, the specified VLAN will be deleted from the device.

Figure 2-5 Delete a VLAN


13

Set Port VLAN information: Turn on the “Port VLAN Table” page by clicking the corresponding button on the top of the “VLAN” dialog box and select a port to be modified. Click <Modify>, a “Modify” dialog box will pop up (see Figure 2-6). Input the parameters to be modified in the dialog box (for example: modify the “Port Access VLAN ID” from “1” to “3”), and click <Apply>, the modification will be saved to the device.

Figure 2-6 Set Port VLAN information

2.3 Cluster

Click [Cluster] on the menu on the main interface of the switch EMS, a drop-down menu from which users can configure services and protocols related to switch cluster will appear. Click a menu item, the dialog box for the corresponding function will pop up. The configuration of switch cluster includes: cluster management, neighbor discovery and topology discovery.

The cluster management function provided by Raisecom enables network administrator to manage over multiple switches through the public network IP address of a manager switch. The manager switch is a commander, while switches under its management are member devices. Generally, a member device has no IP address and its management and maintenance are realized through the manager device. A typical application is shown in Figure 2-7.


14

Figure 2-7 Cluster management

Cluster management mainly includes three protocols: Raisecom Neighbor Discover Protocol (RNDP), Raisecom Topology Discover Protocol (RTDP) and Raisecom Cluster Management Protocol (RCMP). RNDP is in charge of neighbor discovery and data collection, RTDP collects and manages the topology information of the whole network, while RCMP completes configuration operations on cluster members like adding, activating and deleting. Both RTDP and RCMP work at VLAN 2. Hence, if a device that does not support Raisecom’s cluster management function exists between two devices with cluster management function, relevant configuration on VLAN 2 is needed to have the communication of RTDP and RCMP unblocked. Different switches have different roles in a cluster according to their status and functions. Users can specify the role of a switch through configuration. The device roles in a cluster are commander device, member device and candidate device.

Commander device: The commander device has a public network IP address. It provides the management interface for all switches in the cluster. The commander device manages member devices via command redirection. At first, users send management command to the commander device via public network. If the commander device recognizes that the command is sent to a member device for execution, it will redirect the command to the member device. The commander device has the ability to detect neighbor information, collect topology information of the whole network, manage the cluster, maintain the status of the cluster and support various types of agent.

Member device: In general, a member device does not have an IP address. Users manage member devices using the command redirection function of the commander device. A member device has the ability to detect neighbor information, accept the management of the commander device, execute the commands forwarded by agents, and report fault and log. When a member device is activated, users can manage the device directly through network


15

management device or via Telnet from the commander device. Candidate device: A candidate device is not a member of any cluster, however, it possesses

cluster function and is able to become a member device in a cluster.

A cluster must have a commander device. After the commander device has been specified, the commander device will detect and confirm candidate devices via RNDP and RTDP.

A candidate device will become a member device after it is added to a cluster. A member device can be managed via cluster management function only when it is activated. Users can either activate the switch manually or activate it by configuring auto-activate function on the switch.

Figure 2-8 Cluster member table

Figure 2-9 RTDP port discovery table


16

Figure 2-10 RTDP device discovery table

2.4 OAM protocol

Click [OAM] on the main menu of the main interface of the switch EMS, a drop-down menu from which users can configure OAM relevant services and protocols will appear. Users can open up the dialog box for an operation by clicking the corresponding item on the menu. The menu items includes: “OAM Table”, “OAM Peer Table”, “OAM Loopback Table”, “OAM Stats Table”, “OAM Log Table”, “OAM Event Log Table”, “Remote Extend OAM Trap”, “Remote Invariable Info Table”, “Remote Environment Table”, “Remote System Config Table”, “Remote Community Table”, “Remote IP Subnet Table”, “Remote Port Table”, “Remote Port Stats Table”, “Remote Device SFP Table”, “Remote Device Q-in-Q Table”, “Send Configure Frame Table”, “Remote Inside Loopback Table”, “Remote Device VCT Table”, “Extend OAM Statistics Table”, “Extend OAM Status Table”, “Extend OAM Notification Enable”, “Extend OAM Upgrade/Backup Table”, and “Extend OAM Upgrade/Backup Status Table”.

According to the factual need of carrier’s network, the management of network is generally classified into three groups: Operation, Administration and Maintenance, known as OAM. Operation completes the analysis, prediction, layout and configuration of the network and network service, while Maintenance focuses on the testing and fault management of the network and network service. ITU-T defines the OAM function as: 1) monitor the network performance, generate maintenance information and valuate the stability of the network according to the above information; 2) detect network fault periodically and generate maintenance information and alarm information; 3) guarantee the proper operation of the network by transferring or switching to other entities and bypassing the disabled entity; 4) send fault information to the commander entity.

ISCOM series switches realize the OAM function defined by IEEE 802.3ah and the Extend OAM function defined by Raisecom. Take “OAM Table” as an example, the configuration process of the function corresponding to the menu item is shown below.

Click [OAM\OAM Table] on the menu and an “OAM Table” dialog box will pop up. Select the port whose parameters are to be modified in the dialog box and click <Modify>, a “Modify” dialog


17

box will pop up (see Figure 2-11). Input the parameters to be modified (for example: modify the “OAM Administration States” from “Enabled” to “Disabled”), and click <Apply> to save the modification on to the device.

Figure 2-11 OAM configuration table

2.5 SNMP parameters

Click [SNMP Parameters] on the menu on the main interface of the switch EMS, a drop-down menu from which users can configure SNMP relevant parameters. The dialog box for a function can be opened by clicking the corresponding menu item. The SNMP parameters include: “SNMP Engine ID”, “USM Statistics”, “USM User Table”, “SNMP Community”, “VACM Security to Group Table”, “VACM Access Table”, “VACM View Tree Family”, and “SNMP Target Address Table”.

Simple Network Management Protocol (SNMP) is a widely-applied network management protocol. ISCOM series switch EMS realizes the management over ISCOM series switches via SNMP.

Access control is an important part of SNMP. We will introduce the access control configuration function in the following section. At present, two access control models are commonly used.

Community-based access control

SNMP Agent brings forth the conception of community to protect itself and its managed MIB from unauthorized accesses. In a community, the management station must use the name of the community when executing “get” and “set” operations on all agents, otherwise the request will not be accepted. When SNMP v1 and SNMP v2 adopt community name authentication, the SNMP messages with community name that the device can not recognize will be discarded. The community names are strings used to mark and differentiate different SNMP communities. SNMP community can have Read-Only authority or Read-Write authority. Communities with Read-Only authority can only query on device information, while those with Read-Write authority can not only query device


18

information but also configure the device.

Click [SNMP Parameters\SNMP Community] on the menu of the main interface of the switch EMS, a “SNMP Community” dialog box will pop up. Select the community to be modified and click <Modify>, a <Modify> dialog box will pop up (see Figure 2-12). Input the parameters to be modified (for example: set the “Community Name” to “read”, set the “View Name” to “internet” and set the “AccessControl” to “ReadOnly”), and click <Apply>, the configuration will be saved on to the device.

Figure 2-12 SNMP community table

User-based access control

SNMP v3 adopts User-based Security Model (USM). USM brings forth the conception of group. One or several users correspond to one access group. Every access group has its pre-defined read view, write view and notify view. Users in the access group possess the read, write or notify authority in the corresponding view. Users that send “Get” and “Set” requests must be a member of an access group that possesses the corresponding authority, otherwise the requests will not be accepted.


19

Figure 2-13 SNMP v3 access control model

Click [SNMP Parameters\USM User Table] on the menu of the main interface of the switch EMS, the interface for configuring USM user will turn up. Users can add, modify or delete USM users in the interface. After adding a new USM user, users can assign it to an access group.

2.6 Performance

Click [Performance] on the menu in the main interface of the switch EMS, a drop-down menu from which users can launch the operation of viewing the performance of the switch will appear. Click a menu item and the dialog box of the corresponding performance will pop up, users can view various performance parameters. The performance of the switch includes: CPU utilization and interface performance.

CPU Utilization: Users can view the CPU utilization in one second and CPU utilization in one minute of the switch here (see Figure 2-14 and 2-15).


20

Figure 2-14 CPU utilization in one second

Figure 2-15 CPU utilization in one minute


21

Interface performance: Users can view performance parameters of port in the switch interface table here. Select a parameter in the table shown in the figure below, and click <Chart>, the performance graph of the selected parameter will be displayed (see Figure 2-16 and 2-17).

Figure 2-16 Select a performance parameter

Figure 2-17 Real-time performance graph


22

2.7 Remote card configuration

Launch the card configuration interface from the topology view or topology list, users can view and configure the information of remote card managed by the switch via OAM. Users can select to open a function page to show basic information and configuring and monitoring commands of the card in the configuration interface. The information and commands include: basic information, port information, extend information, environment information, IP address, SNMP community, port statistic information, system commands, and etc. The function page and configurable parameters are different for different cards.


23

Chapter 3 Operation and Maintenance

3.1 Device system information

Click [Device\RFC1213 System Group] on the menu in the main interface of the switch EMS, a “RFC1213 System Group” dialog box will pop up to show the relevant system information of the RFC1213 system group, including basic information like system name, system OID, and etc.

Figure 3-1 Device system information

3.2 Save current configuration

Clicking [Command\Write] on the menu in the main interface of the switch EMS, users can save the current configuration to the “startup_config.conf” file in the Flash of the switch. The configuration will be uploaded on to the device when the switch starts.

Figure 3-2 Save current configuraiton

3.3 Erase the configuration file

Users can delete the “startup_config.conf” file from the Flash of the switch by clicking [Device\Erase] on the menu in the main interface of the switch EMS. The switch will restore to the initial status after the operation.


24

Figure 3-3 Erase the configuration file

3.4 Reboot the system

To reboot the device, please click [Device\Reboot] on the menu in the main interface of the switch EMS.

Figure 3-4 Reboot the system

3.5 Set the trap target address

Click [SNMP Parameters\SNMP Target Address Table] on the menu of the main interface of the switch EMS, the interface for setting up SNMP target address will pop up. The trap target address of the switch can be set up by adding list record.

The trap types are:

ospf: OSPFtrap

snmp: SNMPtrap

rmon: RMONtrap

interface: Interface trap

config: Config trap

bridge: Bridge trap


25

Figure 3-5 Set up trap target address

3.6 Upgrade/backup file

ISCOM series switches are in support of the upgrading and backing up of the “system-boot” file, “startup-config” file and etc. of the local device and the remote device managed via OAM. Users can upgrade/backup the files via FTP or TFTP.

The upgrading/backing up of the local device: Click [Command\Online Upgrade/Backup] on the menu of the main interface of the switch EMS, an “Online Upgrade/Backup” dialog box will pop up. Users can upgrade or back up a specified file by adding corresponding list record.


26

Figure 3-6 Upgrade/Back up the local device

Note: The “bootstrap” file can not be backed up. When upgrading “system-boot”,

“startup-config” or “bootstrap” file, the file will only be valid after the reboot of the switch. The “Local File Name” is used to specify the source file name when backing up. The file is from the Flash of the switch. When upgrading, the “Local File Name” is used to specify the target storing type and file name. If the file name is headed by “mem:\”(select “Memory” in the “Add” dialog box), it is saved as memory file, otherwise, the file is saved to the Flash. If the “Local File Name” is not specified, the file will be read in default ways, that is when backing up the “startup-config”/“system-boot” file, the file being backed up is “startup-config.conf”/“system-boot.Z”; when upgrading “startup-config”/“systemj-boot” file, the file being saved is “startup-config.conf”/“system-boot.Z”. The data in the “Online Upgrade/Backup table” will be deleted automatically after 5 seconds from the completion of the upgrading and backing up operation.

The upgrading/backing up of the remote device: Click [OAM\Extend OAM Upgrade/Backup Table] on the menu of the main interface of the switch EMS, an “Extend OAM Upgrade/Backup” dialog box will pop up. By adding corresponding list records, users can obtain upgrade file from the Flash or memory of the local device (the device that manages the remote device via OAM). In the upgrading process, the upgrade file will be placed into the Flash or memory of the local device through the “Online Upgrade/Backup Table” at first, then the system will execute the upgrade operation. Similarly, in the backing up process, the backup file must be placed in the Flash or memory of the local device before executing the backup operation via the “Online Upgrade/Backup Table”.


27

Figure 3-7 The upgrading/backing up of the remote device

Note: The “bootstrap” file and “fpga” file can not be backed up. When upgrading “system-boot”,

“startup-config”, “bootstrap” or “fpga” file, the file will only be valid after the reboot of the switch. The “File Name” is used to specify the target storing type and file name when backing up file. If the file name is headed by “mem:\”(select “Memory” in the “Add” dialog box), it is saved as memory file, otherwise, the file is saved to the Flash. The “File Name” is used to specify the source type and file name of the source file when upgrading file. If the file name is headed by “mem:\”(select “Memory” in the “Add” dialog box), its source is memory file, otherwise, the file is from the Flash. If the “File Name” is not specified, source/target files are device default configuration files. The “Remote Devices to be Upgraded or Backed Up” adopts hyphen “-” to separate the number of remote devices, the ifIndex of the local port the remote device connected to, and remote device ID list. If the ifIndex of the local port is 0, the remote device ID will be the ifIndex value of the remote device connected to them. If the ifIndix of the remote port is not 0, the remote device ID will be the ifIndex of the remote device minus 100000. One table item in the remote device ID list corresponds to one remote device. At most, 62 devices can be supported. For example, a RC551-GE is connected to the port 27 of ISCOM2828F, then the item “Remote Devices to be Upgraded or Backed Up” should be 1-0-27 when upgrading/backing up the remote RC551-GE. The data in the “Extend OAM Upgrade/Backup Table” will be deleted automatically after 5 seconds from the completion of the upgrading and backing up operation.


28

Chapter 4 Alarm and Event Management

4.1 View current alarm information

Open the current alarm management interface

Select a network element node on the topology list, right-click on the selected node and click [Alarm\View Alarm] on the shortcut menu, a “View Event” dialog box will pop up. Click <Current Alarm> on the left to turn on the “Current Alarm” page (see Figure 4-1).

Figure 4-1 “Current Alarm” page

Acknowledge alarm record

Select an alarm record whose “Alarm Status” is “Newcome” on the alarm list, and click [Acknowledge] on the right-click menu of the selected record.

Clear current alarm record

Select one or multiple records on the alarm list and click [Clear] on the right-click menu of the selected records.

Export current alarm record

Click an item on the sub menu of [Export] on the right-click menu of the alarm list according to need. The records can be exported as a text file or an Excel file.

View detailed information of alarm

Right-click on a row of record on the alarm list and click [Properties] on the shortcut menu, a “Properties” dialog box will pop up (see Figure 4-2).


29

Figure 4-2 The “Properties” dialog box for a current alarm

Filter current alarm

Select a network element node on the topology list and click [Alarm\Alarm Filter] on the right-click menu of the selected node, an “Alarm Filter Rules” dialog box will pop up (see Figure 4-3).


30

Figure 4-3 Alarm Filter

Take add a device filter rule as an example: Click <Add Filter Rule for Device> on the left to open up the corresponding page in the “Alarm Filter Rules” dialog box. Select the device to be filtered and the alarm types on the selected device to be filtered (filter all alarm types by default). See Figure 4-4.


31

Figure 4-4 Set up alarm filter rules

4.2 View historical alarm information

Open up the historical alarm management interface

Select a network element node on the topology list and click [Alarm\View Alarms] on the right-click menu of the selected node. Click <Historical Alarm> on the left to turn up the “Historical Alarm” page (see Figure 4-5).


32

Figure 4-5 “Historical Alarm” page

Clear historical alarm record

Select one or multiple records on the alarm list and click [Clear] on the right-click menu of the selected records.

Export historical alarm record

Click an item on the sub menu of [Export] on the right-click menu of the alarm list according to need. The records can be exported as a text file or an Excel file.

View detailed information of alarm

Right-click on a row of record on the alarm list and click [Properties] on the shortcut menu, a “Properties” dialog box will pop up (see Figure 4-6).


33

Figure 4-6 “Properties” dialog box for historical alarms


34

Appendix A Alarm Type

Serial Number Alarm Type Alarm Source

1 Cold Start NE

2 Link Up Port

3 Link Down Port

4 Authentication Failure NE

5 Config Operation NE

6 Online Upgrade/Backup NE

7 RTDP Topology Change NE

8 STP New Root NE

9 Topology Change NE

10 RMON Falling NE

11 RMON Rising NE

12 KeepAlive NE

13 Connector Insert Port

14 Connector Remove Port

15 Loopback Port Link Up Port

16 Loopback Port Link Down Port

17 OAM Discovery Trap Port

18 OAM Peer Lost Trap Port

19 Remote Link Up Remote

20 Remote Link Down Remote

21 Extend OAM Upgrade/Backup Complete NE

22 Remote ErroredSymbloEvent Remote


35

23 Remote ErroredFramePeriodEvent Remote

24 Remote ErroredFrameEvent Remote

25 Remote ErroredFrameSecondsEvent Remote

26 Remote DyingGaspEvent Remote

27 Remote CriticalLinkEvent Remote

28 Remote ErroredSymbolEvent Recovery Remote

29 Remote ErroredFramePeriodEvent Recovery Remote

30 Remote ErroredFrameEvent Recovery Remote

31 Remote ErroredFrameSecondsEvent Recovery Remote

32 Remote DyingGaspEvent Recovery Remote

33 Remote CriticalLinkEvent Recovery Remote

Address: 2nd Floor, South Building of Rainbow Plaza, No.11 Shangdi Information Road, Haidian District, Beijing Postcode: 100085 Tel: +86-10-82883305 Fax: +86-10-82883056 Email: [email protected] http://www.raisecom.com

ISCOM Series Switch EMS User Manual 070809

Documents

Transcript of ISCOM Series Switch EMS User Manual 070809