blog presentation

F4798_Q11

SpectralWave™ C-Node

STM-4/STM-1 Compact Multiplexer

RELEASE 5.11

OPERATION AND MAINTENANCE

NEC Corporation

• 7-1, Shiba 5-chome, Minato-ku, Tokyo 108-8001, Japan • TEL +81-3-3454-1111

• TELEX NECTOK J22686 • FAX +81-3-3798-1510/9 • E-mail:[email protected]

F4798_Q11 OPERATION AND MAINTENANCE

Windows® 2000/XP is either registered trademarks or trademarks of Microsoft. Corporation in the United States and/or other countries. SpectralWave is a registered trademark of NEC Corporation. Copyright © 2007 by NEC Corporation. All rights reserved. The information of this manual was approved by product manager of CND. This manual is subject to change without notice. 1st Issue Apr. 2008 Printed in China


CONTENTS

Contents - i -

1. SUMMARY 1-1

1.1 Overview of Maintenance Works..........................................................1-1

1.2 Requirements for Maintenance Operation...........................................1-2 1.2.1 Skills Required for Maintenance Operator ..............................................1-2 1.2.2 Apparatus for Maintenance.......................................................................1-2

2. OPERATION CONTROLS 2-1

2.1 Orderwire................................................................................................2-2 2.1.1 Using Handset (Telephone Set) ................................................................2-2 2.1.2 Terminate Orderwire Communication......................................................2-3

2.2 House Keeping Control .........................................................................2-4 2.2.1 Apparatus ...................................................................................................2-4 2.2.2 Parameters .................................................................................................2-4 2.2.3 Procedure: Enable Housekeeping Controls............................................2-4

3. RETRIEVE INFORMATION 3-1

3.1 Alarm Status...........................................................................................3-1 3.1.1 Procedure: Open Alarm Monitor Dialog Box...........................................3-1 3.1.2 Alarm Monitor Dialog Box.........................................................................3-2 3.1.3 View Current Alarms..................................................................................3-5 3.1.4 View History Alarms ..................................................................................3-8 3.1.5 View Actual Alarms..................................................................................3-10

3.2 Operation Log ......................................................................................3-12 3.2.1 Items in Operation Log Dialog Box........................................................3-12 3.2.2 Procedure: View Operation Logs ...........................................................3-13

3.3 Event View............................................................................................3-15 3.3.1 Mointor Traffic Performance...................................................................3-15 3.3.2 Monitor Path Protection Switching Conditions ....................................3-17 3.3.3 Monitor MS Protection Switching Conditions.......................................3-18 3.3.4 Monitor Timing Source Switching Conditions ......................................3-19

3.4 Performance Monitoring .....................................................................3-20 3.4.1 PM Parameters.........................................................................................3-20 3.4.2 Display Current PM Status......................................................................3-35


Contents - ii -

3.4.3 Display History PM Data..........................................................................3-43 3.4.4 PM Counter Reset....................................................................................3-49 3.4.5 Display Threshold Crossing Alert (TCA) ...............................................3-52

3.5 Hardware Inventory and LED Status ..................................................3-53 3.5.1 Display Hardware Information and LED Status ....................................3-53

3.6 Firmware Version.................................................................................3-55 3.6.1 Procedure: Retrieve Installed Firmware Version ..................................3-55

3.7 Logged-in Users ..................................................................................3-56 3.7.1 Procedure: Retrieve Logged-in Users List ............................................3-56

4. ROUTINE MAINTENANCE 4-1

4.1 Check LED Operation on All Boards....................................................4-1 4.1.1 Target Boards.............................................................................................4-1 4.1.2 Procedure: Verify LEDs on Front Panel of C-Node.................................4-1 4.1.3 Procedure: Verify LEDs on 100Base-T/100Base-T2 Tributary Board....4-2 4.1.4 Procedure: Verify LEDs on Board by CID................................................4-3

4.2 Check FAN..............................................................................................4-4 4.2.1 Apparatus ...................................................................................................4-4 4.2.2 Procedure: Verify FAN...............................................................................4-4

5. HARDWARE REPLACEMENT 5-1

5.1 Replace Cables ......................................................................................5-2 5.1.1 Precautions ................................................................................................5-2 5.1.2 Apparatus ...................................................................................................5-2 5.1.3 Procedure: Disconnect Cables.................................................................5-2 5.1.4 Procedure: Connect Cables......................................................................5-2

5.2 Board ......................................................................................................5-3 5.2.1 Precautions ................................................................................................5-3 5.2.2 Apparatus ...................................................................................................5-4 5.2.3 Procedure: Replace Board........................................................................5-4

5.3 SFP Module ............................................................................................5-5 5.3.1 Precautions ................................................................................................5-5 5.3.2 Apparatus ...................................................................................................5-5 5.3.3 Procedure: Replace SFP Module..............................................................5-5

5.4 Power Board...........................................................................................5-7 5.4.1 Precautions ................................................................................................5-7 5.4.2 Apparatus ...................................................................................................5-7 5.4.3 Procedure: Replace Power Board............................................................5-7

5.5 Fuse of Power Board.............................................................................5-8 5.5.1 Precautions ................................................................................................5-8


Contents - iii -

5.5.2 Apparatus ...................................................................................................5-8 5.5.3 Procedure: Replace Fuse of Power Board ..............................................5-8

5.6 FAN .......................................................................................................5-10 5.6.1 Precautions ..............................................................................................5-10 5.6.2 Apparatus .................................................................................................5-10 5.6.3 Procedure: Replace FAN.........................................................................5-10

6. EQUIPMENT MAINTENANCE 6-1

6.1 Database Upload/Download..................................................................6-2 6.1.1 Database List..............................................................................................6-2 6.1.2 Procedure: Upload/Download Database..................................................6-4

6.2 Equipment Reset ...................................................................................6-8 6.2.1 Procedure: Execute Equipment Reset.....................................................6-8

6.3 Equipment Initialization.......................................................................6-10

7. TRAFFIC MAINTENANCE 7-1

7.1 Loopback................................................................................................7-2 7.1.1 Description .................................................................................................7-2 7.1.2 Loopback Statuses ....................................................................................7-3 7.1.3 Procedure: Setup Loopback.....................................................................7-3

7.2 Crossconnect Maintenance ..................................................................7-5

7.3 Protection ...............................................................................................7-6 7.3.1 MSP .............................................................................................................7-6 7.3.2 SNCP.........................................................................................................7-10 7.3.3 Timing Source Protection .......................................................................7-13

8. FIRMWARE MAINTENANCE 8-1

8.1 Switch Firmware Version ......................................................................8-2 8.1.1 Procedure: Switch Firmware Version ......................................................8-2

8.2 Upgrade Firmware Version ...................................................................8-4 8.2.1 Procedure: Upgrade the Version of Mainboard ......................................8-4

9. CONFIGURATION CHANGES 9-1

9.1 Adding Nodes ........................................................................................9-2 9.1.1 Example Description(Before Change) .....................................................9-2 9.1.2 IP Address Configuration..........................................................................9-6 9.1.3 NSAP Change........................................................................................... 9-11 9.1.4 Crossconnect Configuration ..................................................................9-14

9.2 Removing Nodes .................................................................................9-21


Contents - iv -

10. TROUBLE CLEARING 10-1

10.1 Making Contact with NEC ...................................................................10-1

10.2 Categories of Condition Types ...........................................................10-2 10.2.1 List of Indication Messages....................................................................10-2

10.3 Retrieve Alarm Information.................................................................10-9 10.3.1 Procedure: Display Current Alarm .........................................................10-9

10.4 Equipment .......................................................................................... 10-11 10.4.1 BUS_ERROR .......................................................................................... 10-11 10.4.2 MEM_FAIL...............................................................................................10-12 10.4.3 PKG_FAIL ...............................................................................................10-13 10.4.4 PKG_REMOVED.....................................................................................10-14 10.4.5 PKG_TYPE..............................................................................................10-15

10.5 Facility ................................................................................................10-16 10.5.1 AIS...........................................................................................................10-17 10.5.2 AU-AIS ....................................................................................................10-18 10.5.3 AU-LOP ...................................................................................................10-19 10.5.4 CLKFAIL..................................................................................................10-20 10.5.5 CLKDRIFT...............................................................................................10-21 10.5.6 HP-DEG...................................................................................................10-22 10.5.7 HP-EXC ...................................................................................................10-23 10.5.8 HP-PLMF.................................................................................................10-24 10.5.9 HP-RDI ....................................................................................................10-25 10.5.10 HP-TIM .................................................................................................10-26 10.5.11 HP-UNEQ .............................................................................................10-27 10.5.12 LOF.......................................................................................................10-28 10.5.13 LOF ⎯ 2Mbps......................................................................................10-29 10.5.14 LOM......................................................................................................10-30 10.5.15 LOS ......................................................................................................10-31 10.5.16 LOS ⎯ 2 MHz ......................................................................................10-32 10.5.17 LOS ⎯ Electrical INTF........................................................................10-33 10.5.18 LP-DEG ................................................................................................10-34 10.5.19 LP-EXC.................................................................................................10-35 10.5.20 LP-PLMF ..............................................................................................10-36 10.5.21 LP-RDI..................................................................................................10-37 10.5.22 LP-TIM..................................................................................................10-38 10.5.23 LP-UNEQ..............................................................................................10-39 10.5.24 LTI.........................................................................................................10-40 10.5.25 MS-AIS .................................................................................................10-41 10.5.26 MS-DEG ...............................................................................................10-42 10.5.27 MS-EXC................................................................................................10-43 10.5.28 MS-RDI .................................................................................................10-44


Contents - v -

E

10.5.29 PPI_AIS ................................................................................................10-45 10.5.30 PPI_EXC...............................................................................................10-46 10.5.31 PPI_DEG ..............................................................................................10-47 10.5.32 PPS-FAIL..............................................................................................10-48 10.5.33 REF_FAIL.............................................................................................10-49 10.5.34 RS-TIM .................................................................................................10-50 10.5.35 TU-AIS..................................................................................................10-51 10.5.36 TU-LOP ................................................................................................10-52

10.6 Environment.......................................................................................10-53 10.6.1 HKAn.......................................................................................................10-53

10.7 Network...............................................................................................10-54 10.7.1 LINK-FAIL ...............................................................................................10-54

10.8 Ethernet Alarm ...................................................................................10-55 10.8.1 CSF_LCS ................................................................................................10-55 10.8.2 CSF_LCSync ..........................................................................................10-56 10.8.3 CSF_R_LCS............................................................................................10-57 10.8.4 CSF_R_LCSync......................................................................................10-58 10.8.5 DropPkt_EXC .........................................................................................10-59 10.8.6 LINK_DOWN ...........................................................................................10-60 10.8.7 RxAlignmentErrorFrame_EXC..............................................................10-61 10.8.8 RxFCSErrorFrame_EXC ........................................................................10-62 10.8.9 TxCollisionFrame_EXC .........................................................................10-63 10.8.10 TxDelayTransmission_EXC................................................................10-64 10.8.11 TxExtCollisionFrame_EXC.................................................................10-65 10.8.12 TxLateCollisionFrames_EXC.............................................................10-66 10.8.13 WAN_PORT_SD ..................................................................................10-67 10.8.14 WAN_PORT_SF...................................................................................10-68

10.9 Encapsulation Alarm .........................................................................10-69 10.9.1 SSF_LGS ................................................................................................10-69 10.9.2 LAPS_FAIL .............................................................................................10-70

10.10 Virtual Concatenation Alarm.........................................................10-71 10.10.1 LP-Xv-LOA...........................................................................................10-71 10.10.2 LP-Xv-LOM ..........................................................................................10-72 10.10.3 LP-Xv-PLM...........................................................................................10-73 10.10.4 LP-Xv-SQM ..........................................................................................10-74

10.11 Office Alarms..................................................................................10-75

10.12 Alarm Action Table.........................................................................10-76

This page is intentionally left blank.


Summary ⎯ Overview of Maintenance Works 1-1

1. SUMMARY

This manual provides information on operation and maintenance for the SpectralWave C-Node.

1.1 Overview of Maintenance Works

Maintenance works are roughly divided into routine maintenance and operational maintenance.

For operational maintenance, the performance monitoring function is provided so as to identify and isolate the problem if it occurs. Refer to the section 3.Retrieve Information for details.

Routine maintenance is necessary to secure normal equipment operations. Detailed information is provided in the section 4. Routine Maintenance.

If any failure occurs, it is notified by alarms. The section 10. Trouble Clearing provides detailed information on alarms and clearance methods for alarmed conditions.


Summary ⎯ Requirements for Maintenance Operation 1-2 E

1.2 Requirements for Maintenance Operation

The following are required for maintenance operation.

1.2.1 Skills Required for Maintenance Operator Maintenance operations must be performed by qualified personnel who satisfies the following requirements:

Having been trained by supplier transaction engineers or having coordinative experience of training.

Knowledge to PC: mastering the ABC of operating system including English version Windows® 2000/XP.

NOTE: “ABC” is used as maintenance technology example.

1.2.2 Apparatus for Maintenance The following apparatuses are required for maintenance works:

Error code testing instrument (PDH/SDH)

Multi-meter whose precision error is less than ±5%

Single mode fibers, adapters, connecting cable, optical splitter

Optical power meter

Optical attenuator

Cleaning kit for optical connector


Operation Controls 2-1

2. OPERATION CONTROLS

This section provides information on the use of the orderwire function and HKC (House Keeping Control) operations to control C-Node.


Operation Controls ⎯ Orderwire 2-2

2.1 Orderwire

This subsection provides the procedures for operating the orderwire.

NOTE:

1. Handset (Telephone Set) which requires distinction of Tip and Ring terminal can not be used for the orderwire interface of C-Node.

2. Only one of two orderwire interfaces on C-Node front and rear side can be used at the same time.

2.1.1 Using Handset (Telephone Set) By using a handset, a caller can only make a selective calling (point-to-point orderwire communication) and a group calling (multiparty line).

2.1.1.1 Apparatus Handset (Two wire DTMF tone Telephone set)

2.1.1.2 Requirements Set correct configuration of orderwire, and the handset is connected to the equipment.

2.1.1.3 Procedure: Operate Orderwire ⎯ Handset (Calling Side)

1. Pick up the handset. OW LED becomes green.

2. Push the code number of receiving side. OW LED blinks.

3. Waiting for the response.

This step is the end of the procedure.

2.1.1.4 Procedure: Operate Orderwire ⎯ Handset (Receiving Side)

1. Receive the request from the calling side. OW LED blinks and buzzer bips.

2. Pick up the handset. OW LED blinks and buzzer becomes silent.

3. Begin the talking.



Operation Controls ⎯ Orderwire 2-3

2.1.2 Terminate Orderwire Communication Perform the following procedure to terminate the orderwire communication and release the line.

NOTE: If a selected line to be closed has been used at any other nodes in the network, those connections will also be terminated by performing the following procedure.

2.1.2.1 Procedure: Terminate Orderwire ⎯ Normal Orderwire Termination Method( Telephone Set On-hook Method)

1. Hang up the telephone on-hook.

2. Verify that the connection is terminated and the orderwire line status is changed to idle.

2.1.2.2 Procedure: Terminate Orderwire ⎯ Forced Hang Up

1. Select Forced Hang Up to valid status in Orderwire and User CH Configuration window.

2. Execute the command by pressing Set button.

3. Verify that the connection is terminated and the orderwire line status is changed to idle.



Operation Controls ⎯House Keeping Control 2-4

2.2 House Keeping Control

This subsection provides the procedure to enable/disable HKC assigned by the procedure in the F4798_Q10 PROVISIONING manual.

2.2.1 Apparatus CID

2.2.2 Parameters

PARAMETER VALUE DESCRIPTION

Start Clicking this radio button enables HKC.

Control Status

Stop Clicking this radio button disables HKC.

Duration 60 thru 15240 (s) Set the duration time.

2.2.3 Procedure: Enable Housekeeping Controls

1. Start up the CID, and log in to the target NE.

2. Open the management dialog box of the target NE. Detailed operation is provided in the section CH07. Working with CID of the F4798_Q09 CID OPERATING GUIDE manual.

3. From the main menu on the NE management dialog box, select Set HKA/HKC from the Configuration menu. The Set HKA/HKC dialog box appears:

4. Click the HKC Interface tab on the Set HKA/HKC dialog box. Figure 2-1 shows an example:


Operation Controls ⎯House Keeping Control 2-5

E

Figure 2-1. Set HKA/HKC Dialog Box (HKC)

5. In this dialog box, four control output interfaces on the Mainboard can be managed. Click the target interface. The Control Status and Start/Stop radio buttons is available, then remove check on Hold-on check box, Duration text field are available also.

6. Click the Start button by clicking the radio button on the right of Control Status (leaving a tick).

7. Set the duration time in the Duration text field.

NOTE: The range of duration time is within 60 through 15240 seconds.

8. Repeat Steps 5 thru 7 for other HKCs to be enabled.

9. When completed, click the Set button.



Retrieve Information ⎯ Alarm Status 3-1

