CPAN User Guide

Version-1
 Content

EMS Client and LCT

User Authority
Service Configuration
Alarm and Performance
Troubleshooting
EMS Client and LCT
 EMS: Netman 6000 OMC-O

FEATURES OMC-O Introduction

● Comprehensive centralized network management Netman6000 OMC-O is a network
o Configuration management management system designed for
o Service management comprehensive
o Fault management management of CPAN PTN products.
o Performance management
o Security and log management
● Intuitive GUI for easy element, network and service
management
● Intelligent management system
o Fast auto-discovery for network elements
o Intelligent procedures for alarms handling
o Graphic display based on real HW layout
o Multiple wizards simplify complex operations
● End-to-end service provisioning
● Distributed cluster-based architecture EMS/Proxy
● High scalability
● High availability and disaster tolerance solution
 Netman 6000 OMC-O HA/Geo
Redundancy
• High availability NMS Architecture – GEO redundancy:
• While Primary NMS is active, Secondary NMS is synchronizing all data changes in
background and performs a heartbeat detection
• If a failure is detected in the Primary NMS, the Secondary NMS will take over
• Auto switchover, manual recovery

NE NE
 EMS Client

Method of Procedure
(OUTBAND, EMS Client <-> GE
Port@GNE node)
Solution seen here is configured
in the following scenario
OUTBAND - NMS port in CPAN
GNE is configured for DCN
Management traffic uplink
EMS Client terminal will be
connected to the GE port of the
GNE node in CPAN network.

Page 6
 EMS Client

Procedure to Access EMS Client are mentioned below:

Connect laptop to CPAN device port/MPLS configured for EMS access
Assign the IP, Mask and Gateway to Laptop
Check the ping for EMS IP 10.121.1.4
Open Browser(Internet Explorer/Mozilla) and enter the URL
http://10.121.1.4:7070
Download the jre 64 bit/32 bit as available in the Laptop
Go to Control Panel/Java/Security and Edit Site list and add the IP
http://10.121.1.4:7070
Now Click on Please Click, Enter option on the browser window
Wait to download and select open and then allow
Wait for verifying application and then accept and run the application
Login window will appear. Enter the user ID and Password in the new
window
EMS Client

Page 8
 EMS Client
Logging on NMS System
If this is the first time to run the OMC-O client, it may take a while to download the
OMC-O server files.
1 Click the Please click, enter… link, the following window displays.
2 Select I accept the risk and want to run this application, then click <Run>. The
Netman6000 OMC-O Login as shown
3 Enter the User Name and Password.
4 Click <Login> to access the main interface.
5 After a successful authentication and logon, the Netman6000 OMC-O main
window

Page 9
 LCT (Local Craft Terminal)
LCT Introduction
The Netman6000OMC-O LCT (Local Craft Terminal) is a local NE management
system. PTN series product can be managed through the LCT.
LCT directly controls a PTN product through the Ethernet port. Using the LCT GUI,
NEs can be created, configured, monitored and tested.
The LCT does not store NE configurations, so it needs to connect to NE and gets
the real-time configuration from the NE all the time.
Follow the steps below to use the LCT:
1 Install the LCT software
The LCT software can be installed in a personal computer or a portable computer
for easy maintenance on site. The application layer provides the operator with a
GUI operating environment.
2 Log on to LCT
3 Create NEs in LCT topology map
4 Manage NEs
After creating NEs and on topology map, the operator can operate on NE.
The operation on NE through LCT is similar to the operation on NE through
OMC-O.

Page 10
User Authority
 User Authority

User Management: Manage the operator account properties and

control access to the system.
• Through the OMC-O User Management, user accounts can be
created, managed, modified or deleted as required.
• A user account is assigned with a role which indirectly determines
the specific operation and management privileges and MOD
assigned to the user.
• Through the user management, user passwords can be managed
and all OMC-O user information can be viewed and modified.
Assigning Privileges to a Role
• NMS provides three default privilege templates: Monitor,
Configuration and Operation.
• The user can set the privileges based on the privilege template, or
copy the privilege from other roles.