3. RETRIEVE INFORMATION

3.1 Alarm Status

The information on the alarm status, including the current alarms, history alarm and actual alarms, can be retrieved and displayed in the Alarm Monitor dialog box.

NOTE: C-Node can only save up to 1000 items of History Alarm message. When the number of History Alarm message is more than 1000, C-Node will delete the alarm who’s “Alarm End Time” is most early.

3.1.1 Procedure: Open Alarm Monitor Dialog Box Perform the following procedure to open the Alarm Monitor dialog box:



3. Perform one of the following procedures:

Select Current Alarm, History Alarm or Actual Alarm from the Alarm menu. The Alarm Monitor dialog box appears with the corresponding tab selected.

Click the visual board of the equipment in the NE management dialog box. The Alarm Monitor dialog box appears with the Current Alarm tab selected.

Click the shortcut button. The Alarm Monitor dialog box appears with the Current Alarm tab selected.

This step is the end of the procedure. Go to the section 3.1.2 Alarm Monitor Dialog Box subsection for the use of the Alarm Monitor dialog box.



3.1.2 Alarm Monitor Dialog Box Figure 3-1 shows an example of the Alarm Monitor dialog box:

Figure 3-1. Alarm Monitor Dialog Box (Current Alarm Tab Selected)

Alarm contents

Tabs to switch Current Alarm, History Alarm

and Actual Alarm



3.1.2.1 Items in Alarm Monitor Dialog Box

ITEMS DESCRIPTION

column headers (on top) Sort alarm records. By clicking a column header, the alarm records in the list are sorted according to the selected subject.

Current Alarm tab Switch the window for displaying a list of current alarms.

History Alarm tab Switch the window for displaying alarm history.

Actual Alarm tab Switch the window for displaying a list of alarms including both masked and unmasked ones (actual alarms).

Retrieve button The alarms of NE are collected again by clicking this button.

Print button The alarm information is printed out by clicking this button.

Close button Alarm browsing is quitted (closing the dialog box) by clicking this button.

Auto Report Screen check box

The auto report function is enabled by clicking this check box (leaving a tick). This is provided for the current alarm list (Current Alarm tab selected) only.

All check box Specifies whether to list the alarm records of all the boards or those of a certain board type by clicking this check box. When this is selected (leaving a tick), the alarms in all boards are listed. When this is not selected (leaving empty), only the alarms in certain-type boards are listed. This is selected by default.



3.1.2.2 Display Options

When the All check box is unselected (leaving empty), the following display options are available:

ITEMS DESCRIPTION

Board Used to select the board type from the drop-down list.

Port Type Used to select the port type from the drop-down list.

Equipment Specify to list equipment alarms.

Facility Specify to list facility alarms.

Environment Specify to list environment alarms.

Alarm Class

Ethernet Specify to list Ethernet alarms.

Critical Alarm Specify to list critical alarms (CR).

Major Alarm Specify to list major alarms (MJ).

Minor Alarm Specify to list minor alarms (MN).

Alarm Severity

Warning Specify to list warning alarms (WN).

Start Time Specify the start time for time span. Time Span

End Time Specify the end time for time span.



3.1.3 View Current Alarms A list of alarms that is currently occurring and not cleared can be displayed in the Alarm Monitor dialog box with the Current Alarm tab selected.

The list of the current alarms is displayed when opening the Alarm Monitor dialog box. When the Alarm Monitor dialog box has already been opened for viewing alarm history or actual alarms, switch the window by clicking the History Alarm or Actual Alarm tab.

Figure 3-2. Alarm Monitor Dialog Box (Current Alarm)

In this dialog box:

Click the Retrieve button to update the current alarm list.

Click the Print button to print out the current alarm list.

Click the Close button to finish alarm monitor.

List of Current Alarms

Current Alarm tab



3.1.3.1 Using Display Options

When the Alarm Monitor dialog box is opened for the first time, the All check box is selected by default to display all current alarms for the equipment. The current alarms to be displayed, however, can be specified by using the display options. Refer to the 3.1.2.2 Display Options subsection for detailed information on the display options.

Perform the following procedure to select the current alarms to be displayed in the list:

Procedure:

1. Clear the active state of All check box by clicking. The window shown in Figure 3-3 appears:

Figure 3-3. Browsing Current Alarms (Clear All Check Box)

click to unselect.



2. Select the board type from the drop-down list on the right of Board.

3. Select the port type from the drop-down list on the right of Port Type.

4. Specify the alarm class by clicking the check boxes in the Alarm Class field.

NOTE: Refer to the section 10.2.1 List of Indication Message to select Alarm Class.

5. Specify the alarm severity by clicking the check boxes in the Alarm Severity field.

NOTE: Refer to the section 9.5 Alarm Attributes of F4798_Q10 PROVISIONING manual.

6. Click the Retrieve button. The current alarms that correspond to the selection above are displayed.


NOTE:

1. To display all the current alarms after specifying the current alarms to be displayed, click the All check box and click the Retrieve button.

2. Selection/unselection of the All check box is valid even after the window is switched by clicking the History Alarm/Actual Alarm tab for viewing alarm history/actual alarms.

3.1.3.2 Auto Refresh Function

Current alarm information displayed in the Alarm Monitor dialog box can automatically be updated by using the auto refresh function. This function is enabled by clicking the Auto Report Screen check box. After select/unselect the Auto Report Screen check box, click the Retrieve button to update the Current Alarm display.

The alarm should be reported automatically after the alarm’s delay time has passed and it should be holding before exceed this alarm’s stretch time.



3.1.4 View History Alarms A list of alarms that have already cleared and confirmed by the user (alarm history) can be displayed in the Alarm Monitor dialog box with the History Alarm tab selected.

To display the alarm history, perform one of the following:

Select History Alarm from the Alarm menu.

When the Alarm Monitor dialog box has already been opened for viewing current alarms or actual alarms, click the History Alarm tab.

Figure 3-4. Browsing Alarm History (Clear All Check Box)

In this dialog box:

Click the Retrieve button to update the alarm history.

Click the Print button to print out the alarm history.

Click the Close button to finish viewing.

History Alarm tab




Alarms displayed in the history alarm field can be specified by using the display options. Refer to the subsection 3.1.2.2 Display Options for detailed information.

Perform the following procedure to select the alarms displayed in the history alarm.

Procedure:

1. Unselect the All check box by clicking.





5. Specify the alarm severity by clicking the check boxes in the Alarm Severity field within NE working period.


6. Specify the time span by setting Start Time and End Time in the Time Span field.

7. Click the Retrieve button. The alarms that correspond to the selection above are displayed.


NOTE: 1. To display all alarms after specifying the alarms to be displayed in the

history alarm, click the All check box to select it again and click the Retrieve button.

2. Selection/unselection of the All check box is valid even after the window is switched by clicking the Current Alarm/Actual Alarm tab for viewing current alarms/actual alarms.



3.1.5 View Actual Alarms A list of alarms, regardless of whether they are masked or not, can be displayed in the Alarm Monitor dialog box with the Actual Alarm tab selected.

NOTE: The difference between current alarm and actual alarm is that actual alarm includes masked current alarms but current alarm not, that is, masked current alarms are shown in actual alarm tab but not in current alarm tab.

To display the actual alarms, perform one of the following:

Select Actual Alarm from the Alarm menu.

When the Alarm Monitor dialog box has already been opened for viewing current alarms or actual alarms, click the Actual Alarm tab.

Figure 3-5. Browsing Actual Alarm (Clear All Check Box)

In this dialog box:

Click the Retrieve button to update the actual alarm list.

Click the Print button to print out the actual alarm list.

Click the Close button to finish viewing.

Actual Alarm tab




Actual alarms to be displayed can be specified by using the display options. Refer to the subsection 3.1.2.2 Display Options for detailed information.

Perform the following procedure to select the alarms displayed in the actual alarm list:

Procedure:

1. Unselect the All check box by clicking.





5. Specify the alarm severity by clicking the check boxes in the Alarm Severity field.


6. Click the Retrieve button. The alarms that correspond to the selection above are displayed.


NOTE: 1. To display all the alarms after specifying the alarms to be displayed in the actual

alarm list, click the All check box to select it again and click the Retrieve button.

2. Selection/unselection of the All check box is valid even after the window is switched by clicking the Current Alarm/History Alarm tab for viewing current alarms/alarm history.


Retrieve Information ⎯ Operation Log 3-12

3.2 Operation Log

A list of the operation logs (event logs) of the NE can be displayed in the Operation Log dialog box.

3.2.1 Items in Operation Log Dialog Box

ITEMS DESCRIPTION

column headers (on top) Sort operation logs. By clicking a column header, the operation logs in the list are sorted according to the selected subject.

Start Time/End Time Specify the time scope. It is valid when the radio button TIME SCOPE is selected.

TIME SCOPE radio button Display the operation logs within the time range specified by Start Time and End Time. When this radio button is selected, the ALL radio button on the right of this radio button is automatically unselected, and Start Time and End Time are enabled.

ALL radio button Display all the operation logs, regardless of the time range. When this radio button is selected by click, the TIME SCOPE radio button on the left of this radio button is automatically unselected, and Start Time and End Time are disabled.

Delete button Delete selected operation logs from the list.

Retrieve button Retrieve the operation logs.

Print button Print out the operation log list.

Close button Finish the operation log browsing (closing the dialog box).


Retrieve Information ⎯ Operation Log 3-13

3.2.2 Procedure: View Operation Logs Perform the following procedure to view the operation log list:



3. Open the Operation Log dialog box by performing one of the following procedures:

Select Operation Log from the Security menu.

Click the shortcut button.

Figure 3-6 shows an example:

Figure 3-6. Operation Log Dialog Box

4. In this dialog box;

To display all the operation logs, click the ALL radio button (leaving a tick), and click the Retrieve button.


Retrieve Information ⎯Operation Log 3-14

5. In this dialog box;

To display all the operation logs, click the ALL radio button (leaving a tick), and click the Retrieve button.

To display operation logs within a certain time range, click the TIME SCOPE radio button (leaving a tick) and specify the start time and end time in the Start Time and End Time text boxes. Then click the Retrieve button.

6. To quit the operation log browsing, click the Close button. The Operation Log dialog box will be closed.



Retrieve Information ⎯ Event View 3-15

3.3 Event View

The conditions of traffic performance TCA and protection can be retrieved and displayed in the Event View dialog box.

3.3.1 Mointor Traffic Performance Perform the following procedure to monitor the traffic performance:

Procedure: 1. Start up the CID, and log in to the target NE.


3. Select Event View from the Alarm menu. The Event View dialog box shown in Figure 3-7 appears:

Figure 3-7. Event View Dialog Box with TCA Event Tab



4. Confirm that the TCA tab is selected. If not, click the TCA tab.

5. Click the Retrieve button. The performance conditions of the existing events are displayed.

6. Click the Close button to finish event monitor.




3.3.2 Monitor Path Protection Switching Conditions Perform the following procedure to monitor the path protection switching conditions:

Procedure:



3. Select Event View from the Alarm menu. The Event View dialog box appears.

4. Click the PPS Event tab. The window shown in Figure 3-8 appears:

Figure 3-8. Event View Dialog Box with PPS Event Tab

5. Click the Retrieve button. The locations and causes of switching events are displayed, if any events happen.



PPS Event tab

Here show the VC4 sequence number in XC matrix. The relationship between slot ID and VC4 sequence number is shown as below: Main Port1: 1~4

Port 2: 5~8 Slot1: 9~10 (9~12 for STM4_S subboard) Slot2: 11~12 Slot3: 13~14 (13~16 for STM4_S subboard) Slot4: 15~16

Here show the VC12 (or VC3) sequence number in the VC4.



3.3.3 Monitor MS Protection Switching Conditions Perform the following procedure to monitor the MS protection switching conditions:

Procedure:




4. Click the MSP Event tab. The window shown in Figure 3-9 appears:

Figure 3-9. Event View Dialog Box with MSP Event Tab

5. Click the Retrieve button. The locations and causes of MSP events are displayed, if any events happen.



MSP Event tab


Retrieve Information ⎯Event View 3-19

3.3.4 Monitor Timing Source Switching Conditions Perform the following procedure to monitor the timing source switching conditions:

Procedure:




4. Click the Timing Source Switch Event tab. The window shown in Figure 3-10 appears:

Figure 3-10. Event View Dialog Box with Timing Source Switch Event Tab

5. Click the Retrieve button. The locations and causes of Timing Source switching events are displayed, if any events happen.



Timing Source Switch Event tab


Retrieve Information ⎯ Performance Monitoring 3-20

3.4 Performance Monitoring

The Performance Monitoring (PM) is used to identify and isolate the problem if occurring at a particular line or path. It also monitors the quality of lines and paths. All Performance Monitoring parameters are collected every minute and accumulated to 15-minute and 24-hour (1 day) statistics. The following are brief descriptions about the PM provided by C-Node.

3.4.1 PM Parameters

3.4.1.1 PM Status Monitor Types

SDH PM

(1 of 2)

MONITOR TYPES DEFINITION SPEC.

BBE Near end background block error ITU-T G.826 G.784

ES Near end errored seconds ITU-T G.826 G.784

SES Near end severely errored seconds ITU-T G.826 G.784

OFS Out of frame seconds ITU-T G.784

RST

UAS Unavailable seconds ITU-T G.826 G.784




MST


FEBBE Far end background block error ITU-T G.826 G.784

FEES Far end errored seconds ITU-T G.826 G.784

FESES Far end severely errored seconds ITU-T G.826 G.784

MST (Far End)

FEUAS Far end unavailable seconds ITU-T G.826 G.784




HPT




(2 of 2)





HPT (Far End)





LPT





LPT (Far End)


PJE-P (see NOTE1)

Pointer justification event ITU-T G.783,G.784 MSA

PJE-N (see NOTE1)

Pointer justification event ITU-T G.783,G.784

PJE-P (see NOTE1)

Pointer justification event ITU-T G.783,G.784 HPA

PJE-N (see NOTE1)

Pointer justification event ITU-T G.783,G.784

PSC Protection switching counts (Only for 1+1 APS)

ITU-T G.783 MSP

PSD (see NOTE2)

Protection switching duration (Only for 1+1 APS)

ITU-T G.783

NOTE:

1. PJE is the pointer justification event, and justification because of AU pointer stuff:

AU pointer positive stuff=>PJE-P

AU pointer Negative stuff=>PJE-N

No AU pointer stuff=>No PJE counter

2. PSD is not supported now.



Ethernet PM

(1 of 3) MONITOR TYPES DEFINITION SPEC.

ETH-DropPkts A count of drop packets.

ETH-RxAlignmentErrorFrames

A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check

RFC1643

ETH-RxBroadcastPkts

Number of good broadcast packets received

ETH-RxFCSErrorFrames

A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check.

RFC1643

ETH-RxMulticastPkts

Number of good multicast packets received(excluding broadcast packets)

ETH-RxOctets The total number of octets received on the interface, including framing characters.

RFC1213

ETH-RxPkt1024toMax

Number of packets received that were between 1024 and the Mac_Pkt_Len octets in length (including error packets)

ETH-RxPkt128to255

Number of packets received that were between 128 to 255 octets in length (including error packets)

ETH-RxPkt256to511


ETH-RxPkt512to1023


ETH-RxPkt64 Number of packets received that were 64 octets in length (including bad packets)

ETH-RxPkt65to127


ETH-TxCollision

Number of collisions on this Ethernet segment

LAN

ETH-TxDelayTransmissions

A count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy.

RFC1643



(2 of 3)


ETH-TxExtCollisionFrames

A count of frames for which transmission on a particular interface fails due to excessive collisions.

RFC1643

ETH-TxLateCollision

The number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet.

RFC1643

ETH-TxMultiCollisionFrames

A count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision.

RFC1643

ETH-TxNUcastPkts

The total number of packets that higher-level protocols requested be transmitted to a non-unicast (i.e., a subnetwork-broadcast or subnetwork -multicast) address, including those that were discarded or not sent.

RFC1213

ETH-TxOctets The total number of octets transmitted out of the interface, including framing characters.

RFC1213

ETH-TxSingleCollisionFrames

A count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision.

RFC1643

LAN

ETH-TxUcastPkts

The total number of packets that higher level protocols requested is transmitted to a subnetwork.

RFC1213

ETH-DropPkts A count of drop packets.

ETH-RxAlignmentErrorFrames

A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check

RFC1643

ETH-RxBroadcastPkts

Number of good broadcast packets received

ETH-RxFCSErrorFrames

A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check.

RFC1643

ETH-RxMulticastPkts

Number of good multicast packets received(excluding broadcast packets)

WAN

ETH-RxOctets The total number of octets received on the interface, including framing characters.

RFC1213



(3 of 3) MONITOR TYPES DEFINITION SPEC.

ETH-RxPkt1024toMax

Number of packets received that were between 1024 and the Mac_Pkt_Len octets in length (including error packets)

ETH-RxPkt128to255


ETH-RxPkt256to511


ETH-RxPkt512to1023


ETH-RxPkt64 Number of packets received that were 64 octets in length (including bad packets)

ETH-RxPkt65to127


ETH-TxNUcastPkts

The total number of packets that higher-level protocols requested be transmitted to a non-unicast (i.e., a subnetwork-broadcast or subnetwork -multicast) address, including those that were discarded or not sent.

RFC1213

ETH-TxOctets The total number of octets transmitted out of the interface, including framing characters.

RFC1213

WAN

ETH-TxUcastPkts

The total number of packets that higher level protocols requested is transmitted to a subnetwork.

RFC1213



Encapsulation PM


GFP_RxEXIErrorPkts

A count of received frame with HEAD errors.

GFP_RxFCSErrorPkts

A count of received frame with FCS errors.

GFP_RxOctets

A count of received octets.

GFP_RxPkts A count of received frame.

GFP_TxOctets

A count of transmitted octets.

GFP

GFP_TxPkts A count of transmitted frame.

LAPS_RxFCSErrorPkts

A count of received frame with FCS errors.

LAPS_RxOctets

A count of received octets.

LAPS_RxPkts

A count of received frame.

LAPS_TxOctets

A count of transmitted octets.

LAPS

LAPS_TxPkts

A count of transmitted frame.



3.4.1.2 Performance Counter Range

SDH PM Counter Range

PM TYPES 15m PM COUNTER RANGE 24h PM COUNTER RANGE

MEMORY RANGE MEMORY RANGE

OFS(RS) 2 Byte 0-900 4 Byte 0-86400

BBE 4 Byte 0-4294967295 4 Byte 0-4294967295

ES 2 Byte 0-900 4 Byte 0-86400

SES 2 Byte 0-900 4 Byte 0-86400

UAS 2 Byte 0-900 4 Byte 0-86400

FE-BBE 4 Byte 0-4294967295 4 Byte 0-4294967295

FE-ES 2 Byte 0-900 4 Byte 0-86400

FE-SES 2 Byte 0-900 4 Byte 0-86400

FE-UAS 2 Byte 0-900 4 Byte 0-86400

PSC 4 Byte 0-4294967295 4 Byte 0-4294967295

PSD 2 Byte 0-900 4 Byte 0-86400

PJE-P 4 Byte 0-4294967295 3 Byte 0-4294967295

PJE-N 4 Byte 0-4294967295 3 Byte 0-4294967295



Ethernet PM Counter Range

PM TYPES 15m PM COUNTER RANG 24h PM COUNTER RANG


ETH-TxOctet 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-RxOctet 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-RxFCSErrorFrame 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-RxAlignmentErrorFrame 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-TxUcastPkt 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-TxNUcastPkt 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-RxMulticastPkt 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-RxBroadcastPkt 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-TxSingleCollisionFrame 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-TxMultiCollisionFrame 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-TxDelayTransmission 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-TxExtCollisionFrame 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-TxLateCollisionFrame 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-TxCollisionFrame 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-RxPkt64 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-RxPkt65to127 4 Byte 0-4294967295 4 Byte 0-4294967295




ETH-RxPkt1024toMax 4 Byte 0-4294967295 4 Byte 0-4294967295

ETH-DropPkt 4 Byte 0-4294967295 4 Byte 0-4294967295



GFP PM Counter Range



GFP_TxPkt 4 Byte 0-4294967295 4 Byte 0-4294967295

GFP_TxOctet 4 Byte 0-4294967295 4 Byte 0-4294967295

GFP_RxPkt 4 Byte 0-4294967295 4 Byte 0-4294967295

GFP_RxOctet 4 Byte 0-4294967295 4 Byte 0-4294967295

GFP_RxFCSErrorPkt 4 Byte 0-4294967295 4 Byte 0-4294967295

GFP_RxEXIErrorPkt 4 Byte 0-4294967295 4 Byte 0-4294967295

LAPS PM Counter Range



LAPS_TxPkt 4 Byte 0-4294967295 4 Byte 0-4294967295

LAPS_TxOctet 4 Byte 0-4294967295 4 Byte 0-4294967295

LAPS_RxPkt 4 Byte 0-4294967295 4 Byte 0-4294967295

LAPS_RxOctet 4 Byte 0-4294967295 4 Byte 0-4294967295

LAPS_RxFCSErrorPkt 4 Byte 0-4294967295 4 Byte 0-4294967295

NOTE: When the PM value exceeds the maximum value in the range showed in all above

tables, the PM will be regarded as “overflow” and showed in PM monitor screen of CID.



3.4.1.3 SES

Two conditions cause SES defect. One is the ratio of error code in one second is 30% or more, the other is that one or more defects occur(s), which is shown in below table.

The Defects Causing Near End SES PATH LAYER NEAR END DEFECT CONDITION

LP UNEQ

LP TIM

TU LOP

TU AIS

HP LOM

LO path layer

HP PLM

HP UNEQ

HP TIM

AU LOP

HO Path layer

AU AIS

MST layer MS AIS

RS TIM

STM LOS

RST layer

STM LOF

The Defects Causing Far End SES PATH LAYER FAR END DEFECT CONDITION

LO path layer LP RDI

HO Path layer HP RDI

SES PM threshold is shown in below table.

Facility SES Threshold Value

VC11 600

VC12 600

VC3 2400

VC4 2400

RS 2400

MS 2400



3.4.1.4 Threshold Crossing Alert (TCA) Default Values

Threshold Crossing Alert (TCA) is set to almost every Performance Monitoring Parameter. It is used to detect when degradation of transmission has reached unacceptable levels. The TCA value of each parameter can be customized. The TCA report can be disabled as well, by setting the value to 0.

SDH TCA (1 of 2)

LAYER PM TYPES 15m TCA THRESHOLD 24h TCA THRESHOLD

DEFAULT RANGE DEFAULT RANGE

BBE 65535 0-65535 6291360 0-6291360

ES 900 0-900 86400 0-86400

SES 63 0-900 4095 0-86400

UAS 63 0-900 4095 0-86400

RS

OFS 900 0-900 86400 0-86400

BBE 65535 0-65535 6291360 0-6291360

ES 900 0-900 86400 0-86400

SES 63 0-900 4095 0-86400

UAS 63 0-900 4095 0-86400

FE-BBE 65535 0-65535 6291360 0-6291360

FE-ES 900 0-900 86400 0-86400

FE-SES 63 0-900 4095 0-86400

MS

FE-UAS 63 0-900 4095 0-86400

PSC 900 0-900 86400 0-86400 MSP

PSD 900 0-900 86400 0-86400

PJE-P 113184 0-113184 10865664 0-10865664 AU-4

PJE-N 113184 0-113184 10865664 0-10865664

BBE 65535 0-65535 6291360 0-6291360

ES 900 0-900 8640 0-86400

SES 63 0-900 4095 0-86400

VC-4

UAS 63 0-900 4095 0-86400



(2 of 2)



FE-BBE 65535 0-65535 6291360 0-6291360

FE-ES 900 0-900 86400 0-86400

FE-SES 63 0-900 4095 0-86400

VC-4

FE-UAS 63 0-900 4095 0-86400

BBE 65535 0-65535 6291360 0-6291360

ES 900 0-900 86400 0-86400

SES 63 0-900 4095 0-86400

UAS 63 0-900 4095 0-86400

FE-BBE 65535 0-65535 6291360 0-6291360

FE-ES 900 0-900 86400 0-86400

FE-SES 63 0-900 4095 0-86400

VC-3

FE-UAS 63 0-900 4095 0-86400

BBE 65535 0-65535 6291360 0-6291360

ES 900 0-900 86400 0-86400

SES 63 0-900 4095 0-86400

UAS 63 0-900 4095 0-86400

FE-BBE 65535 0-65535 6291360 0-6291360

FE-ES 900 0-900 86400 0-86400

FE-SES 63 0-900 4095 0-86400

VC-12/ VC11

FE-UAS 63 0-900 4095 0-86400

PJE-P 113184 0-113184 10865664 0-10865664 TU

PJE-N 113184 0-113184 10865664 0-10865664



Ethernet TCA

(1 of 2)



ETH-TxOctet 4294967294 0-4294967294 4294967294 0-4294967294

ETH-RxOctet 4294967294 0-4294967294 4294967294 0-4294967294

ETH-RxFCSErrorFrame 133929000 0-133929000 4294967294 0-4294967294

ETH-RxAlignmentErrorFrame

133929000 0-133929000 4294967294 0-4294967294

ETH-TxUcastPkt 133929000 0-133929000 4294967294 0-4294967294

ETH-TxNUcastPkt 133929000 0-133929000 4294967294 0-4294967294

ETH-RxMulticastPkt

133929000 0-133929000 4294967294 0-4294967294

ETH-RxBroadcastPkt 133929000 0-133929000 4294967294 0-4294967294

ETH-TxSingleCollisionFrame 133929000 0-133929000 4294967294 0-4294967294

ETH-TxMultiCollisionFrame

133929000 0-133929000 4294967294 0-4294967294

ETH-TxDelayTransmission

133929000 0-133929000 4294967294 0-4294967294

ETH-TxExtCollisionFrame

133929000 0-133929000 4294967294 0-4294967294

ETH-TxLateCollisionFrame

133929000 0-133929000 4294967294 0-4294967294

ETH-TxCollisionFrame 46875000 0-46875000 4294967294 0-4294967294

ETH-RxPkt64 133929000 0-133929000 4294967294 0-4294967294

ETH-RxPkt65to127

133929000 0-133929000 4294967294 0-4294967294

ETH-RxPkt128to255

76014000 0-76014000 4294967294 0-4294967294

ETH-RxPkt256to511

40760970 0-40760970 4294967294 0-4294967294

LAN

ETH-RxPkt512to1023

21146400 0-21146400 4294967294 0-4294967294



(2 of 2)



ETH-RxPkt1024toMax

10775700 0-10775700 4294967294 0-4294967294 LAN

ETH-DropPkt 133929000 0-133929000 4294967294 0-4294967294

ETH-TxOctet 4294967294 0-4294967294 4294967294 0-4294967294

ETH-RxOctet 4294967294 0-4294967294 4294967294 0-4294967294

ETH-RxFCSErrorFrame 133929000 0-133929000 4294967294 0-4294967294

ETH-RxAlignmentErrorFrame 133929000 0-133929000 4294967294 0-4294967294

ETH-TxUcastPkt 133929000 0-133929000 4294967294 0-4294967294

ETH-TxNUcastPkt 133929000 0-133929000 4294967294 0-4294967294

ETH-RxMulticastPkt

133929000 0-133929000 4294967294 0-4294967294

ETH-RxBroadcastPkt

133929000 0-133929000 4294967294 0-4294967294

ETH-RxPkt64 133929000 0-133929000 4294967294 0-4294967294

ETH-RxPkt65to127 133929000 0-133929000 4294967294 0-4294967294

ETH-RxPkt128to255

76014000 0-76014000 4294967294 0-4294967294

ETH-RxPkt256to511

40760970 0-40760970 4294967294 0-4294967294

ETH-RxPkt512to1023

21146400 0-21146400 4294967294 0-4294967294

ETH-RxPkt1024toMax

10775700 0-10775700 4294967294 0-4294967294

WAN

ETH-DropPkt 133929000 0-133929000 4294967294 0-4294967294



GFP TCA



GFP_TxPkt 4294967294 0-4294967294 4294967294 0-4294967294

GFP_TxOctet 4294967294 0-4294967294 4294967294 0-4294967294

GFP_RxPkt 4294967294 0-4294967294 4294967294 0-4294967294

GFP_RxOctet 4294967294 0-4294967294 4294967294 0-4294967294

GFP_RxFCSErrorPkt

133929000 0-133929000 4294967294 0-4294967294

Encapsulation

GFP_RxEXIErrorPkt

133929000 0-133929000 4294967294 0-4294967294

LAPS TCA



LAPS_TxPkt 4294967294 0-4294967294 4294967294 0-4294967294

LAPS_TxOctet 4294967294 0-4294967294 4294967294 0-4294967294

LAPS_RxPkt 4294967294 0-4294967294 4294967294 0-4294967294

LAPS_RxOctet 4294967294 0-4294967294 4294967294 0-4294967294

Encapsulation

LAPS_RxFCSErrorPkt

133929000 0-133929000 4294967294 0-4294967294



3.4.2 Display Current PM Status The current performance monitor (PM) data of NE can be retrieved and displayed.

NOTE: When PM value exceeds the content of PM register, CID reports “PM value overflow” in “Performance value” column.

Figure 3-11 shows an example where the current 15m PM data are listed.

Figure 3-11. PM Data Dialog Box

NOTE: Hereafter, a dialog box that lists the current PM data is referred to PM Data dialog box.

PM data

Tabs to switch current PM data list (15 minutes or 24 hours) and PM

data history (15 minutes or 24 hours)



3.4.2.1 Items in PM Data Dialog Box

The functions of the items in the PM Data dialog box are following:

ITEMS DESCRIPTION

column headers (on top) Sort PM data. By clicking a column header, the PM data in the list are sorted according to the selected subject.

Current 15m Data tab Switch the window for displaying a list of current 15-minute PM data.

Current 24h Data tab Switch the window for displaying a list of current 24-hour PM data.

History 15m Data tab Switch the window for displaying the history of 15-minute PM data.

History 24h Data tab Switch the window for displaying the history of 24-hour PM data.

Retrieve button The PM data are collected again by clicking this button.

Print button The PM data information is printed out by clicking this button.

Close button PM data browsing is quitted (closing the dialog box) by clicking this button.

Don’t Display Zero Value check box

Select this check box not to display the PM whose value is zero. This is selected by default.

All check box Specifies whether to list the PM data of all the boards and ports or those of a certain type board/port by clicking this check box. When this is selected (leaving a tick), the PM data in all boards are listed. When this is not selected (not leaving a tick), only the alarms in certain-type boards and ports are listed. This check box must be unselected for viewing the PM history. This is selected by default.


When the All check box is unselected (leaving empty), the following display options are available:

ITEMS DESCRIPTION

Board Select the board type from the drop-down list.

Port Type Select the port type from the drop-down list.





3.4.2.3 Procedure: View Current 15-Minute PM Data

Perform the following procedure to view a list of the current 15m PM data:



3. Perform one of the following two procedures:

Select Current PM from the Performance menu.


4. The PM Data dialog box listing the current 15m PM data shown in Figure 3-12 appears:

Figure 3-12. Performance View ⎯ Current 15m PM Data



5. In this dialog box, perform one of the following:

To view the current 15m PM data list using the display option, refer to 3.4.2.5 View Current PM Data Using Display Options.

To update the current 15m PM data list, click the Retrieve button.

To print out the current 15m PM data list, click the Print button.

To view the current 24h PM data list, click the Current 24h Data tab. Refer to 3.4.2.4 Procedure: View Current 24-Hour PM Data for details.

To view the PM data history, click the History 15m Data or History 24h Data tab. Refer to 3.4.3 Display History PM Data for details.

To finish viewing, click the Close button.




3.4.2.4 Procedure: View Current 24-Hour PM Data

Perform the following procedure to view a list of the current 24h PM data:



3. Select Current PM from the Performance menu or click the shortcut button. The PM Data dialog box shown in Figure 3-12 appears.

4. Click the Current 24h Data tab on the dialog box to switch the window. Figure 3-13 shows an example where the Current 24h Data tab is selected:

Figure 3-13. Performance View ⎯ Current 24h Data

Current 24h Data tab



5. In this dialog box, perform one of the following:

To view the current 24h PM data list using the display option, refer to 3.4.2.5 View Current PM Data Using Display Options.

To update the current 24h PM data list, click the Retrieve button.

To print out the current 24h PM data list, click the Print button.

To view the current 15m PM data list, click the Current 15m Data tab. Refer to 3.4.2.3 Procedure: View Current 15-Minute PM Data for details.

To view the PM data history, click the History 15m Data or History 24h Data tab. Refer to 3.4.3 Display History PM Data for details.

To finish viewing, click the Close button.




3.4.2.5 View Current PM Data Using Display Options

When the PM Data dialog box is opened for the first time, the All check box is selected by default to display all the current 15m PM data within the equipment. The current PM data to be displayed, however, can be specified by using the display options. Refer to the subsection 3.4.2.2 Display Options for detailed information on the display options.

Perform the following procedure to select the current PM data to be displayed in the list:

Procedure:

1. Unselect the All check box by clicking. The window shown in Figure 3-14 appears:

Figure 3-14. Performance View ⎯ Current 15m Data (Clear All Check Box)

click to unselect.



Figure 3-15. Performance View ⎯ Current 24h Data (Clear All Check Box)



4. Click the Retrieve button. The current PM data that correspond to the selection above are displayed.


NOTE: 1. To display all the current PM data after specifying the current PM data to be

displayed, click the All check box to select it again and click the Retrieve button.

2. Selection/unselection of the All check box is valid even after the window is switched by clicking the Current 15m Data/Current 24h Data tab for viewing the list of the current 15-minute/24-hour PM data or the 15-minute/24-hour PM data history.

click to unselect.