Page 12
Service Configuration
 Service Configuration

Point to Point Service(E-Line)

Multipoint to Multipoint Service(E-LAN)
Point to Multipoint Service(E-Tree)
SDH Service
PDH Service
E-Line service configuration
 E-Line service configuration

Service configuration procedure

1. Create LSP

2. Create PW

3. Create CE
 E-Line service configuration
1. Create LSP

In “Service” menu, click “LSP management”

In “LSP management”, click “Create”

 E-Line service configuration

Fill in “Name” and other items, red item is necessarily, other is optionally.
select A End NE and Z End NE
Click “Next”
 E-Line service configuration

Select all related NE to right side widow

Click “Next”
 E-Line service configuration

There are two method to “create route”. We can use anyone method to
created route.
1. Manual Create Route
2. Auto Create Route
We use Manual mode to create route, select “Manual Create Route”

Click on A NE and next Z NE. The route will be created once we click on the
nodes
 E-Line service configuration

We can get Trail information and the link color between A Node and Z node changed

Click “next” and “finish”

 E-Line service configuration

Now, use auto mode to create route, select “Auto Create Route”

Click A NE and next Z NE

Page 22
 E-Line service configuration

Select “Through Nodes” and “Excluded Nodes”

Click “Next”
 E-Line service configuration

Click “Start Route Search” to search route automatically

get “Candidate Trail” information and Select one trail, if there are many trail.
Click “finish”
 E-Line service configuration

We can get Trail information and the link color between A Node and Z node changed

Click “next” and “finish”

 E-Line service configuration

We can get one “planned” LSP, this LSP configuration only on NMS
Click “Activate”, this configuration will download to Node.
 E-Line service configuration
2. Create PW

In “Service” menu, click “PW management”

In “PW management”, click “Create”

 E-Line service configuration

Select “Create Single Segment PW”

Fill in “Name” and other items, red item is necessarily, other is optionally.
PW Type select “Ethernet” for “port” AC , “Ethernet Tagged Mode” for vlan AC
Select A End NE and Z End NE
Click “Next”
 E-Line service configuration

Select the “trail” which this PW will configure on

Here we select the LSP which we created just now.
Click “finish”

One LSP can configure many PW on it.

 E-Line service configuration

We can get one “planned” PW, this PW configuration only on NMS

Click “Activate”, this configuration will download to Node.
 E-Line service configuration
3. Create CE

In “Service” menu, click “CE Service management”

In “CE Service management”, click “Create”

 E-Line service configuration

Fill in “Name” and other items, red item is necessarily, other is optionally.
Service Type select “E-Line”
 E-Line service configuration

Select wanted port, and select “Ethernet AC mode” on two End nodes
Click “Next”
 E-Line service configuration

Create route for this CE.

In normal status, there is one default route configured for this CE,
If you want this route, you can Keep it, if don’t want it, you can delete and create again
 E-Line service configuration

Click node one by one, one window will pop up, you can select wanted PW
Click “Next”, until “Finish”
 E-Line service configuration

We can get one “planned” CE, this CE configuration only on NMS

Click “Activate”, this configuration will download to Node.

Until now, one port mode E-Line service configuration Finished

 E-Line service configuration
Vlan mode E-Line service configuration

1. LSP configuration is same as port mode E-Line service configuration

2. PW configuration is similar as port mode E-Line service,

only PW Type select “Ethernet Tagged Mode”
 E-Line service configuration

3. Vlan mode configuration is similar as port mode. select port and select AC mode
E-LAN service configuration
 E-LAN service configuration

NE1

NE2 NE4

NE3

1. Create 6 LSP between each other:

NE1-NE2,NE1-NE3,NE1-NE4
NE2-NE3,NE2-NE4
NE3-NE4
 E-LAN service configuration