3.4.3 Display History PM Data The history of performance monitor (PM) data of NE can be retrieved and displayed. When browsing history PM data, the All check box is not available.

Figure 3-16 shows an example where the history of the 15m PM data is displayed.

Figure 3-16. PM History Dialog Box

NOTE: Hereafter, a dialog box that lists the PM data history is referred to as PM History dialog box.

PM history data Tabs to switch the current PM data list (15 minutes or 24 hours) and PM data history (15 minutes or 24 hours)



3.4.3.1 Items in PM History Dialog Box

The functions of the items in the PM History dialog box are following:

ITEMS DESCRIPTION

column headers (on top) Sort PM data. By clicking a column header, the PM data in the list are sorted according to the selected subject.

Current 15m Data tab Switch the window for displaying a list of current 15-minute PM data.

Current 24h Data tab Switch the window for displaying a list of current 24-hour PM data.

History 15m Data tab Switch the window for displaying the history of 15-minute PM data.

History 24h Data tab Switch the window for displaying the history of 24-hour PM data.

Retrieve button The PM data are collected again by clicking this button.

Print button The PM data information is printed out by clicking this button.

Close button PM data browsing is quitted (closing the dialog box) by clicking this button.

Don’t Display Zero Value check box

Select this check box to display all the PM data on the screen. This is selected by default.


ITEMS DESCRIPTION

Board Select the board type from the drop-down list.

Port Type Select the port type from the drop-down list.





3.4.3.3 Procedure: View History 15 Minute PM Data

Perform the following procedure to view history 15m PM data:



3. Select History PM from the Performance menu. The PM History dialog box appears, showing history 15m PM data.

NOTE: The PM History dialog box can also be displayed by clicking the History 15m Data tab on the PM Data dialog box.

Figure 3-17. Performance View ⎯ History 15m Data

NOTE: AU_PORT History PM of FE board only can count for 4 hour data.

History 15m Data tab






7. Click the Retrieve button. History 15m PM data that corresponds to the selection above is displayed.

8. In this dialog box, the following options are also available:

To print out history 15m PM data, click the Print button.

To view history 24h PM data, click the History 24h Data tab. Refer to 3.4.3.4 Procedure: View History 24-Hour PM Data for details.

To view the current 15m/24h PM data list, click the Current 15m Data or Current 24h Data tab. Refer to 3.4.2 Display Current PM Status for details.

9. To finish viewing, click the Close button.


NOTE: Selection/unselection of the All check box is valid even after the window is switched by clicking the History 24h Data/Current 15m Data/Current 24h Data tab for viewing the 24h PM data history or the list of the current 15-minute/24-hour PM data.



3.4.3.4 Procedure: View History 24-Hour PM Data

Perform the following procedure to view history 24h PM data:


2. Open the management dialog box of the target NE. Detailed operation is provided in the CH07. Working with CID of the F4798_Q09 CID OPERATING GUIDE manual.

3. Select History PM from the Performance menu. The PM History dialog box appears, showing history 15m PM data.

4. Click the History 24h Data tab. The PM History dialog box displays history 24h PM data.

NOTE: The PM History dialog box for 24h PM data can also be switched from the PM Data dialog box by clicking the History 24h Data tab.

Figure 3-18. Performance View ⎯ History 24h Data

History 24h Data tab






8. Click the Retrieve button. History 24h PM data that corresponds to the selection above is displayed.

9. In this dialog box, the following options are also available:

To print out history 24h PM data, click the Print button.

To view history 15m PM data, click the History 15m Data tab. Refer to 3.4.3.3 Procedure: View History 15 Minute PM Data for details.

To view the current 15m/24h PM data list, click the Current 15m Data or Current 24h Data tab. Refer to 3.4.2 Display Current PM Status for details.



NOTE: Selection/unselection of the All check box is valid even after the window is switched by clicking the History 15m Data/Current 15m Data/Current 24h Data tab for viewing the 15m PM data history or the list of the current 15-minute/24-hour PM data.



3.4.4 PM Counter Reset The performance of the equipment can be reset via the Performance Counter Reset dialog box. Figure 3-19 shows an example:

Figure 3-19. Performance Counter Reset Dialog Box



3.4.4.1 Items in Performance Counter Reset Dialog Box

ITEMS DESCRIPTION

Performance Source Select the operating object for which the PM counter should be reset.

Performance Name Select the performance name that needs to be reset.

15m Performance Counter Select the 15m PM counter. NOTE: This item already is selected by

CID, and CID displays grey in the screen.

Counter Type

24h Performance Counter Select the 24h PM counter. NOTE: This item already is selected by

CID, and CID displays grey in the screen.

Reset All check box When this check box is selected (leaving a tick), all the operating objects will be reset.

Set button Send the specified settings to the NE.

Close button Quit the PM counter reset operation (closing the dialog box).



3.4.4.2 Procedure: Execute PM Counter Reset

Perform the following procedure to reset the PM counter.



3. Select PM Counter Reset from the Performance menu. The Performance Counter Reset dialog box shown in Figure 3-19 appears.

4. Select the operating object for which the PM counter should be reset from the Performance Source tree in the left window.

5. Select the performance name that needs to be reset from the Performance Name list box in the right window. In this list, only the performance names that are relevant to the operating object selected in Step 4 are displayed.

6. Confirm the setting, then click the Set button to send the data to NE.

7. To reset all the operating objects, click the Reset All check box (leaving a tick).

8. Click the Close button to finish the PM counter reset operation.

NOTE: If the Close button is clicked without clicking the Set button, the Performance Counter Reset dialog box is closed ignoring the setting.




3.4.5 Display Threshold Crossing Alert (TCA) The TCA values can be displayed in the PM Item Setup dialog box. Perform the following procedure.

NOTE: TCA values can also be modified via the PM Item Setup dialog box. Refer to 9. Parameter Change; 9.6.1 Modifying PM Items in the F4798_Q10 PROVISIONING manual for details.

Procedure: 1. Start up the CID, and log in to the target NE.


3. Select PM Item Setup from the Performance menu. The PM Item Setup dialog box shown in Figure 3-20 appears:

Figure 3-20. PM Item Setup Dialog Box

4. After viewing, click the Close button.



Retrieve Information ⎯ Hardware Inventory and LED Status 3-53

3.5 Hardware Inventory and LED Status

3.5.1 Display Hardware Information and LED Status Information on the installed boards and its LED status can be displayed in the NE management dialog box. Perform the following procedure to open the management dialog box of the target NE:

Procedure:

1. Start up the CID, and log in to the target NE. The CID retrieves the configuration information data on the equipment during logging in.

2. When the CID main window shown in Figure 3-21 is displayed, click or double the target NE in the window, then double click it:

Figure 3-21. CID Main Window

Click or double-click to select the target NE, then double-click it.


Retrieve Information ⎯ Hardware Inventory and LED Status 3-54

3. The NE management dialog box shown in Figure 3-22 appears:

Figure 3-22. NE Management Dialog Box

Information on the installed boards and its LED status are displayed. In this dialog box, the target NE type of the equipment, working mode and alarm conditions are also displayed.



Retrieve Information ⎯ Firmware Version 3-55

3.6 Firmware Version

The information on the firmware installed in an NE can be retrieved.

3.6.1 Procedure: Retrieve Installed Firmware Version



3. Select Upgrade F/W and FPGA from the Maintenance menu. The Upgrade F/W and FPGA dialog box shown in Figure 3-23 appears:

Figure 3-23. Upgrade F/W and FPGA Dialog Box

4. Select the corresponding equipment from the tree structures on the left of the Upgrade F/W and FPGA dialog box.

5. Click the Version radio button in the Operation Option field.

6. Click the OK button to retrieve the firmware version.

7. Click the Close button to finish viewing the firmware version.



Retrieve Information ⎯ Logged-in Users 3-56 E

3.7 Logged-in Users

Perform the following to list up the logged-in users.

3.7.1 Procedure: Retrieve Logged-in Users List

1. Start up the CID, and log in to an NE.


3. Select User Management from the Security menu. The User Management dialog box shown in Figure 3-24 appears:

Figure 3-24. User Management Dialog Box

Clicking the Retrieve button retrieves the logged-in user list.




Routine Maintenance ⎯ Check LED Operation on All Boards 4-1

4. ROUTINE MAINTENANCE

4.1 Check LED Operation on All Boards 4.1.1 Target Boards

All boards managed by the Mainboard within the equipment.

4.1.2 Procedure: Verify LEDs on Front Panel of C-Node From the front panel, three LEDs labeled as PWR, ALM and OW respectively indicate the status of power, alarm, and order wire phone. Figure 4-1 shows the front view of C-Node.

ALMf PWR OW ACO OW

Figure 4-1. Front View of C-Node

LED condition of front panel of C-Node is shown in Table 4-1.

Table 4-1. LED Condition on Front Panel

Name Condition On: Normal Operation (Power on) PWR

Off: Power off

On: Alarm Condition Blink: In start up process

ALM

Off: Normal Operation (No Alarm Condition)

On: Using order wire Blink: Calling

OW

Off: Normal Operation (Not using order wire)



Procedure

1. Turn on power of the NE. Verify that the power LED (green) on the left of the face light up.

2. If there is (are) alarm(s) occur in the equipment, the alarm LED (red) on the left of the face should light up. The LED should shut down after the alarm(s) disappear.

3. If the OW phone(TEL SET) is picked off, the LED (green) on the right of the face should light up. The LED should flash quickly when dial a number or the OW is called. The LED should shut down after the dialing is over.


4.1.3 Procedure: Verify LEDs on 100Base-T/100Base-T2 Tributary Board

Figure 4-2 shows the front view of 4-port 100Base-T/100Base-T2 Tributary Board

12Console 34

Figure 4-2. View of 100Base-T/100Base-T2 Tributary Board

LED condition of 100Base-T/100Base-T2 board is shown in Table 4-2.

Table 4-2 . LED Condition of 100Base-T/100Base-T2 Board

Name Condition

Rate Off: 10Mbps On: 100Mbps

Data Off: Link down On: Link up but no data transmission Blink: Data transmission

Procedure

1. Connect PC or other terminal equipment by using UTP cable.

2. When link up condition is detected at LAN port, Data LED (green) turns on. And if data communication rate is 100Mbps, Rate LED turns on.

Rate Data



3. After starting data communication, Data LED (green) blinks.


4.1.4 Procedure: Verify LEDs on Board by CID

1. Connect NE with CID.

2. In NE management window, if no alarm occurs in the equipment, LEDs' color of installed board is green. If any alarm(s) occurs in the equipment, the LEDs' color of corresponding board becomes other colors except green. Which color is shown is decided by occurring alarm class. After the alarm(s) disappear(s), the LEDs become green again.



Routine Maintenance ⎯Check FAN 4-4 E

4.2 Check FAN

If a fan fails, the temperature within the shelf may go up, which affects the equipment operation. Since the life of a fan is limited, fans installed in the shelf should be replaced approximately within 3 years for preventive maintenance.

NOTE: For FAN cleaning and replacing, fan removing time should be less than 24h because long time fan removing may cause equipment temperature increase and damage performance.

4.2.1 Apparatus Antistatic wrist strap A new fan, if required. Vacuum cleaner, cotton swabs, brush, etc. (do not use chemical agents or detergents for cleaning)

4.2.2 Procedure: Verify FAN Once the FAN is inserted into subrack and it will run all the time. There are three LEDs which labeled as PWR, ALM and OW on the front panel of C-Node respectively. These LEDs indicate the status of power, alarm, and order wire phone. If any alarm(s) occurs in the equipment, including the FAN etc, the LED’s color of ALM will become red. You can refer following procedure to verify if the FAN occurs alarm. In CID NE management window, if any alarm occurs in the FAN, the FAN_FAIL alarm will be displayed in the Alarm Monitor Dialog Box. As following figure shows:


Hardware Replacement 5-1

5. HARDWARE REPLACEMENT This section provides steps to replace hardware installed in C-Node equipment while in service. The Mainboard, which manages the equipment, especially requires special precautions and methods when it is replaced.

CAUTION To prevent the equipment from getting damages, be sure to wear anti-static wrist strap connected to the ESD terminal. - Put on gloves when touching boards. - When storing a spare board, put it into an antistatic bag and

place it in an antistatic environment. - Ensure that all testing equipment, instrument, computer, etc.,

are connected to shielded ground and static ground reliably.


Hardware Replacement ⎯ Replace Cables 5-2

5.1 Replace Cables

This subsection provides procedures to remove/replace cables connected at C-Node equipment. While in service, removal of cables requires special precautions.

5.1.1 Precautions Confirm there is no traffic in cable.

5.1.2 Apparatus

CID

New Cable for replacement

5.1.3 Procedure: Disconnect Cables

1. Pull out the cable which need to be replaced.

2. Clean the optical connector.


5.1.4 Procedure: Connect Cables

1. Connect the new optical cable to the equipment.

2. Check the new cable to confirm whether the connection is credible.



Hardware Replacement ⎯Board 5-3

5.2 Board

This subsection provides procedures to remove/replace board of the C-Node equipment. While in service, removal of board requires special precautions.

5.2.1 Precautions Confirm there is no traffic in board.

CAUTION

To prevent any damage to Power board, when Mainboard is removed or inserted, be sure to turn off the switch on Power board.

CAUTION

To prevent unexpected error on data transmission, before 34M/45M subboard is removed or inserted, reset switch on Mainboard must be operated. After reset operation, replacement of 34M/45M subboard must be finished within 45 seconds.


Hardware Replacement ⎯ Board 5-4

5.2.2 Apparatus

CID

New board for replacement

5.2.3 Procedure: Replace Board

1. Delete all the configurations on the board which need to be replaced.

2. Pull out the board.

3. Insert the new board.

4. Make new configuration to the board.



Hardware Replacement ⎯SFP Module 5-5

5.3 SFP Module

This subsection provides procedures to remove/replace SFP module of the C-Node equipment. While in service, removal of SFP module requires special precautions.

5.3.1 Precautions Confirm there is no effect on traffic.

5.3.2 Apparatus

CID

New module for replacement

5.3.3 Procedure: Replace SFP Module

NOTE: Since SFP module support hot-plugging, you can replace it directly.

Replacing a SFP module with another of the same type

1. Disconnect the cable from SFP interface.

2. Replace a new SFP module with another of the same type directly.

3. Reconnect the cable to the SFP interface.

4. Check the alarms related SFP module and fiber (LOS, LOF, MS-EXC, MS-DEG, PKG_TYPE and so on).

5. If these alarms occurring, please confirm whether the SFP module and fiber mounted correctly referring trouble clearing.



Hardware Replacement ⎯ SFP Module 5-6

Replacing a SFP module with another of the different type

6. Delete all the configurations on the mainboard/subboard which need to be replaced.

7. Configure the mainboard/subboard type as the correct package type from CID, the detail package types are shown as below table:

Category Package type MAIN4OD MAIN4OS MAIN1OD MAIN1OS MAIN1ED

Mainboard

MAIN1ES STM4_S

STM1O_D STM1O_S STM1E_D

Subboard

STM1E_S

NOTE: The detail operation refers to section 4.2.3 Setup Physical Slot Configuration of F4798_Q10 PROVISIONING manual.

8. Disconnect the cable from SFP interface.

9. Replace the old SFP module with the spare module.

NOTE: The detail operation refers to section 4.2 Install/Extract SFP Module of F4798_Q07 MAIN/SUB BOARD DESCRIPTION/INSTALLATION manual.

10. Replace the cable to adapt the new SFP module and connect this cable to SFP connector.

11. Check the alarms related SFP module and cable (LOS, LOF, PKG_TYPE and so on).

12. If these alarms occurring, please confirm whether the SFP module and cable mounted correctly referring trouble clearing.

13. Reconfigure the board.



Hardware Replacement ⎯ Power Board 5-7

5.4 Power Board

This subsection provides procedures to remove/replace power terminal of the C-Node equipment. While in service, removal of power terminal requires special precautions.

5.4.1 Precautions Confirm there are no power supply to power board.

CAUTION

During replacement work of power board, power supply to the equipment should keep turn off.

5.4.2 Apparatus

CID

New Power board for replacement

5.4.3 Procedure: Replace Power Board

1. Turn off the power of the equipment.

2. Remove power cable.

3. Replace power board.

4. Connect power cable

5. Turn on the power of equipment.



Hardware Replacement ⎯ Fuse of Power Board 5-8

5.5 Fuse of Power Board

This subsection provides procedures to replace fuse of power board of the C-Node equipment.

CAUTION Attached Fuse is used only for C-Node.

5.5.1 Precautions

Confirm that power board has already turned off.

5.5.2 Apparatus

New fuse for replacement

Antistatic wrist strap

5.5.3 Procedure: Replace Fuse of Power Board

For one port power board

1. Turn off power, and extract power board from subrack.

2. Unscrew the fuse cap, and take out the old fuse.

3. Put the new fuse in the fuse cap.

The fuse on the power board


Hardware Replacement ⎯ Fuse of Power Board 5-9

4. Screw the fuse cap.

5. Insert the power board to subrack, and turn on the power.


For two port power board

1. Turn off power, and extract power board from subrack.

2. Fix the power board by one hand.

3. Take out the old fuse by another hand.

4. Insert the new fuse into specified slot.

5. Insert the power board to subrack, and turn on the power.


The fuse on the power board


Hardware Replacement ⎯FAN 5-10 E

5.6 FAN

This subsection provides procedures to remove/replace fan of the C-Node equipment. While in service, removal of fan requires special precautions.

NOTE:

1) For FAN cleaning and replacing, fan removing time should be less than 24h because long time fan removing may cause equipment temperature increase and damage performance.

2) For guaranteeing the FAN board working normally, you should replace it every 3 years.

5.6.1 Precautions Confirm there are no operations in service.

5.6.2 Apparatus

CID

New Fan board for replacement

5.6.3 Procedure: Replace FAN

1. Delete all the configurations on the fan which need to be replaced.

2. Pull out the fan.

3. Insert new fan.

4. Make new configuration to the fan.



Equipment Maintenance 6-1

6. EQUIPMENT MAINTENANCE

This section provides the maintenance information and procedures related to the equipment and equipment configuration.


Equipment Maintenance ⎯ Database Upload/Download 6-2

6.1 Database Upload/Download

When the configuration of a C-Node is completed, all the configuration information on that equipment can be saved by the database upload function. After this, these configurations can be conveniently sent to another C-Node, which needs to set up its configuration, by the database download function without needing repeat the configuration setup for it.

NOTE: Do not download Database of release 3.5 and earlier because they are not compatible.

6.1.1 Database List The configuration database items that can be uploaded/downloaded are listed in the following table in alphabetical order. These are listed in the Database Select text box of the Database Upload/Download dialog box (see Figure 6-1).



Database Items

NE Attribute Tab Common Performance Attribute Tab Environment Control Output Port Config Tab RIP Config Tab Slot Config Tab Physical Port Config Tab Static Route Tab SDH/PDH Service Interface Config Tab SDH MSP Group Config Tab SDH MSP Config Tab Higher Order Path Cross-Connect Config Tab Higher Order Service TimeSlot (J1) Config Tab SDH Lower Order TimeSlot Config Tab System Timing Source Tab ByPass Timing Source Tab Clock Path Info Config Tab 2M bit/Hz Output State & SAN bit Tab Power Port/Fan port/Environment Port Alarm Type Config Tab Digital Performance Type Config Tab User Information Tab IP\RS232\DCC Config Tab OWH_ATTR DATA_CHANNEL TRUNK_FE VLAN_FE Mac Filter of FE Bandwidth_FE Port_FE Board_FE STP_FE Encapsulation_FE HKA/HKC Name



6.1.2 Procedure: Upload/Download Database Perform the following procedure to upload/download the database:



3. Select Database Upload/Download from the File menu. The Database Upload/Download dialog box shown in Figure 6-1 appears:

Figure 6-1. Database Upload/Download Dialog Box

4. When downloading database, a database folder to which the database is to be saved must be selected first. Perform the following procedure:

1) Click the Browse button on the right of the DataBase Folder Select field to open the Work Path Select dialog box shown in Figure 6-2.



Figure 6-2. Work Path Select Dialog Box

2) Select a desired directory from the tree structure on the left of the dialog box. The path of the selected folder (directory) will be displayed in the upper field.

3) Click the OK button. The Work Path Select dialog box is closed and the Database Upload/Download dialog box appears again, with the selected directory entered in the DataBase Folder Select field.

5. In the Operation field, select the operation mode Upload or Download radio button.

6. Select the databases to be uploaded or downloaded in the Database Select text box. The left text box lists all the databases, and the right text box will list the selected databases. Perform one of the following procedures to select the database to be uploaded/downloaded:

• Click a database in the left text box (a selected database name will be highlighted), then click the > button. The target database moves to the right text box.

• Double-click a database in the left text box. The target database moves to the right text box.

• To select all the databases at once, click the >> button. It is not necessary to select any database in this event.



NOTE:

1. The selected databases once moved into the right text box can be returned to the left text box. Select database(s) in the right text box (selected databases will be highlighted), then click the < button. All the databases in the right text box can be moved into the left text box by clicking the << button without selecting any databases.

2. When you download Database by Remote access via DCC, please execute it according to the following procedure.

1) Please execute the following setting by local beforehand.

# Slot config Tab

# Phsical Port Config Tab

# IP/RS232/DCC Config Tab

# OSI Config Tab(In the case of TCP/IP, this setting is unnecessary.)

2) After execute the above setting, please except the above setting from the target of download, and execute download Database. Please refer to following figure.

(Physical Port Config Tab is chosen, and if it is moved to the left window, above # mark in connection with a DCC setup moves to the left window together.)

Figure 6-3. Download Database by Remote access via DCC

7. Confirm that the specified operation (upload/download) and selected databases to be uploaded/downloaded are correct, then click the Start button.



8. Then the confirmation dialog box appears, asking whether to actually execute the uploading/downloading operation. Click the OK button.

9. When the updating/downloading operation is completed, a message box appears displaying whether the operation has been successfully finished or not.



Equipment Maintenance ⎯Equipment Reset 6-8

6.2 Equipment Reset

After modifying the IP parameter, OSI parameter or the DCC parameter (see 7.2 IP Parameter Setup in the F4798_Q10 PROVISIONING manual for details), it is necessary to reset the equipment.

NOTE: Equipment reset operation will cause TCA, PPS, MSP and Timing Source Switch events clear and CID communication down.

6.2.1 Procedure: Execute Equipment Reset Perform the following procedure to reset the equipment:



3. Select Equipment Reset from the Maintenance menu. The Equipment Reset dialog box shown in Figure 6-4 appears:

Figure 6-4. Equipment Reset Dialog Box


Equipment Maintenance ⎯Equipment Reset 6-9

4. Select the equipment, board, or port to be reset in the Device Select tree structure on the left of the dialog box.

5. Confirm that the selected equipment/board/port is correct, then click the Reset button. The confirmation dialog box shown in Figure 6-5 appears:

Figure 6-5. Confirmation Dialog Box for Equipment Reset

6. Click the OK button to perform equipment reset.

NOTE: Clicking the Cancel button instead of the OK button closes the confirmation dialog box and the Equipment Reset dialog box appears again.

7. The equipment restarts automatically. It takes about 60 to 90 seconds for equipment restart.

NOTE: The communication between CID and NE will be shut down during restarting.



Equipment Maintenance ⎯Equipment Initialization 6-10

E

6.3 Equipment Initialization

Perform the following procedure to reset the equipment:



3. Select Equipment Initialization from the Maintenance menu. The Equipment Initialization dialog box shown in Figure 6-6 appears:

Figure 6-6. Equipment Initialization Dialog Box

4. Click the OK button to perform equipment initialization. The equipment will restart automatically. Click the Close button to quit equipment initialization.

NOTE: Equipment initialization will delete all configuration of NE. Users should be very caution before initializing equipment.



Traffic Maintenance 7-1

7. TRAFFIC MAINTENANCE

This section provides the maintenance information and procedures related to traffics.

Traffic maintenance should be carried out by a maintenance personnel to assure or inspect the quality of the traffic.

The tasks provided in this section are not arranged in any specific order.


Traffic Maintenance ⎯ Loopback 7-2

7.1 Loopback

7.1.1 Description

Loopback function allows fault isolation and pre-service operation practice. Performing loopback interrupts the flow of traffic, and changes the normal transmission. Therefore, the use of loopback as routine practice is not recommended.

When the loopback is executed, the system generates an alarm indication signal, and sends it to the far-end NE.

See the following for other features of the loopback:

The loopback can be executed on every path.

Alarms in the path layer are masked during the loopback operation.

NOTE: When Remote check box of CID is checked at login screen, loopback control for SDH interface from CID is rejected. Though CID does not show any information box, making loopback in remote login will lead communication down

CAUTION

When using F port to remote login and selecting Remote at Login screen, please don't operate SDH interface Loopback setting. The setting might not be relieved because you disconnect to remote and can not login again.

CAUTION

Performing loopback interrupts the flow of traffic, and changes the normal transmission.



7.1.2 Loopback Statuses There are the following three kinds of loopback status:

LOOPBACK STATUS DESCRIPTION

Facility loopback Incoming signals from other equipment is looped back to the signal source without any management.

Terminal loopback Signals are looped back without sending to other equipment.

Non loop Signals go straight without any loopback.

7.1.3 Procedure: Setup Loopback



3. Select Loopback Control from the Maintenance menu. The Loopback Control dialog box shown in Figure 7-1 appears:

Figure 7-1. Loopback Control Dialog Box



4. Select a port for which loopback is to be executed from tree structures in the left window (selected ports will be highlighted).

5. Click the Retrieve button to send the loopback data information of the selected port to the CID.

6. Click a port in the Loopback Status field. Its loopback status switches

(Facility) → (Terminal) → (Non Loop) by clicking.

NOTE:

1) A same loopback status can be specified for all the paths on a certain slot position by clicking the corresponding button in the All field.

2) When execute or release loopback to the WAN side of 100BASE-T(2) at the time of the STP Action is enabled, the main signal of 100BASE-T(2) is turned off. If this phenomenon was occurred, please remove 100BASE-T(2) PKG or execute soft reset for 100BASE-T(2) PKG.

7. Click the Set button. The specified loopback settings will be sent to the NE.

8. Click the Close button to finish the loopback setup operation.



Traffic Maintenance ⎯Crossconnect Maintenance 7-5

7.2 Crossconnect Maintenance

The procedures regarding the crossconnect maintenance operations are provided in the F4798_Q10 PROVISIONING manual.

Procedure


2. Open the management dialog box of the target NE.

3. Select Cross Connect Configuration from the Configuration menu. The Cross Connect Configuration dialog box shown in Figure 7-2 appears:

Figure 7-2. Cross Connect Configuration Dialog Box

4. Choose the Delete radio button, delete the crossconnect that need to be modified at the destination side.

NOTE: When this is selected, Multi-TS is disabled.

5. Configure the new crossconnect.


Traffic Maintenance ⎯Protection 7-6

NOTE: In the latest release, VC-12, VC-3 and VC4 crossconnect function are all supported.


7.3 Protection

C-Node supports two kinds of protections: MSP (multiplex section protection) and SNCP (sub-network connection protection).

7.3.1 MSP

7.3.1.1 Action Mode

C-Node supports MSP in action mode: 1+1 Uni-directional Non-revertive Linear Protection. The following illustration shows 1+1 Unidirectional Linear Protection Operation. Only receive side is switched by line failure.

Figure 7-3 1+1 Unidirectional Linear Protection Operation

Following tables show some kinds of MSP settings.

Case1: primary/backup ports on Mainboard



Tributary:2M/34M/45M/STM-1o(e) Mainboard Aggregate Mainboard

slot1 slot2 slot3 slot4

slot1 slot3 STM-4oD OK OK OK OK

slot2 slot4 STM-1o(e)D OK OK OK OK

Red line means MSP setting.

Case2: primary/backup ports on same subboard. Mainboard does not use.

Tributary:2M/34M/45M/STM-1o(e) Mainboard

Aggregate Mainboard


STM-N slot3 STM-1o(e)D OK OK OK

slot2 slot4 STM-1o(e)D OK OK OK

Red line means MSP setting. STM-1o(e)D OK OK OK

STM-1o(e)D OK OK OK

ST-N subboard in different slot

7.3.1.2 Switching Criterion

Item Switching

requirement Monitor place B2ERR_HIGH SF Line (Work / Prot) B2ERR_LOW SD Line (Work / Prot)

LOS SF Line (Work / Prot) LOF SF Line (Work / Prot)

MS-AIS SF Line (Work / Prot) RS-TIM* SF Line (Work / Prot)

*: J Byte must be enabled in order to make TIM function be a switch criterion.



7.3.1.3 External Commands

Command Term Content Lockout of protection LKOP Protection line is forbidden to use

unconditionally. Lockout of working LKOW Working line is forbidden to use

unconditionally. Forced switch to protection FSP If the command is set on working line, the

traffic will be switched to protection line unconditionally.

Forced switch to working FSW If the command is set on protection line, the traffic will be switched to working line unconditionally.

Manual switch to protection MSP If the command is set on working line and protection line is in normal status, the traffic will be switched to protection line.

Manual switch to working MSW If the command is set on protection line and working liner is in normal status, the traffic will be switched to the working line.

7.3.1.4 Command Priority LKOP>LKOW>FSW>FSP>SF on Prot>SF on Work>SD on Prot>SD on Work> MSW>MSP

7.3.1.5 Switch Status MSP switch status is given in MSP Configuration windows of CID. In order to setup MSP configuration, please refer to the section 4.4 Setup MSP Configuration in manual F4798_Q10 PROVISIONING for detail information.

In MSP Configuration windows, read only edit box Status give the MSP status. If C-Node works on working line, it shows Normal as in Figure 7-4; If C-Node works on protection line, it shows Switch as in Figure 7-5.



Figure 7-4. MSP in Normal Status

Figure 7-5. MSP in Switch Status



7.3.2 SNCP

7.3.2.1 Action Mode C-Node supports SNCP in action methods: 1+1 Uni-directional Non-Revertive/ Revertive and monitor methods: SNC/I (Sub-Network Connection Protection with Inherent Monitoring) and SNC/N (Sub-Network Connection Protection with Non-intrusive Monitoring).

NOTE: C-Node supports both SNC/N and SNC/I in SNCP ring configuration, according to the following table.

1008*1008 cross-connect moduleSubboard Slot 1 Slot 2 Slot 3 Slot 4

32 * E12 (2M) SNC/N SNC/N SNC/N SNC/N

8 * E12 (2M) SNC/N SNC/N SNC/N SNC/N

STM-1o SNC/I SNC/I SNC/I SNC/I

STM-1e SNC/I SNC/I SNC/I SNC/I

STM4_S SNC/I SNC/I SNC/I SNC/I

2*100Base-T SNC/I SNC/I SNC/I SNC/I

4*100Base-T SNC/I SNC/I SNC/I SNC/I

3*E31 (34M) SNC/I SNC/I SNC/I SNC/I

3*E32 (45M) SNC/I SNC/I SNC/I SNC/I

Following tables show some kinds of PPS settings.

Case1: primary/backup ports on Mainboard

Tributary:2M/34M/45M/STM-1o(e) Mainboard Aggregate Mainboard slot1 slot2 slot3 slot4

slot1 slot3 STM-4oD OK OK OK OK slot2 slot4 STM-1o(e)D OK OK OK OK

Red line means PPS setting.



Case2: primary/backup ports on same subboard. Mainboard does not use.


Aggregate Mainboard slot1 slot2 slot3 slot4

STM-N slot3 STM-1o(e)D OK OK OK

slot2 slot4 STM-1o(e)D OK OK OK

Red line means PPS setting. STM-1o(e)D OK OK OK

STM-1o(e)D OK OK OK

STM-N subboard in different slot Case3: one of primary/backup ports on Mainboard, the other one on subboard

Tributary:2M/34M/45M/STM-1o(e) Mainboard Aggregate Mainboard


STM-N slot3 STM-1(4)o/1o(e) OK OK OK

slot2 slot4 STM-1(4)o/1o(e) OK OK OK


STM-1(4)o/1o(e) OK OK OK

STM-1(4)o/1o(e) OK OK OK

STM-N subboard in different slot Case4: one of primary/backup ports on subboard, the other one on another subboard.

Mainboard does not use.


Aggregate Mainboard slot1 slot2 slot3 slot4

STM-N slot3 STM-1o(e)D OK OK

STM-N slot4 STM-1o(e)D OK OK


STM-1o(e)D OK OK

STM-1o(e)D OK OK

STM-1o(e)D OK OK

STM-1o(e)D OK OK

STM-N subboard in different slot

NOTE: Above cases combination use in one C-Node has no limitation


Traffic Maintenance ⎯ Protection 7-12

7.3.2.2 Switching Criterion

For SNC/I Item Switching Requirement Note

AU-LOP SSF (Server Signal Fail) - HOP

AU-AIS SSF (Server Signal Fail) Include cause of AU-AIS ex LOS

TU-LOP SSF (Server Signal Fail) - LOP

TU-AIS SSF (Server Signal Fail) Include cause of TU-AIS ex LOS

For SNC/N Item Switching Requirement

AU-LOP SSF (Server Signal Fail)

AU-AIS SSF (Server Signal Fail)

HP-UNEQ TSF (Trail Signal Fail)

HP-TIM TSF (Trail Signal Fail)

HP-EXC TSF (Trail Signal Fail)

HOP

HP-DEG TSD (Trail Signal Degrade)

TU-LOP SSF (Server Signal Fail)

TU-AIS SSF (Server Signal Fail)

LP-UNEQ TSF (Trail Signal Fail)

LP-TIM TSF (Trail Signal Fail)

LP-EXC TSF (Trail Signal Fail)

LP-DEG TSD (Trail Signal Degrade)

LOP