NE1

NE2 NE4

NE3

2. Create 6 PW between each other:

NE1-NE2,NE1-NE3,NE1-NE4
NE2-NE3,NE2-NE4
NE3-NE4
 E-LAN service configuration

3. Select E-LAN type CE

 E-LAN service configuration

4. Add port to E-LAN

 E-LAN service configuration

5. Create route for each trial, until finish.

E-TREE service configuration
 E-TREE service configuration

NE1

root NE2 NE4

NE3

1. Create LSP according to E-Tree design:

NE2-NE1,NE2-NE4,NE2-NE3
 E-TREE service configuration

NE1

NE2 NE4

NE3

2. Create PW on LSP:

NE2-NE1,NE2-NE4,NE2-NE3
 E-TREE service configuration

3. Select E-TREE type CE

 E-TREE service configuration

4. Add port to E-TREE

 E-TREE service configuration

5. Setting “root” for E-TREE

 E-TREE service configuration

6. Select “parent Node” for other “Leaf” node

 E-TREE service configuration

7. Create route for each trial, until finish.

SDH PDH service configuration
 SDH PDH service configuration

NE1 NE2

The procedure to configure SDH and E1 service is similar with E-Line.

1. Create LSP
2. Create PW
3. Create CE

But there is some different configuration in QoS setting.

 SDH PDH service configuration

1. Create LSP
For SDH and PDH service, including ATM service, QoS must be setting,
If configured CIR, CBS must be configure together.
“Cos” is better set to 6, but 0 can also work.
 SDH PDH service configuration

2. Create PW
“PW Type” CEP can support SDH and PDH,
“satop” type can also support PDH, but not SDH.
Cos value should same as LSP,CIR and EIR can not more than LSP setting.
 SDH PDH service configuration

3. For SDH service,

STM-1 interface support SDH and ATM,
before configure CE, interface type should be confirmed.
 SDH PDH service configuration

4. For PDH service,

it support E1 and T1, before configure CE, interface type should be confirmed.
 SDH PDH service configuration

5. And for PDH service,

it support “Cep” and “satop” mode, before configure CE,
should setting this type same as PW type.
 SDH PDH service configuration

6. Create CE

“Service Type” select “SDH”, “PDH” or “Channelized STM-1”

“SDH” means two end is SDH;

“PDH” means two end is PDH;
“Channelized STM-1” means one end is SDH, the other end is PDH.
Maintenance
 Agenda

1 Alarm

2 Performance

3 Security

4 Other Maintenance

10/23/2018
 Alarm Records

Alarm ID Alarm ID name abbreviation.

Severity TN Series-supported alarms are classified into five levels:

Critical, Major, Minor, Warning and Indeterminate.

Entity type The entity type can be PW, LSP, SDH, ATM, Ethernet, Clock,
System

Category Basic alarm type

Create Time The time when an alarm occurred

Ack User The user who acknowledged the alarm

Ack Time The time when the alarm was acknowledged

Description Alarm descriptions

Specific Cause & Information regarding the probable cause of the alarm and
Recommended Action recommended action to take to clear the alarm.
 Alarm Severity Levels

Alarm Severity Displayed

Description Color
Level Character
Critical alarms indicate a severe service-affecting Red
Critical condition that requires immediate corrective action C
(Example: service interruption)

Major alarms indicate a service-affecting condition Orange

Major that requires immediate corrective action (Severe M
degradation of service)

Minor alarms indicate the existence of a non-service- Yellow

Minor affecting fault condition that requires corrective action M
to prevent a more serious fault from developing

Warning alarms indicate the detection of a potential Cyan

Warning or impending service-affecting fault, before any W
significant effects have occurred
Blue
Indeterminate alarms that have not been defined or
Indeterminate I
divided

Gray
The total number of alarms (All severity levels
Total -
combined)
 Alarm Attributes Configuration

The following alarm attributes can be modified