LOM TSF (Trail Signal Fail)


Traffic Maintenance ⎯ Protection 7-13

E

7.3.2.3 External Commands

Command Term Content Revertive Non- revertive

Lockout of protection LKOP If the command is set, the protection channel

will be forbidden to use unconditionally. ○ ○

Forced switch FSP If the command is set, the traffic will be

switched to protection channel unconditionally. ○ ○

Manual switch MSP

If the command is set and protection channel is in normal status, the traffic will be switched to protection channel.

○ ○

7.3.2.4 Command Priority

LKOP> FSP> SF on Prot>SF on Work> SD on Prot> SD on Work> MSP> Wait-to-restore> No request

7.3.3 Timing Source Protection

7.3.3.1 Action Mode C-Node supports Timing source protection in action methods: Revertive.

7.3.3.2 Switching Criterion Lockout/FS/ SF/MS SF (STM-N): LOS, LOF, MS-AIS, and RS-TIM SF (2Mbps G.703.6) LOS, LOF, AIS SF (2MHz G703.10) LOS (Priority/ Quality/ SSM selectable)

7.3.3.3 Switch Time Switch time: 200msec (timing source selected time)+300msec(timing source switch time)

This page is intentionally left blank


Firmware Maintenance 8-1

8. FIRMWARE MAINTENANCE

Firmware is the semi-permanent set of operating instructions (software). The version of the firmware can be retrieved/switched/upgraded via the Upgrade F/W and FPGA dialog box.

NOTE: For retrieving the firmware version, refer to 3.6.1 Procedure: Retrieve Installed Firmware Version in this manual.


Firmware Maintenance ⎯ Switch Firmware Version 8-2

8.1 Switch Firmware Version

Sometimes it is necessary to switch the firmware version for maintenance.

The firmware version switch is available for the software port only. For other ports (FPGA hardware ports) the firmware version switch cannot be performed.

8.1.1 Procedure: Switch Firmware Version Perform the following procedure to switch the firmware version:






Firmware Maintenance ⎯ Switch Firmware Version 8-3

4. At the top of Upgrade F/W and FPGA dialog box, Select the target board from first drop-down list and select F/W from the second drop-down list.

5. Click Retrieve button to retrieve the current version information.

6. Click the check box from the Serial column to select the operation object.

7. Check the Switch radio button, and then click the Run button. The Process Result dialog box will be shown.

Figure 8-2. Process Result dialog box

This step is the end of procedure.


Firmware Maintenance ⎯Upgrade Firmware Version 8-4

8.2 Upgrade Firmware Version

The firmware can be upgraded to support new functions or revise bugs. Take Mainboard upgrading for example:

NOTE:

1) All the other applications must be quitted during performing the firmware version upgrading operation.

2) The FPGA of mainboard is not compatible before version 0.15 from R5.1b.

8.2.1 Procedure: Upgrade the Version of Mainboard

Upgrade Firmware Version

Perform the following procedure to upgrade the firmware version:

1. Close all the files and applications running in the system.







5. Select the Mainboard and the upgrade type F/W from the drop-down list on the top of the Upgrade F/W and FPGA dialog box

6. Check the Retrieve radio button and click the Run button to upload the release information.

7. Click the Upgrade radio button.

8. Click the Set Upgrade button. The Upgrade Setting dialog box is shown as Figure 8-4:



Figure 8-4. Upgrade Setting Dialog Box

9. Input the location of the upgrade file to the Upgrade File textbox, if you know where the upgrading file exists accurately, else you can select the upgrade file by click the Browse button. The Open window shown as bellow:

NOTE: If the Cancel button is clicked here instead of the Open button, browsing operation will be cancelled.



10. Select The settings are fit for all objects which have the same attributes check box to enable this function, otherwise the settings are only applied for the selected objects.

11. Confirm the setting you have just done correct, and then click the Ok button to over you setting procedure.

12. Then click the Run button to execute firmware upgrading.

NOTE: If the Close button is clicked here instead of the Run button, the firmware upgrading is cancelled.

13. During the upgrading operation, the window is shown as Figure 8-5 .

Figure 8-5. Upgrade F/W and FPGA Dialog Box during Upgrading

14. If the Stop Current Object button in the Process Result dialog box is clicked during the firmware version upgrading operation, it only stop upgrading the current object; if the Stop All Object button is clicked, all object upgrading operation will be interrupted

To quit the firmware version upgrading operation, click the Close button.


NOTE: When finish upgrade Mainboard, there is a trial run status, during which it is forbidden to power down or reset until 6 minutes late.



Upgrade FPGA Version

Perform the following procedure to upgrade the firmware version:




3. Select the Mainboard and the upgrade type FPGA from the drop-down list on the top of the Upgrade F/W and FPGA dialog box

4. Check the Retrieve radio button and click the Run button to upload the release information.

5. Click the Upgrade radio button.

6. Click the Set Upgrade button. The Upgrade Setting dialog box is shown as Figure 8-7:



Figure 8-7. Upgrade Setting Dialog Box

7. Input the location of the upgrade file to the Upgrade File textbox, if you know where the upgrading file exists accurately, else you can select the upgrade file by click the Browse button. The Open window shown as bellow:

NOTE: If the Cancel button is clicked here instead of the Open button, browsing operation will be cancelled.



E

8. Select The settings are fit for all objects which have the same attributes check box to enable this function, otherwise the settings are only applied for the selected objects.

9. Confirm the setting you have just done correct, and then click the Ok button to over you setting procedure.

10. Then click the Run button to execute firmware upgrading.

NOTE: If the Close button is clicked here instead of the Run button, the firmware upgrading is cancelled.

11. During the upgrading operation, the window is shown as Figure 8-8 .

Figure 8-8. Upgrade F/W and FPGA Dialog Box during Upgrading

12. If the Stop Current Object button in the Process Result dialog box is clicked during the firmware version upgrading operation, it only stop upgrading the current object; if the Stop All Object button is clicked, all object upgrading operation will be interrupted

To quit the FPGA version upgrading operation, click the Close button.



Configuration Changes 9-1

9. CONFIGURATION CHANGES

This section provides descriptions and procedures for changing C-Node setups while in service by CID operations. Because only ring network is supported by our products, this section provides descriptions and procedures of adding NE into ring and removing NE from ring network.

The following configuration changes are provided:

Adding nodes

Removing nodes


Configuration Changes ⎯ Adding Nodes 9-2

9.1 Adding Nodes

In this section, an example will be given to illustrate how to add a node in a ring network. In the course of adding a node in a ring network IP address for F and DCC interfaces and traffic linkage must be modified. In order to achieve adding a node in service the ring network must be configured with protection mode.

9.1.1 Example Description(Before Change)

Figure 9-1 is a STM ring network. The ring includes three NEs.

Figure 9-1. SDH ring network

Table 9-1 shows the traffic configuration relationship of three NEs (for example).

Table 9-1. Crossconnect Configuration of Three NEs (for example)

NE NO. TS NO.

ADD/DROP PASS THROUGH

NE1 1#VC4 1#TUG3 1# TU12

1#VC4 1#TUG3 2# TU12

NE2 1#VC4 1#TUG3 1# TU12 1#VC4 1#TUG3 2# TU12


Figure 9-2, Figure 9-3 and Figure 9-4 shows the crossconnect configuration of three NEs in CID.


Configuration Changes ⎯Adding Nodes 9-3

Figure 9-2. NE1 Crossconnect Configuration





Figure 9-5 shows IP address of NE and CID. It is just an example. Many other settings are also usable. Table 9-2 gives the corresponding IP parameter setting.

192.254.1.2

192.254.1.1

192.1.1.1

192.1.2..1 192.1.1..2192.1.2.2

192.1.3.1192.1.3.2 192.254.2.1

192.254.2.2

NE1 NE2 NE3

CID1 CID2

Figure 9-5. IP Setting of DCC Port (for example )



Table 9-2. IP Parameter Setting(for example )

OBJECT DCC PORT IP PARAMETERS

PORT PORT

POSITION PORT

ALLOCATIONIP

ADDRESSSUBNET

MASK BROADCAST

ADDRESS

Port 1 STM-1-W Network 192.1.1.1 255.255.255.0 192.1.1.255 Port 2 STM-1-E User 192.1.3.2 255.255.255.0 192.1.3.255 NE1

F LAN - 192.254.1.1 255.255.255.0 192.254.1.255 Port 1 STM-1-W Network 192.1.2.1 255.255.255.0 192.1.2.255

NE2 Port 2 STM-1-E User 192.1.1.2 255.255.255.0 192.1.1.255 Port 1 STM-1-W Network 192.1.3.1 255.255.255.0 192.1.3.255 Port 2 STM-1-E User 192.1.2.2 255.255.255.0 192.1.2.255 NE3

F LAN - 192.254.2.1 255.255.255.0 192.254.2.255 CID1 - - - 192.254.1.2 255.255.255.0 192.254.1.255 CID2 - - - 192.254.2.2 255.255.255.0 192.254.2.255

Then we will add a node of NE4 into the above ring network. Figure 9-6 shows a new STM-ring network after adding a new node of NE4 between NE2 and NE3. Below description provides how to operate in CID for adding NE4.

Figure 9-6. New SDH ring Network after Adding NE4


Configuration Changes⎯ Adding Nodes 9-6

9.1.2 IP Address Configuration

9.1.2.1 New IP Configuration

Figure 9-7 shows IP setting of NE and CID of new network. It is also an example. Table 9-3 provides the corresponding new IP parameter setting.

Figure 9-7. IP Setting of DCC Port (for example )



Table 9-3. IP Parameter Setting (for example )

OBJECT DCC PORT IP PARAMETERS

PORT PORT

POSITION PORT

ALLOCATIONIP

ADDRESSSUBNET

MASK BROADCAST

ADDRESS

Port 1 STM-1-W Network 192.1.1.1 255.255.255.0 192.1.1.255 Port 2 STM-1-E User 192.1.3.2 255.255.255.0 192.1.3.255 NE1

F LAN - 192.254.1.1 255.255.255.0 192.254.1.255 Port 1 STM-1-W Network 192.1.2.1 255.255.255.0 192.1.2.255

NE2 Port 2 STM-1-E User 192.1.1.2 255.255.255.0 192.1.1.255 Port 1 STM-1-W Network 192.1.4.1 255.255.255.0 192.1.4.255 Port 2 STM-1-E User 192.1.2.2 255.255.255.0 192.1.2.255 NE4

F LAN 192.254.3.1 255.255.255.0 192.254.3.255 Port 1 STM-1-W Network 192.1.3.1 255.255.255.0 192.1.3.255 Port 2 STM-1-E User 192.1.4.2 255.255.255.0 192.1.4.255 NE3

F LAN - 192.254.2.1 255.255.255.0 192.254.2.255 CID1 - - - 192.254.1.2 255.255.255.0 192.254.1.255 CID2 - - - 192.254.2.2 255.255.255.0 192.254.2.255 CID3 192.254.3.2 255.255.255.0 192.254.3.255

Comparing Table 9-2 and Table 9-3, we will find that only NE3’s IP address should be modified in original network and the new adding NE4 should be totally initialed. Below description provides the IP setting procedure of F interface and DCC interface of NE3 and NE4 with CID.

9.1.2.2 NE3 IP Modification Procedure

Procedure

1. Start up the CID, and log in to the target NE3.


3. Select IP Parameter Setup from the Communication menu. The IP parameters Setup dialog box shown in Figure 9-8 appear:



Figure 9-8. IP Parameters Setup Dialog Box of NE3

4. Click the Retrieve button to report the IP parameters of the C-Node NE to the CID.

5. Enter the IP address (192.254.2.1) into the IP Address field and enter the subnet mask (255.255.255.0) into the Net Mask field in F Interface (A,B,C,D)

6. Select DCC1 channel in the tree structure, enter IP address (192.1.3.1) and subnet mask (255.255.255.0) into the IP Address and the Net Mask fields respectively and click the Modify button.

7. Select DCC2 channel in the tree structure, enter IP address (192.1.2.2) and subnet mask (255.255.255.0) into the IP Address and the Net Mask fields respectively and click the Modify button.

8. Click the Set button to send above modification down to NE.



9.1.2.3 NE4 IP Setup Procedure

Procedure



3. Select IP Parameter Setup from the Communication menu. The IP parameters Setup dialog box shown in Figure 9-9 appear:

Figure 9-9. IP Parameter Setup Dialog Box NE4


5. Enter the IP address (192.254.3.1) into the IP Address field and enter the subnet mask (255.255.255.0) into the Net Mask field in F Interface (A,B,C,D)

6. Select DCC1 channel in the tree structures, enter IP address (192.1.4.1) and subnet mask (255.255.255.0) into the IP Address and the Net Mask fields respectively and click the Add button.



7. Select DCC2 channel in the tree structures, enter IP address (192.1.2.2) and subnet mask (255.255.255.0) into the IP Address and the Net Mask fields respectively and click the Add button.




9.1.3 NSAP Change

9.1.3.1 New NSAP Configuration

Figure 9-10 shows NSAP setting of NE in the new network. It is also an example.

Table 9-4 provides the corresponding new NSAP parameter setting.

Figure 9-10. NSAP Setting (4 NE Ring for example)



Table 9-4. IP Parameter Setting (4 NE Ring for example)

C-Node 1 C-Node 2 C-Node 3 C-Node 4

Manual Area Address 49000000000000000000000000

49000000000000000000000000

49000000000000000000000000

49000000000000000000000000

Local System ID 0007300d0123 0007300d0120 0007300d0117 0007300d01fe

Transport N-selector 0x01 0x01 0x01 0x01

Comparing Table 9-2 and Table 9-4, we will find that all the original NEs and CID needn’t be modified; only the new adding NE4 should be totally initialed. Below description provides the NSAP setting procedure NE4 with CID.

9.1.3.2 NE4 NSAP Setup Procedure

Procedure



11. Select OSI Protocol Configuration from the Communication menu. Then click the CLNP Tab, the CLNP parameters Setup dialog box shown in Figure 9-11appear: You can change the NSAP in this tab through change the Manual Area address and Local System ID (Set).


13. Enter the Area address (49000000000000000000000000) into the Manual Area Address field, enter the System ID (0007300d01fe) into the Local System ID (Set) field and NSEL (01) into the Transport N-Selector Value field.


NOTE: When OSI Parameters are changed, we need to reset the MainBoard.

NE PARAMETER



Figure 9-11. NSAP Parameter Setup Dialog Box (NE4)



9.1.4 Crossconnect Configuration

9.1.4.1 New Crossconnect Configuration New crossnnect configuration should not change the traffic linkage between original three nodes. At the same time original NEs must transmit new node’s traffic. Table 9-5 shows an example of the traffic configuration relationship for four NEs.

Table 9-5. Crossconnect Configuration of Four NEs (for example)

NE NO. TS NO.

ADD/DROP PASS THROUGH

NE1 1#VC4 1#TUG3 1# TU12

1#VC4 1#TUG3 2# TU12

1#VC4 1#TUG3 3# TU12


1#VC4 1#TUG3 3# TU12


1#VC4 1#TUG3 3# TU12


1#VC4 1#TUG3 2# TU12

Figure 9-12, Figure 9-13, Figure 9-14 and Figure 9-15 show the crossconnect configuration of four NEs in CID.



Figure 9-12. NE1 Cossconnect Configuration




9.1.4.2 NE1 Crossconnect Setting Procedure

Procedure



3. Select Cross Connect Configuration from the Communication menu. The Cross Connect Configuration dialog box appears.

4. Click 1+1 Primary, connect 1#VC4 1#TUG3 1#TU12 of 01 optic port to 1#TU12 of E1 port.

5. Click 1+1 Backup, connect 1#VC4 1#TUG3 1#TU12 of 02 optic port to 1#TU12 of E1 port.

6. Click Broadcast, connect 1#TU12 of E1 port. to 1#VC4 1#TUG3 1#TU12 of 01 optic port and 1#VC4 1#TUG3 1#TU12 of 02 optic port.

7. Repeat steps 4,5 and 6 for 1#VC4 1#TUG3 2#, 3# TU12 of 01 and 02 optic port individually to 2#, 3# TU12 of E1 port.

8. Click the Set button.




Procedure



3. Select Cross Connect Configuration from the Configuration menu. The Cross Connect Configuration dialog box appears.




7. Click Broadcast, connect 1#VC4 1#TUG3 2#TU12 of 01 optic port from/to 1#VC4 1#TUG3 2#TU12 of 02 optic port, 1#VC4 1#TUG3 3#TU12 of 01 optic port from/to 1#VC4 1#TUG3 3#TU12 of 02 optic port respectively.





Procedure










Configuration Changes ⎯Removing Nodes 9-21

E

9.2 Removing Nodes

Removing a node is just reverse to adding a node. Detail process refers to above adding process.


Trouble Clearing ⎯ Making Contact with NEC 10-1

10. TROUBLE CLEARING

This section provides the information on the required actions against the alarm conditions indicated by alarm messages.

10.1 Making Contact with NEC