Alarm ID
Alarm Severity Level
Alarm Monitor
Alarm Creation Delay Time
Alarm Disappearance Delay Time
 Current Alarm

– List all active alarms or

confirmed-but-not-cleared
alarms.
 Current Alarm

The light is matched

with the severity of alarm.
 History Alarm

The alarm will go to

history alarm when it is
cleared

The customer can view

the create time, clear
time, and lasting time
of the alarms.
 Agenda

1 Alarm

2 Performance

3 Security

4 Other Maintenance

10/23/2018
 Performance Monitor

Monitor the flow of packets in the network and become aware of any
issues that might impact the flow before it starts to significantly
impact the performance of the application.

Basic objects for performance monitoring data collection:

15-minute Current Data
15-minute Historical Data
24-hour Current Data
24-hour Historical Data
Current PM
History PM
 Agenda

1 Alarm

2 Performance

3 Security

4 Other Maintenance
System Log
Operation Log
 Event Log

– Protection Switch Event

» 1+1/1:1 MSP
» 1:1 LSP
» Ring protection
» LAG
» Timing switch
» Card protection
 Agenda

1 Alarm

2 Performance

3 Security

4 Other Maintenance
Loopback
NE Backup
NE Recover
Upgrade
Troubleshooting
 Agenda

1 No Physical Card Detected by NMS

2 NE Disconnection

3 Ethernet/Ces Service Troubleshooting

4 Handling LSP/PW/LSP Protection Faults

5 QoS Troubleshooting

10/23/2018
 Handling No Physical Card Detected by NMS

This section describes how to troubleshoot no physical card detected by NMS in terms of the
symptoms, possible causes, tools required for troubleshooting and the procedure that should be
taken during the troubleshooting.

Symptoms：

A physical card is actually installed in the equipment chassis. But it cannot be detected by
NMS.

Possible Causes：

Cause 1: The equipment is powered off.

Cause 2: The card is installed in a wrong slot.
Cause 3: The card is spoiled or has some faults.
Cause 4: Some pins in the backplane are fallen and cannot be properly connected with the
sockets of the physical card.
 Handling No Physical Card Detected
by NMS

Procedure：

Cause 1:
Check whether the power of the equipment and the equipment room are both turned on.

Cause 2：
Check whether the card is installed in a proper slot or not. Ensure that all cards are installed in
correct slots.

Cause 3:
Pull the card out and check for the surface damage.

Cause 4:
Pull the card out and use a flashlight to illuminate the pins on the backplane. Check for the
fallen pins. If there is a fallen pin, replace the whole equipment chassis and send it back to factory
for repair.
 Handling NE Disconnection

This section describes how to troubleshoot NE disconnection in terms of the symptoms,

possible causes, tools required for troubleshooting and troubleshooting procedure that should
be taken during the troubleshooting.

Symptoms：

NE disconnection with NMS.

Possible Causes：

Cause 1: The equipment is powered off.

Cause 2: A fiber is broken or connected with the NE abnormally.
Cause 3: The OSPF configuration is set wrongly.
Cause 4: There is a hardware fault in the NE equipment.
Cause 5: The Interface Status of the adjacent neighbor NE connected with the disconnected
NE is ‘Down’.
 Handling NE Disconnection

Procedure：

Cause 1：
Check whether the disconnected NE equipment is powered on normally.

Cause 2:
Check whether there is an alarm about fiber break in the adjacent neighbor NE connected with
the disconnected NE.

Cause 3:
In the NMS, check for alarms and OSPF configuration of the adjacent neighbor NE connected
with the disconnected NE.

Cause 4:
Check for the status of the cards, ports and fiber connection of the disconnected NE locally.

Cause 5:
In the NMS, check whether the optical port Admin Status of the fiber’s both ends are both ‘Up’. If
not, modify as ‘Up’.
 Ethernet Service Troubleshooting

This section describes how to troubleshoot Ethernet service interruption or packet loss in terms
of the symptoms, possible causes, tools required for troubleshooting and the procedure that should
be taken during the troubleshooting.

Symptoms:

The Ethernet service in the network is interrupted, loses packets, or has error packets.

Possible Causes:

Cause 1: The card has a hardware fault, is out of position, or has excessively high or low
temperature. As a result, the card cannot work normally.

Cause 2: The Ethernet signals accessed by the Ethernet service card or the Ethernet service
interface card are lost or degraded. Or the optical fiber or optical module is abnormal.

Cause 3: The LSP carrying the Ethernet service is interrupted.

Cause 4: The bandwidth configuration is wrong.
Cause 5: The Ethernet interface configuration is wrong.
 Ethernet Service Troubleshooting
Procedure:

Cause 1:
Query the current alarms of the system to check for the CardFailure, CardOffline,
HighTemperature or LowTemperature alarm on the specific card. Make sure the hardware is
normal.

Cause 2:
Check whether the optical fibers connected with the Ethernet card are all normal and all the
optical modules in the Ethernet card work well.

Cause 3:
Check for the mismatch of each LSP label of upstream or downstream NE nodes in the LSP
tunnel. If yes, rectify it.

Cause 4:
Check whether the configured QoS parameters in LSP or PW are excessively low and the
configured QoS parameters in CE service are excessively high. If yes, correct these parameters to
restore the Ethernet service.

Cause 5:
Make sure that interfaces is admin up ,AC port mode and max frame length configure right
 TDM CES (SAToP) Service Troubleshooting

This section describes how to troubleshoot interruption or bit errors of the CES service in terms
of the symptoms, possible causes, tools required for troubleshooting and the procedure that should
be taken during the troubleshooting.

Symptoms:

The CES service (including SDH service and E1/ service) in the network has bit errors or is
interrupted. The communication is degraded or interrupted.

Possible Causes:

Cause 1: The card has a hardware fault, is out of position, or has excessively high or low
temperature. As a result, the card cannot work normally.

Cause 2: The CES signals accessed by the CES card are lost or degraded. Or the optical fiber or
optical module is abnormal.

Cause 3: The LSP carrying the CES service is interrupted.

Cause 4: The CES service port configuration is wrong.
Cause 5: The PDH service cable is broken or connected abnormally.
 CES Service Troubleshooting

Procedure:

Cause 1:
Query the current alarms of the system to check for the CardFailure, CardOffline,
HighTemperature or LowTemperature alarm on the specific card. Make sure the hardware is
normal.

Cause 2:
Check whether the optical fibers connected with the CES card are all normal and all the optical
modules in the Ethernet card work well.

Cause 3:
Check for the mismatch of each LSP label of upstream or downstream NE nodes in the LSP
tunnel. If yes, rectify it.

Cause 4:
Enter the General Interface Config tab in the [NE Management > Interface Management]
interface in the NMS，and configure the port admin up.

Cause 5:
Check whether the PDH service cable and its connection are both normal.
 Handling LSP Faults

This section describes the LSP faults such as the creation failure or service interruption in terms
of the symptoms, possible causes, tools required for troubleshooting and the procedure that should
be taken during the troubleshooting.

Symptoms:

1.Creating the LSP tunnel fails, and thus the service is unavailable.
2.The LSP tunnel is faulty, and thus the service is interrupted.

Possible Causes:

Cause 1: The routing fails.

Cause 2: Creating the LSP tunnel fails.
Cause 3: The physical link where the LSP tunnel resides is faulty.
 Handling LSP Faults

Procedure:

Cause 1:
a. Check whether there is a complete and reachable link between the NEs where the source and
sink nodes of the LSP tunnel reside. If the link does not exist, repair the incomplete or faulty part of
the link.
b. Check whether there is a disconnected NE among the LSP tunnel. If yes, rectify the NE
disconnection fault.