For technical assistance or information, please contact your project contractor, or an NEC supporting office:


Trouble Clearing ⎯ Categories of Condition Types 10-2

10.2 Categories of Condition Types

Descriptions and procedures in this section are organized in the alphabetic order of indication messages. Alarm indication messages and procedures to clear the conditions are provided in the following subsection:

10.2.1 List of Indication Messages SDH Alarm

(1 of 4)

INDICATION CATEGORY DESCRIPTION FAULT LOCATION DEFAULT CLASS

AIS (only 2Mbps)

Facility Alarm indication signal

EXT CLK IN External timing source

MN

AU-AIS Facility Alarm indication signal

MSA MSA function in upstream equipment

MJ

AU-LOP Facility Loss of pointer MSA MSA function in upstream equipment

MJ

BUS_ERROR Equipment BUS defect BUS BUS_ERROR

MN

CLKFAIL Facility Clock fail SETS Clock module

MN

CLKDRIFT Facility Frequency drift SETS Clock sending function in upstream equipment

MN

HKAn (n = 1 thru 8)

Environment

House keeping alarms

Environment Environment device

MN

HP-DEG Facility Degrade HPT HPT in upstream equipment or optical fiber and connector

MN

HP-EXC Facility B3 byte error HPT HPT in upstream equipment or optical fiber and connector

MJ

HP-PLMF Facility Payload mismatch

HPA Configuration in upstream equipment

MJ



(2 of 4)


HP-RDI Facility Remote defect indicate

HPT Upstream equipment detecting HP alarm

MJ

HP-TIM Facility Trace mismatch HPT J1 setting or upstream equipment setting

MJ

HP-UNEQ Facility Unequipment HPT No crossconnect setting in upstream equipment

MJ

LINK-FAIL Network LAPD communication fail

DCC Upstream equipment DCC failure

MN

LOF Facility Loss of frame RST Upstream equipment

CR

LOF (only 2Mbps)

Facility Loss of frame EXT CLK IN External timing source

MN

LOM Facility Los of multi-frame

HPA HPA function in upstream equipment

MJ

SPI Optical fiber or upstream equipment

CR

45M 45M input cable or upstream equipment

CR


CR


CR

LOS Facility No signal input

EXT CLK IN (2Mbps) Input cable or external timing source

MN



(3 of 4)


LOS (2MHz)

Facility No signal input EXT CLK IN Input cable or external timing source

MN

LOS (electrical INTF)

Facility No signal input SPI Cable or upstream equipment

CR

LP-DEG Facility Degrade LPT LPT in upstream equipment or optical fiber and connector

MN

LP-EXC Facility B3 byte error LPT LPT in upstream equipment or optical fiber and connector

MJ

LP-PLMF Facility Payload mismatch

LPA Configuration in upstream equipment

MJ

LP-RDI Facility Remote defect indicate

LPT Upstream equipment detecting LP alarm

MJ

LP-TIM Facility Trace mismatch LPT J2 setting or upstream equipment setting

MJ

LP-UNEQ Facility Unequipped LPT No crossconnect setting in upstream equipment

MJ

LTI Facility Los of External timing source

SETS All the timing source

MJ

MEM_FAIL Equipment Memory defect MEM Memory fail

MN

MS-AIS Facility Alarm indication signal

MST Upstream equipment

CR

MS-DEG Facility Degrade MST Optical fiber or connector

MN

MS-EXC Facility MS B2 byte error

MST Optical fiber or connector

MJ



(4 of 4)


MS-RDI Facility Remote defect indicate

MST Upstream equipment detecting alarm

MJ

PKG_FAIL Equipment Package defect PKG (see NOTE) breakdown

CR

PKG_REMOVED

Equipment Remove board PKG (see NOTE) Not install board

CR

PKG_TYPE

Equipment Wrong PKG install

PKG (see NOTE) Wrong configuration

CR

PPI_AIS Facility Alarm indication signal

PPI Frame all "1"

MN

PPI_EXC Facility PDH code error PPI PDH Bit Error>=10e-3

MJ

PPI_DEG Facility PDH Degrade PPI PDH Bit Error>=10e-5

MN

PPS-FAIL Facility PPS failed HPC, LPC Both not receiving signals

CR

REF_FAIL Facility SSM failure SETS Upstream equipment

MN

RS-TIM Facility Trace mismatch RST J0 setting or upstream equipment setting

CR

TU-AIS Facility Alarm indication signal

HPA, LPA HPA function in upstream equipment

MJ

TU-LOP Facility Loss of pointer HPA HPA function in upstream equipment

MJ

NOTE: “PKG (Package)” indicates Mainboard and Subboards.



Ethernet Alarm

(1 of 2)

INDICATION CATEGORY DESCRIPTION FAULT LOCATION

DEFAULT CLASS

CSF_LCS Facility Loss of Client Signal Ethernet

(WAN) MJ

CSF_LCSync Facility

Loss of Client Character Synchronization

Ethernet (WAN)

MJ

CSF_R_LCS Facility Remote end Loss of Client Signal

Ethernet (WAN)

MN

CSF_R_LCSync Facility

Remote end Loss of Client Character Synchronization

Ethernet (WAN)

MN

DropPkt_EXC

Facility A count of drop packets. Ethernet (LAN&WAN)

MJ

LINK_DOWN Facility Alarm for the link status. Ethernet (LAN&WAN)

CR

RxAlignmentErrorFrame_EXC

Facility A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check

Ethernet (LAN&WAN)

MJ

RxFCSErrorFrame_EXC

Facility A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check.

Ethernet (LAN&WAN)

MJ

TxCollisionFrame_EXC

Facility Number of collisions on this Ethernet segment

Ethernet (LAN)

MJ

TxDelayTransmission_EXC

Facility A count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy

Ethernet (LAN)

MJ

TxExtCollisionFrame_EXC

Facility A count of frames for which transmission on a particular interface fails due to excessive collisions.

Ethernet (LAN)

MJ

TxLateCollisionFrame_EXC

Facility The number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet

Ethernet (LAN)

MJ



(2 of 2)


DEFAULT CLASS

WAN_PORT_SD

Facility WAN port DEG Ethernet (WAN)

MN

WAN_PORT_SF

Facility WAN port fail Ethernet (WAN)

MJ

NOTE: There are some EXC alarms in above Ethernet Alarm table. They are converted from corresponding performances once the performances exceed the thresholds which are shown in below.

Performance EXC Alarm

ALARM PERFORMANCE DEFAULT THRESHOLD

THRESHOLD SETTING RANGE

DropPkt_EXC ETH-DropPkt 4294967294 0~4294967294

RxAlignmentErrorFrame_EXC

ETH-RxAlignmen tErrorFrame

4294967294 0~4294967294

RxFCSErrorFrame_EXC

ETH-RxFCSErrorFrame

4294967294 0~4294967294

TxCollisionFrame_EXC ETH- TxCollisionFrame

4294967294 0~4294967294

TxDelayTransmission_EXC

ETH- TxDelayTransmission

4294967294 0~4294967294

TxExtCollisionFrame_EXC

ETH-TxExtCollisionFrame

4294967294 0~4294967294

TxLateCollisionFrame_EXC

ETH- TxLateCollisionFrame

4294967294 0~4294967294

Encapsulation Alarm


DEFAULT CLASS

SSF_LGS Facility Loss of GFP frame Synchronization

WAN MJ

LAPS_FAIL Facility LAPS Layer Fail WAN MJ



Virtual Concatenation Alarm


DEFAULT CLASS

LP-Xv-LOA Facility Loss of Alignment VC12/VC3 MJ

LP-Xv-LOM Facility Loss of Multi-frame defect VC12/VC3 MJ

LP-Xv-PLM Facility Extended signal label mismatch

VC12 MJ

LP-Xv-SQM Facility Loss of Sequence defect VC12/VC3 MJ


Trouble Clearing ⎯ Retrieve Alarm Information 10-9

10.3 Retrieve Alarm Information

Use the following procedures to verify the condition. These steps are required by some trouble clearing procedures.

10.3.1 Procedure: Display Current Alarm



3. Perform one of the following procedures to open the Alarm Monitor dialog box shown in Figure 10-1:

Select Current Alarm from the Alarm menu.

Click the board of the equipment in the NE management dialog box.


Figure 10-1. Alarm Monitor Dialog Box


Trouble Clearing ⎯ Retrieve Alarm Information 10-10

In this dialog box:

To view the current alarms using display options, click the All check box to unselect it and specify display options. Then click the Retrieve button to update the current alarm list according to the selection. For detailed information, refer to the section 3. Retrieve Information; 3.1.3.1 Using Display Options in this manual.

To enable the auto refresh function, click the Auto Report Screen check box to select it and click the Retrieve button. For detailed information, refer to the section 3. Retrieve Information; 3.1.3.2 Auto Refresh Function in this manual.

To print out the current alarm list, click the Print button.

4. After viewing, click the Close button.



Trouble Clearing ⎯ Equipment 10-11

10.4 Equipment

This subsection provides the descriptions and clearing methods (procedure) for alarmed conditions related to the equipment.

10.4.1 BUS_ERROR

10.4.1.1 Description

This message indicates there are some errors in package bus.

10.4.1.2 Apparatus

A package for the replacement


10.4.1.3 Clear BUS_ERROR Condition

1. Replace the package.

2. Retrieve the current alarms, and check if the BUS_ERROR alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.4.2 MEM_FAIL


This message indicates there are some read/write errors of FLASH ROM.

10.4.2.2 Apparatus

A FLASH ROM for the replacement


10.4.2.3 Clear MEM_FAIL Condition

1. Replace the package.

2. Retrieve the current alarms, and check if the MEM_FAIL alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.4.3 PKG_FAIL


This message indicates that a failure has been detected in the installed package(s). The possible cause is that package type can not be identified because of package failure.

10.4.3.2 Apparatus

A board for the replacement


10.4.3.3 Clear PKG_FAIL Condition

1. Replace the FLASH ROM.

2. Retrieve the current alarms, and check if the PKG_FAIL alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.4.4 PKG_REMOVED


This message indicates that a failure has been detected in the registered board. The possible cause is removed of board.

10.4.4.2 Apparatus



10.4.4.3 Clear PKG_REMOVED Condition

1. Confirm that the board is located in the registered slot.

2. Pull out the board, and reinsert it into the slot. If there is not board in the registered slot, delete the register of it.

3. Retrieve the current alarms, and check if the PKG_REMOVED alarm is cleared.

4. If the alarm is not cleared, replace the board.

5. Retrieve the current alarms, and check if the PKG_REMOVED alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.4.5 PKG_TYPE


This message indicates that a failure has been detected in the registered board. The possible causes are board register error or the port connector type error or the port configures error in the CID.

10.4.5.2 Apparatus


10.4.5.3 Clear PKG_TYPE Condition

1. Confirm whether the registered board is correct.

2. If the configuration is incorrect, modify it.

3. Retrieve the current alarms, and check if the PKG_TYPE alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.



Trouble Clearing ⎯ Facility 10-16

10.5 Facility

Alarms related to the facility category may be caused by an improper cable connection, and/or by degraded optical connectors. If any alarm described in this subsection occurs, these physical problems should be verified first.



10.5.1 AIS


This message indicates that a failure of the AIS (alarm indication signal) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the indicated line in the far-end NE.

10.5.1.2 Clear AIS Condition

1. Check if an alarm occurs to a facility or path in the far-end NE that is associated with the indicated facility, and clear it to normal state.

2. Retrieve the current alarms, and check if the AIS alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.2 AU-AIS


This message indicates that a failure of the AU-AIS (alarm indication signal) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the MSA function in the far-end NE.

10.5.2.2 Clear AU-AIS Condition

1. Check if an alarm occurs to a facility or path in the far-end NE that is associated with the indicated facility.

2. Clear condition that cause the alarm for the far-end NE.

3. Retrieve the current alarms, and check if the AU-AIS alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.3 AU-LOP


This message indicates that a failure of the AU-LOP (loss of pointer) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the MSA function in the far-end NE.

10.5.3.2 Clear AU-LOP Condition


2. Clear condition that cause the alarm for the far-end NE.

3. Retrieve the current alarms, and check if the AU-LOP alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.4 CLKFAIL


This message indicates that a failure of the CLKFAIL (clock fail) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the clock module.

10.5.4.2 Apparatus

A clock module for replacement


10.5.4.3 Clear CLKFAIL Condition

1. Check if the timing reference failed between the internal modules.

2. Clear the condition that cause the alarm.

3. Retrieve the current alarms, and check if the CLKFAIL alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.5 CLKDRIFT


This message indicates that a failure of the CLKDRIFT (frequency drift) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the clock sending function in the far-end NE.

10.5.5.2 Clear CLKDRIFT Condition

1. Check if timing source reference drift occur.


3. Retrieve the current alarms, and check if the CLKDRIFT alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.6 HP-DEG


This message indicates that a failure of the HP-DEG (degrade) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the optical fiber and connector or on HPT in the far-end NE.

10.5.6.2 Clear HP-DEG Condition

1. Check the optical fiber and connector of upstream equipment.


3. Retrieve the current alarms, and check if the HP-DEG alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.7 HP-EXC


This message indicates that a failure of the HP-EXC (B3 byte error) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the optical fiber and connector or on HPT in the far-end NE.

10.5.7.2 Clear HP-EXC Condition



3. Retrieve the current alarms, and check if the HP-EXC alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.8 HP-PLMF


This message indicates that a failure of the HP-PLMF (payload mismatch) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the configuration in the far-end NE.

10.5.8.2 Clear HP-PLMF Condition


2. Clear condition that cause the alarm at the far-end NE.

3. Retrieve the current alarms, and check if the HP-PLMF alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.9 HP-RDI


This message indicates that a failure of the HP-RDI (remote defect indicate) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is a HP alarm is detected in the far-end NE.

10.5.9.2 Clear HP-RDI Condition


2. Clear condition that cause the alarm at the far-end NE

3. Retrieve the current alarms, and check if the HP-RDI alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.10 HP-TIM


This message indicates that a failure of the HP-TIM (trace mismatch) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the J1 setting or on the far-end NE setting.

10.5.10.2 Clear HP-TIM Condition

1. Check if the receive byte same to expect.

2. Clear the condition if the receive byte not same to expect.

3. Retrieve the current alarms, and check if the HP-TIM alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.11 HP-UNEQ


This message indicates that a failure of the HP-UNEQ (un equipment) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the crossconnect setting in the far-end NE.

10.5.11.2 Clear HP-UNEQ Condition


2. Clear condition that cause the alarm at the far-end NE

3. Retrieve the current alarms, and check if the HP-UNEQ alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.12 LOF


This message indicates that a failure of the LOF (loss of frame) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the cable or on the far-end NE.

10.5.12.2 Clear LOF Condition


2. Clear the condition that causes the alarm.

3. Retrieve the current alarms, and check if the LOF alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.13 LOF ⎯ 2Mbps


This message indicates that a failure of the LOF (2 Mbps) (loss of frame) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the external timing source.

10.5.13.2 Clear LOF (2 Mbps) Condition

1. Check if an alarm occurs or wrong setting exists in the equipment at another side.


3. Retrieve the current alarms, and check if the LOF (2 Mbps) alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.14 LOM


This message indicates that a failure of the LOM (loss of multi-frame) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the HPA function in the far-end NE.

10.5.14.2 Clear LOM Condition



3. Retrieve the current alarms, and check if the LOM alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.15 LOS


This message indicates that a failure of the LOS (loss of signal) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the optical fiber or on the far-end NE.

10.5.15.2 Clear LOS Condition

1. Check if there is any problem in cable connection or in the equipment at another side.


3. Retrieve the current alarms, and check if the LOS alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.16 LOS ⎯ 2 MHz


This message indicates that a failure of the LOS (2 MHz) (loss of signal) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the input cable or on the external timing source.

10.5.16.2 Clear LOS (2 MHz) Condition



3. Retrieve the current alarms, and check if the LOS (2 MHz) alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.17 LOS ⎯ Electrical INTF


This message indicates that a failure of the LOS (electrical INTF) (loss of signal) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the fiber or at the far-end NE.

10.5.17.2 Clear LOS (Electrical INTF) Condition



3. Retrieve the current alarms, and check if the LOS (electrical INTF) alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.18 LP-DEG


This message indicates that a failure of the LP-DEG (degrade) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the optical fiber and connector or on LP at the far-end NE.

10.5.18.2 Clear LP-DEG Condition



3. Retrieve the current alarms, and check if the LP-DEG alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.19 LP-EXC


This message indicates that a failure of the LP-EXC (B3 byte or V5 BIP2 error ) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the optical fiber and connector or on LP at the far-end NE.

10.5.19.2 Clear LP-EXC Condition



3. Retrieve the current alarms, and check if the LP-EXC alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.20 LP-PLMF


This message indicates that a failure of the LP-PLMF (payload mismatch) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the configuration at the far-end NE.

10.5.20.2 Clear LP-PLMF Condition



3. Retrieve the current alarms, and check if the LP-PLMF alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.21 LP-RDI