Cause 2:
a. Check whether there are conflict LSP labels in the NMS. If yes, rename the LSP labels.
b. Check whether the number of LSP tunnels reaches the upper limit of the NE or that of the card.
If yes, make a plan again or delete redundant LSP tunnels.

Cause 3:
a. Check whether the CardFailure, CardOffline, Los alarm indicating that the physical link used by
the LSP tunnel is faulty exists in the system. If yes, take priority to handle the alarm.
b. Check whether anomalies such as card faults or NE resetting exist on the opposite equipment.
If yes, rectify the anomalies.
 Handling LSP Protection Faults

This section describes the protection switching fails, and thus the service is interrupted, or
packet loss and bit errors occur in the service faults.

Symptoms:

The protection switching fails, and thus the service is interrupted, or packet loss and bit errors
occur in the service.

Possible Causes:

Cause 1: The LSP automatic protection switching fails.

 Handling LSP Protection Faults

Procedure:

Cause 1:

a. Check whether the configurations at the two ends of the APS protection group are inconsistent.
If yes, make sure the consistent configurations at the two ends.

b. Check whether the optical fibers or cables are correctly connected. If not, correct the fiber or
cable connection.

c. Check whether a hardware alarm such as CardFailure or CardOffline exists in the card where
the protection LSP resides. If yes, clear the CardFailure or CardOffline alarm.

d. Check whether an OAM alarm exists in the working LSP or protecting LSP. If yes, the protection
capability of the very LSP fails. In this case, clear the alarm, and then check whether the switching
can be normally performed.
 Handling PW Faults

This section describes the PW faults such as the creation failure or service interruption in terms
of the symptoms, impact on the system, possible causes, tools required for troubleshooting and
the procedure that should be taken during the troubleshooting.

Symptoms:

1.Creating the PW fails, and thus the service is unavailable.

2.The PW is faulty, and thus the service is interrupted, or packet loss or bit errors occur in the
service.

Possible Causes:

Cause 1: Creating the PW fails.

Cause 2: The physical link is faulty.
Cause 3: The LSP tunnel where the PW resides is faulty.
 Handling PW Faults

Procedure:

Cause 1:
a. Check whether both the selected source and sink ends are proper to be used for creating
PW.
b. Check whether the number of PWs reaches the upper limit of the NE or that of the card. If
yes, make a plan again or delete redundant PWs.

Cause 2:
a. Check whether the physical link between the source and sink nodes of the PW are normal
and whether the CardFailure, CardOffline alarm exists in the system. If the alarm exists, take
priority to handle the alarm.
b. Check whether anomalies such as card faults or NE resetting exist in the opposite
equipment. If yes, rectify the anomalies.

Cause 3:
For details on the tunnel faults, refer to Section Handling LSP Faults.
 QoS Troubleshooting

This section describes the QoS faults in terms of the symptoms, possible causes, tools
required for troubleshooting and the procedure that should be taken during the troubleshooting.

Symptoms:

a. The service is configured with bandwidth parameters, but the actual traffic exceeds the limit.
Hence, the traffic is too large and the congestion occurs.
b. Different services preempt bandwidth mutually. The packets of the service are lost or bit
errors occur in the service whose bandwidth is preempted.

Possible Causes

Cause 1: The NE is not configured with the QoS policy.

Cause 2: During the service configuration, an incorrect QoS policy is selected.
Cause 3: The bandwidth configured in the LSP tunnel or PW is small.
Cause 4: The card is faulty, and the configuration data is not delivered to the card.
 QoS Troubleshooting

Procedure:

Cause 1:
Check whether the NE is configured with the related QoS policy.If the NE is not configured with
the related QoS policy, configure the missed QoS policy.

Cause 2:.
Check whether the QoS policy that is currently configured is applicable. If it is not applicable,
reconfigure a new policy.

Cause 3:
Check whether the bandwidth that is currently configured in the tunnel or PW meets the
requirement for the traffic.

Cause 4:
Check whether a hardware alarm such as CardFailure exists in the system. If yes, clear it.