This message indicates that a failure of the LP-RDI (remote defect indicate) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is a LP alarm is detected at the far-end NE.

10.5.21.2 Clear LP-RDI Condition



3. Retrieve the current alarms, and check if the LP-RDI alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.22 LP-TIM


This message indicates that a failure of the LP-TIM (trace mismatch) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the J2 setting or at the far-end NE setting.

10.5.22.2 Clear LP-TIM Condition

1. Check if the receive byte same to expect.

2. Clear the condition if the receive byte not same to expect.

3. Retrieve the current alarms, and check if the LP-TIM alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.23 LP-UNEQ


This message indicates that a failure of the LP-UNEQ (un equipment) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the crossconnect setting at the far-end NE.

10.5.23.2 Clear LP-UNEQ Condition



3. Retrieve the current alarms, and check if the LP-UNEQ alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.24 LTI


This message indicates that a failure of the LTI (loss of all incoming timing source) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on all the timing source.

10.5.24.2 Clear LTI Condition

1. Check if all incoming timing references are invalid.


3. Retrieve the current alarms, and check if the LTI alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.25 MS-AIS


This message indicates that a failure of the MS-AIS (alarm indication signal) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is at the far-end NE.

10.5.25.2 Clear MS-AIS Condition



3. Retrieve the current alarms, and check if the MS-AIS alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.26 MS-DEG


This message indicates that a failure of the MS-DEG (degrade) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the optical fiber or connector.

10.5.26.2 Clear MS-DEG Condition



3. Retrieve the current alarms, and check if the MS-DEG alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.27 MS-EXC


This message indicates that a failure of the MS-EXC (MS B2 byte error) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the optical fiber or connector.

10.5.27.2 Clear MS-EXC Condition



3. Retrieve the current alarms, and check if the MS-EXC alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.28 MS-RDI


This message indicates that a failure of the MS-RDI (remote defect indicate) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is an alarm is detected at the far-end NE.

10.5.28.2 Clear MS-RDI Condition



3. Retrieve the current alarms, and check if the MS-RDI alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.29 PPI_AIS


This message indicates that a failure of the PPI_AIS (alarm indication signal) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on both receiving signals.

10.5.29.2 Clear PPI_AIS Condition



3. Retrieve the current alarms, and check if the PPI_AIS alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.30 PPI_EXC


This message indicates that a failure of the PPI_EXC (PDH code error) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the cable or connector.

10.5.30.2 Clear PPI_EXC Condition

1. Check the cable and connector of downstream equipment.


3. Retrieve the current alarms, and check if the PPI_EXC alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.31 PPI_DEG This message indicates that a failure of the PPI_DEG (degrade) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the cable or connector.

10.5.31.1 Clear PPI_DEG Condition

1. Check the cable and connector of downstream equipment.


3. Retrieve the current alarms, and check if the PPI_DEG alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.32 PPS-FAIL


This message indicates that a failure of the PPS-FAIL (PPS failed) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on both receiving signals.

10.5.32.2 Clear PPS-FAIL Condition

1. Check if the secondary path is available and the crossconnect configuration is valid.


3. Retrieve the current alarms, and check if the PPS-FAIL alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.33 REF_FAIL


This message indicates that a failure of the REF_FAIL (SSM failure) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is at the far-end NE.

10.5.33.2 Clear REF_FAIL Condition



3. Retrieve the current alarms, and check if the REF_FAIL alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.34 RS-TIM


This message indicates that a failure of the RS-TIM (trace mismatch) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the J0 setting or at the far-end NE setting.

10.5.34.2 Clear RS-TIM Condition

1. Check if the receive byte same to expected.

2. Clear the condition if the receive byte is not same to expected.

3. Retrieve the current alarms, and check if the RS-TIM alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.35 TU-AIS


This message indicates that a failure of TU-AIS (alarm indication signal) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the LPA function in the far-end NE.

10.5.35.2 Clear TU-AIS Condition



3. Retrieve the current alarms, and check if the TU-AIS alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.5.36 TU-LOP


This message indicates that a failure of the TU_LOP (loss of pointer) is detected from the incoming signal on the indicated facility. If this condition occurs, the problem is on the HPA function at the far-end NE.

10.5.36.2 Clear TU-LOP Condition



3. Retrieve the current alarms, and check if the TU-LOP alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.



Trouble Clearing ⎯ Environment 10-53

10.6 Environment

In this subsection, provide the descriptions and clearing methods (procedure) for alarmed conditions related to the environment.

10.6.1 HKAn


This message indicates that a failure condition that is assigned to item number n (n = 1 thru 8) of the housekeeping alarm is detected.

NOTE: Only after having configured FAN_2 in Port Configuration window, the 5-8 port of the housekeeping alarm can be shown. The detailed configuration procedure refers to section 4.5 Setup Port Configuration of F4798_Q10 PROVISIONING manual

10.6.1.2 Clear HKAn Condition

1. Confirm which HKA is declared.


3. Retrieve the current alarms, and check if the HKA alarm is not cleared, contact NEC for the appropriate maintenance support.



Trouble Clearing ⎯ Network 10-54

10.7 Network

10.7.1 LINK-FAIL


This message indicates DCC communication down.

10.7.1.2 Clear LINK-FAIL Condition

1. Check if DCC Link Layer Setup between local end and far end is matching.

2. Check if Physical layer Setup of far end is activated and use same data paths: D1-D3.

3. Retrieve the current alarms, and check if the LINK-FAIL alarm is not cleared, contact NEC for the appropriate maintenance support.



Trouble Clearing ⎯ Ethernet Alarm 10-55

10.8 Ethernet Alarm

10.8.1 CSF_LCS


This message indicates loss of client signal. It is detected when SMII_SYNC and SMII_CLK is in the order, but SMII_RXDAT signal is lost.

10.8.1.2 Apparatus



10.8.1.3 Clear CSF_LCS Condition

1. Replace the board.

2. Retrieve the current alarms, and check if the CSF_LCS alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.2 CSF_LCSync


This message indicates loss of client character synchronization. It is detected when SMII_SYNC or SMII_CLK is lost

10.8.2.2 Apparatus



10.8.2.3 Clear CSF_LCSync Condition

1. Replace the board.

2. Retrieve the current alarms, and check if the CSF_LCSync alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.3 CSF_R_LCS


This message indicates remote end loss of client signal. It is detected when CSF_LCS alarm is reported in far end equipment.

10.8.3.2 Clear CSF_R_LCS Condition



3. Retrieve the current alarms, and check if the CSF_R_LCS alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.4 CSF_R_LCSync


This message indicates remote end loss of client character synchronization. It is detected when CSF-LCSync alarm is reported in far end equipment.

10.8.4.2 Clear CSF_R_LCSync Condition



3. Retrieve the current alarms, and check if the CSF_R_LCSync alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.5 DropPkt_EXC


This message indicates the rate of package dropped. It is detected when the rate of ETH-DropPkt exceeds Detect Threshold.

10.8.5.2 Clear DropPkt_EXC Condition

1. Check if Ethernet Port Configuration is valid.

2. Check if Layer 2 Configuration is valid.

3. Retrieve the current alarms, and check if the alarm DropPkt_EXC is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.6 LINK_DOWN


For LAN port: The alarm is reported when physical link failure is detected.

For WAN port: The alarm is reported when Ethernet bandwidth is not configured or WAN_PORT_SF alarm is detected.

But the alarm is not reported for the two kinds of ports when the port is shut off.

10.8.6.2 Clear LINK_DOWN Condition

1. For LAN port, Check if twisted-pair physical link is valid.

2. For WAN port, Check if Bandwidth Configuration is valid and confirm that there is no WAN_PORT_SF alarm.

3. Retrieve the current alarms, and check if the alarm LINK_DOWN is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.7 RxAlignmentErrorFrame_EXC


This message indicates the rate of received Frame with alignment error on a particular interface. It is detected when rate of ETH-RxAlignmentErrorFrame exceeds Detect Threshold.

10.8.7.2 Clear RxAlignmentErrorFrame_EXC Condition

1. For LAN, check if twisted-pair is CAT5 and RJ-45 connector is fastened.

2. For WAN, check if the performances of SDH transport layer and EOS encapsulation is normal. If not, make performances normal first.

3. Retrieve the current alarms, and check if RxAlignmentErrorFrame_EXC alarm is cleared. If the alarm is not cleared, replace the board.

4. Retrieve the current alarms, and check if RxAlignmentErrorFrame_EXC alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.8 RxFCSErrorFrame_EXC


This message indicates the rate of received Frame with FCS error on a particular interface. It is detected when rate of ETH-RxFCSErrorFrame exceeds Detect Threshold.

10.8.8.2 Clear RxFCSErrorFrame_EXC Condition

1. For LAN, check if twisted-pair is CAT5 and RJ-45 connector is fastened.

2. For WAN, check if the performances of SDH transport layer and EOS encapsulation is normal. If not, make performances normal first.

3. Retrieve the current alarms, and check if RxFCSErrorFrame_EXC alarm is cleared. If the alarm is not cleared, replace the board.

4. Retrieve the current alarms, and check if RxFCSErrorFrame_EXC alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.9 TxCollisionFrame_EXC


This message indicates the rate of Collision on Ethernet segment in which C-Node is located. It is detected when rate of ETH-TxCollisionFrame exceeds Detect Threshold. It is valid only on LAN.

10.8.9.2 Clear TxCollisionFrame_EXC Condition

1. Check if the port configurations between LAN port and the equipment attached to it is matching.

2. Retrieve the current alarms, and check if the alarm TxCollisionFrame_EXC is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.10 TxDelayTransmission_EXC


This message indicates the rate of Frame for which the first transmission attempt on a particular interface is delayed because the medium is busy. It is detected when rate of ETH-TxDelayTransmissions exceeds Detect Threshold. It is valid only on LAN.

10.8.10.2 Clear TxDelayTransmission_EXC Condition


2. Retrieve the current alarms, and check if TxDelayTransmission_EXC alarm is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.11 TxExtCollisionFrame_EXC


This message indicates the rate of Frame for which transmissions on a particular interface fail due to excessive collisions. It is detected when rate of ETH-TxExtCollisionFrame exceeds Detect Threshold. It is valid only on LAN.

10.8.11.2 Clear TxExtCollisionFrame_EXC Condition


2. Retrieve the current alarms, and check if the alarm TxExtCollisionFrame_EXC is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.12 TxLateCollisionFrames_EXC


This message indicates the rate of collisions that is detected in a time slot after transmission. It is detected when rate of ETH-TxLateCollisionFrame exceeds Detect Threshold.

10.8.12.2 Clear TxLateCollisionFrame_EXC Condition


2. Retrieve the current alarms, and check if the alarm TxLateCollisionFrame_EXC is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.13 WAN_PORT_SD


This message indicates the status of SDH transport path used by WAN port. It is detected when there is DEG alarm on SDH transport path used by WAN.

10.8.13.2 Clear WAN_PORT_SD Condition

1. Check if there is DEG alarm on SDH transport path used by WAN port. Clear it first.

2. Retrieve the current alarms, and check if the alarm WAN_PORT_SD is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.8.14 WAN_PORT_SF


It is detected when there exist alarms of UNEQ, TIM, RDI LOP and AIS on SDH transport path, or LP_Xv_SQM, LP_Xv_LOM and LP_Xv_LOA on Virtual Concatenation layer, or SSF_LGS LAPS_FAIL on Encapsulation layer.

10.8.14.2 Clear WAN_PORT_SF Condition

1. Check if there is Failure or DEG alarms on SDH transport path used by WAN port. Clear them.

2. Check if there is concatenation alarms on WAN port. Clear them.

3. Check if there is encapsulation alarms on WAN port. Clear them.

4. Retrieve the current alarms, and check if the alarm WAN_PORT_SF is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.



Trouble Clearing ⎯ Encapsulation Alarm 10-69

10.9 Encapsulation Alarm

10.9.1 SSF_LGS


This message indicates loss of GFP frame synchronization. It is detected when GFP synchronization signal is lost.

10.9.1.2 Clear SSF_LGS Condition

1. Check if cross connect configuration or bandwidth configuration of 100Base-T(2) is valid.

2. Check there is signal failure or degrade on SDH transport layer. Clear them.

3. Check if encapsulation is valid.

4. Retrieve the current alarms, and check if the alarm SSF_LGS is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.



Trouble Clearing ⎯ Encapsulation Alarm 10-70

10.9.2 LAPS_FAIL


This message indicates LAPS layer path alarm. It is detected when there is no idle byte(7EH) over 2048 octets.

10.9.2.2 Clear LAPS_FAIL Condition


2. Check is there signal failure or degrade on SDH transport layer. Clear them.

3. Check if encapsulation is valid.

4. Retrieve the current alarms, and check if the alarm LAPS_FAIL is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support



Trouble Clearing ⎯ Virtual Concatenation Alarm 10-71

10.10 Virtual Concatenation Alarm

10.10.1 LP-Xv-LOA


This message indicates loss of virtual concatenation multi-frame alignment. It is detected when not finding multi-frame alignment.

10.10.1.2 Clear LP-Xv-LOA Condition



3. Check is there too large time delay on virtual encapsulation transport trail.

4. Retrieve the current alarms, and check if the alarm LP-Xv-LOA is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support




10.10.2 LP-Xv-LOM


This message indicates loss of virtual concatenation multi-frame. It is detected when multi-frame counter's value is errorous for three times continuously.

10.10.2.2 Clear LP-Xv-LOM Condition



3. Retrieve the current alarms, and check if the alarm LP-Xv-LOM is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.




10.10.3 LP-Xv-PLM


This message indicates extended signal label mismatch. It is detected when extended signal label is different from the expectation value for three K4 multi-frame continuously.

10.10.3.2 Clear LP-Xv-SQM Condition

1. Check if there is signal failure or degrade on SDH transport layer. Clear them.

2. Check if encapsulation protocol configuration is right.

3. Retrieve the current alarms, and check if the alarm LP-Xv- PLM is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support




10.10.4 LP-Xv-SQM


This message indicates loss of virtual concatenation multi-frame sequence. It is detected when sequence number of virtual concatenation multi-frame is not stable for three times continuously.

10.10.4.2 Clear LP-Xv-SQM Condition

1. Check if cross connect configuration is valid.


3. Retrieve the current alarms, and check if the alarm LP-Xv- SQM is cleared. If the alarm is not cleared, contact NEC for the appropriate maintenance support.



Trouble Clearing ⎯ Office Alarms 10-75

10.11 Office Alarms

C-Node has four types of office alarms output: Alarm output for Bell (AB), Alarm Lamp (AL), Prompt Maintenance (PM), Differed Maintenance (DM). It can connect to Top of RACK, and show alarm status of C-Node.

Following table lists the relationship of alarm class and office alarm.

RANK OF ALARM REPORT TO OS PM DM AB AL LED

CR (Critical) V V - V V V

MJ (Major) V V - V V V

MN (Minor) V - V V V V

WN (Warning) V - - - - -

ACO function - - - V - -

NOTE: “V” denotes corresponding office alarm in the column will report when corresponding class alarm in the row occurs.

If you execute ACO (Alarm Cut Off) during alarm occurrence (AB/AL output), the audible alarm (AB) is silenced; however, AB will be output if another alarm occurs later.


Trouble Clearing ⎯ Alarm Action Table 10-76

E

10.12 Alarm Action Table physicalsection

RegeneratorSection PPT

SPI RST (note1)MST MSA HPOM HUG HPC HPT HPA LPOM LUG LPC LPT LPA PPTLOS

LOF <1>RS-TIM *1

REGENERATED SIGNALPASSED THROUGH

MS-AISMS-EXC *1MS-DEG AU-AISMS-BIP ERRORMS-REI

MS-RDIUNUSED HPC Out

MS-RDI HQ-UNEQAU-AIS <1>AU-LOP

HO PATH SIGNAL PASSED TH <1>HO VC WITH POH AND UNSPECIFIED PAYLOAD TU-AISHO UNEQUIPPED SIGNAL

HP-UNEQHP-DEGHP-EXCHP-TIM *1 <1>

HP-PLMFHP-BIP ERRORHP-FEBEHP-RDIHP-RDIHP-FEBE <1>

TU-AISHP-LOM/TU-LOP UNUSED LPC

LO PATH SIGNAL PASSED Out/LQ-UNEQLO VC WITH POH AND UNSPECIFIED PAYLOAD <1>LO UNQUIPPED SIGNAL

LP-UNEQ <1>LP-DEGLP-EXCLP-TIM *1LP-PLMFLP-BIP ERRORLP-FEBELP-RDILP-RDILP-FEBE

AISLOS

AIS PPI-AIS PPI-EXC PPI-DEG

Multiplex Section Higher Order Path Lower Order Path

NOTE: ● Detection ○ Generation <1> Insertion of all-ones (AIS) signal *1 Both AIS and RDI insertion is user selectable. Not configured PKG should send.

blog presentation

Design

maintenance operation

q11 operation

operation controls

maintenance nec corporation

view operation logs

maintenance contents

maintenance windows

maintenance operator