F05 Work

F5259_F05
SpectralWave V-Node
STM-16/ STM-4/ STM-1 Multiplexer RELEASE 3.10
FUNCTIONAL DESCRIPTION
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
F5259_F05 FUNCTIONAL DESCRIPTION
SpectralWave is a registered trademark of NEC Corporation.
Copyright 2005-2006 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 July 2006 Printed in China
CONTENTS
1. SDH WORKING PRINCIPLE 1-1
1.1 Signal Multiplexing Paths ................................................................ 1-1 1.2 Basic Parameters ............................................................................. 1-2
1.2.1 1.2.2 1.2.3 1.2.4 Frame Structure .................................................................................... 1-2 Multiplexing Structure and Multiplexing Methods............................. 1-2 Frame Synchronization and Line Code Type ..................................... 1-3 Overhead Function ............................................................................... 1-3
2. V-NODE WORKING PRINCIPLE
2-1
2.1 Login/Logout..................................................................................... 2-1 2.2 Layer 2 Switch Function .................................................................. 2-2

2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.2.6 2.2.7 2.2.8 2.2.9 Learning Bridge .................................................................................... 2-2 Broadcast Storm Filtering.................................................................... 2-5 Maximum Frame Size ........................................................................... 2-8 Maximum Bridge Transmit Delay ...................................................... 2-10 Low Queue Delay Bound.................................................................... 2-13 Maximum Queue Delay Time ............................................................. 2-13 VLAN mode.......................................................................................... 2-15 Spanning-Tree Protocol ..................................................................... 2-31 Trunk .................................................................................................... 2-44
2.2.10 Port monitor configuration ................................................................ 2-47 2.2.11 MAC filtering........................................................................................ 2-49 2.2.12 Service priority configuration............................................................ 2-54
2.3 Encapsulation and LCAS Function ............................................... 2-57

2.3.1 2.3.2 Encapsulation ..................................................................................... 2-57 LCAS .................................................................................................... 2-66
2.4 Cross connection ........................................................................... 2-72

2.4.1 2.4.2 2.4.3 Matrix structure................................................................................... 2-72 Cross-connect level............................................................................ 2-72 Cross-connect type ............................................................................ 2-73
2.5 Protection........................................................................................ 2-84

2.5.1 MSP ...................................................................................................... 2-84
Contents i
2.5.2 2.5.3 2.5.4 2.5.5
MS-SP Ring.......................................................................................... 2-88 SNCP .................................................................................................... 2-90 Hardware Protection........................................................................... 2-92 Overhead protection........................................................................... 2-96
2.6 Synchronization............................................................................ 2-100

2.6.1 2.6.2 2.6.3 2.6.4 Timing source ................................................................................... 2-100 Timing source control ...................................................................... 2-100 Timing source selection................................................................... 2-103 DNU Group ........................................................................................ 2-105
2.7 Trace/signal label function .......................................................... 2-106 2.8 Configuration Management ......................................................... 2-108 2.9 Performance monitor ................................................................... 2-110
2.9.1 2.9.2 2.9.3 2.9.4 2.9.5 2.9.6 2.9.7 The Definition of PM item................................................................. 2-110 Performance Counter Range ........................................................... 2-118 SES..................................................................................................... 2-122 Invalid condition ............................................................................... 2-123 Register management ...................................................................... 2-123 PM reset function.............................................................................. 2-124 TCA .................................................................................................... 2-124
2.10 Fault management ........................................................................ 2-131

2.10.1 Fault monitor items........................................................................... 2-131 2.10.2 Alarm management........................................................................... 2-140 2.10.3 Alarm report ...................................................................................... 2-141
2.11 Maintenance Management ........................................................... 2-143

2.11.1 Unit Rest ............................................................................................ 2-143 2.11.2 Equipment Initialization.................................................................... 2-144 2.11.3 Loopback ........................................................................................... 2-145 2.11.4 Software Download........................................................................... 2-147 2.11.5 Software Upgrade ............................................................................. 2-149 2.11.6 Configuration Download/Upload ..................................................... 2-150 2.11.7 Automatic Laser Shutdown ............................................................. 2-151 2.11.8 Overhead Function ........................................................................... 2-155 2.11.9 House Keeping.................................................................................. 2-156 2.11.10Security management ...................................................................... 2-157
2.12 Memory Management ................................................................... 2-161

2.12.1 Database Distribution....................................................................... 2-161 2.12.2 Database Action................................................................................ 2-161
Contents ii
2.13 OW Function ................................................................................. 2-169

2.13.1 OW interface...................................................................................... 2-169 2.13.2 OW function....................................................................................... 2-169 2.13.3 Calling method .................................................................................. 2-170 2.13.4 Branch function ................................................................................ 2-170 2.13.5 Sequence description....................................................................... 2-171 2.13.6 Idle code ............................................................................................ 2-171
2.14 LAPD/Network /Routing Protocol................................................ 2-172 2.15 Real Time Clock System .............................................................. 2-173
2.15.1 Features ............................................................................................. 2-173 2.15.2 Block Diagram................................................................................... 2-174
2.16 Equipment Cooling System ......................................................... 2-174

2.16.1 The threshold of the fan speed........................................................ 2-174 2.16.2 The LED Status of FAN Board ......................................................... 2-174
2.17 Power Management System ........................................................ 2-175 2.18 Retiming Buffer............................................................................. 2-175
2.18.1 Functional Description and Block Diagram ................................... 2-175
2.19 LOG................................................................................................ 2-176
3. EXTERNAL INTERFACES
3-1
3.1 User channel ..................................................................................... 3-1 3.2 Orderwire........................................................................................... 3-1 3.3 User Interface.................................................................................... 3-2
3.3.1 3.3.2 CID Interface.......................................................................................... 3-2 NMS ........................................................................................................ 3-3
3.4 Physical Specification...................................................................... 3-4

3.4.1 V-Node Subrack Dimensions............................................................... 3-4
Contents iii
This page is intentionally left blank.
1. SDH WORKING PRINCIPLE

1.1 Signal Multiplexing Paths
Figure 1-1 shows the functional diagram of signal multiplexing paths:
Figure 1-1. STM-N Signal Multiplexing Paths
SDH Working Principle 1-1
1.2 Basic Parameters

1.2.1 Frame Structure
Basic frame structure is shown in Figure 1-2. Basic Frame Structure
See also Table 1-1 for the frame structure parameter of STM-N (N=1/4/16).
270 N columns (bytes) 9N 261 N
Section overhead SOH Administrative unit pointer(s) STM-N payload Section overhead SOH 9 rows
3 4 5
T1518000-95
Figure 1-2. Basic Frame Structure
Table 1-1. Frame Structure Parameter of STM-N
Grade STM-1 STM-4 STM-16
Rate 155.520 Mb/s 622.080 Mb/s 2488.32 Mb/s
N 1 4 16
Frame length 2430 BYTES 9720 BYTES 38880 BYTES
Frame cycle 125 us 125 us 125 us
1.2.2 Multiplexing Structure and Multiplexing Methods

Multiplexing structure is provided in Figure 1-1. Multiplexing STM-1 to STM-N or AUG to STM-N adopts multiplexing methods of byte interval insertion. Administrator unit (AU) multiplexing to STM-N frame, and tributary mapping to VC-4 conform to ITU-T relative references and the requirement of national optic synchronous transmission technical system completely.
1.2.3 Frame Synchronization and Line Code Type

1.2.3.1 Frame Synchronization Frame synchronization bytes A1/A2 are transmitted at STM-1/STM-4/STM-16 output port, and received at the corresponding input port to align the frame according to their fixed pattern. If 5 continuous frame codes fail (neither A1 nor A2 is detected), the frame goes out of synchronization, and the OOF (out of frame) alarm is issued. While in the OOF status, it is considered to have searched frame signal after continuously receiving correct A1 and A2 for two frames. And it is considered that the system goes into LOF status (lost of frame) after OOF lasts 3 ms (24 frames). While in the LOF status, the location of A1 and A2 will be searched again, and is considered to go into alignment frame status after continuously receiving correct A1 and A2 for 3 ms (24 frames), and LOF alarm will disappear. STM-4 optical line interface: NRZ code after serial scrambling by polynomial 1 + X6 + X7 STM-1 optical line interface: NRZ code after serial scrambling by polynomial 1 + X6 + X7 STM-1 electrical line interface: CMI code STM-16 optical line interface: NRZ code after serial scrambling by polynomial 1 + X6 + X7 45M electrical tributary interface: B3ZS code 34M electrical tributary interface: HDB3 code 2M electrical tributary interface: HDB3 code
1.2.4 Overhead Function

1.2.4.1 Section Overhead ( SOH ) V-Node supports section and path OH. The definition of SOH is shown in Figure 1-3, Figure 1-4, Figure 1-5 and Table 1-2. The blanks in the figure and table are reserved to arrange bytes by international, is a byte related to transmission media, is a reserved byte for the civil use, * is a byte that are not scrambled.
9 bytes
A1 A1 B1 D1 9 rows
A1 A2 A2 A2 J0
* RSOH
E1 D2
F1 D3
Administrative Unit pointer(s) B2 B2 D4 D7 D10 S1 B2 K1 D5 D8 D11 K2 D6 D9 D12 M1 E2

T1523130-96
MSOH
Bytes reserved for national use * Unscrambled bytes. Therefore care should be taken with their content Media dependent bytes
NOTE ? All unmarked bytes are reserved for future international standardization (for media dependent, additional national use and other purposes).
Figure 1-3.
SOH of STM-1
Figure 1-4.
SOH of STM-4
Figure 1-5.
SOH of STM-16
Table 1-2.
Byte
Summary for RSOH/MSOH of STM-1, STM-4, and STM-16

Description
Position Position Position (STM-1 frame) (STM-4 frame) (STM-16 frame) Row Byte Row Byte Row Byte Sequence Sequence Sequence Sequence Sequence Sequence
A1 A2
1 1 1
1, 2, 3 4, 5, 6 7
1 1 1
1 thru 12 13 thru 24 25
1 1 1
1 thru 48 49 thru 96 97
J0
D1 D2 D3 D4
thru
3 3 3 6, 7, 8
1 4 7 1, 4, 7
3 3 3 6, 7, 8
1 13 25 1, 13, 25
3 3 3 6, 7, 8
1 49 97 1, 49, 97
Frame Location A1: 11110110 A2: 00101000 As signal of frame locating Section Trace, STM Identifier Substitute C1 in new versions suggestion, encoding to regeneration section DCC (Data Communication Channel) The 192 kbit/s DCC for regenerator section. DCC (Data Communication Channel) The 576 kbit/s DCC for multiplex section. * Not supported in V-Node Orderwire Channel The 64 kbit/s orderwire channel for regenerator section; available on VF communication orderwire channel. Orderwire Channel The 64 kbit/s orderwire channel for multiplex section; available on VF communication orderwire channel. User Channel The 64 kbit/s clear channel reserved for user definition. Error Monitor Detects regenerator section error by BIP-8. Error Monitor on STM-1 Detects multiplex section error by BIP-24. Error Monitor on STM-4 Detects multiplex section error by BIP-96. Error Monitor on STM-16 Detects multiplex section error by BIP-384 APS (Automatic Protection Switching) Used to divert the traffic signal; MS-AIS, MS-RDI Multiplex Section REI (Remote Error Indication) Synchronization Status Message National uses * Not supported in V-Node Illustrating types of transmission media * Not supported in V-Node
D12 E1
13
49
E2
25
97
F1
25
97
B1
B2
1, 2, 3
B2
1 thru 12
B2
1 thru 48
K1 K2 M1 S1
5 5 9 9 12, 9 2, 3
4 7 6 1 8, 9 2, 3, 5
5 5 9 9 12, 9 2, 3
13 25 15 1 29 thru 36 5 thru 12 17 thru 20
5 5 9 9 12, 9 2, 3
49 97 51 1 113 thru 144
In it: K1, K2 Bytes (b1 thru b5): Two bytes are used to initiate APS when the signal degrade (signal failure or the error exceeds specified limits) occurs. Upper 13 bits of K1, K2 bytes are used for line protection. K2 Bytes (b6 thru b8): K2 bytes are used for detecting Multiplex Section Alarm Indicator (MS-AIS), and Remote Defect Indicator (MS-RDI). If received signal fails, or has 111 for the 6 thru 8 bits on K2 byte, it is referred to have MS-AIS signal, which is invalid net load, and send all 1 signal to the terminal. MS-RDI indicates that the received signal is invalid, or has MS-AIS inserted. MS-RDI is an insertion of 110 at b6, b7, b8 bits in K2 byte before scrambled code. S1 Bytes (b5 thru b8): S1 bytes are used to display synchronization status for timing source selection. The 5 thru 8 bits in S1 byte are arranged to indicate synchronization status message. Table 1-3 gives bit-pattern arrangement of four synchronization grades conforming to ITU-T. Table 1-3. S1 Byte Signal
Bits (5 thru 8) in S1 Byte Timing Source Quality and Grade
0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111
Quality unknown Reserved G.811 Reserved G.812 Transit Reserved Reserved Reserved G.812 Local Reserved Reserved G.813 (SETS) Reserved Reserved Reserved Do not use for timing source
SETS: Synchronous Equipment Timing Source

M1 Byte: M1 byte is used for Multiplex Section Remote Error Indicator (MS-REI). This byte in STM-N outputs the count of interleaved bit blocks detected in error by BIP-24 n (B2; see below) to a remote side on a frame-by-frame basis. This value is used at the far-end for its PM. In STM-1: This byte outputs the number of error blocks detected by BIP-24 (range: 0, 24). In STM-4: This byte outputs the number of error blocks detected by BIP-96 (range: 0, 96). In STM-16: This byte outputs the number of error blocks detected by BIP-384 (range: 0, 384). The data more than 384 is processed as 384. BIP operation is listed in Table 1-4: Table 1-4. BIP Operations
Signal Level
BIP-8 (B1) STM-1, STM-4,STM-16
BIP-24 (B2) STM-1
BIP-96 (B2) STM-4
BIP-384 (B2) STM-16
Insertion Target
After scrambling Regenerator Section
Before scrambling Multiplex Section Except the first row of SOH in the previous frame, all bits with even parity of every 24 bits, after scrambling
Before scrambling Multiplex Section Except the first rows of SOH in the previous frame, all bits with even parity of every 96 bits, after scrambling The receiving system recomputes the checksum based upon the received data for multiplex section, and compares the values. Results are transferred and used by the performance monitoring, being a trigger of protection switching.
Before scrambling Multiplex Section Except the first rows of SOH in the previous frame, all bits with even parity of every 384 bits, after scrambling The receiving system recomputes the checksum based upon the received data for multiplex section, and compares the values. Results are transferred and used by the performance monitoring, being a trigger of protection switching.
Computing All bits in the previous frame after Range
scrambling
Processing The receiving system The receiving system recomputes the Principle at recomputes the Reception
checksum based upon the received data for regenerator section, and compares the values. Results are transferred and used by the performance monitoring at the far-end.
checksum based upon the received data for multiplex section, and compares the values. Results are transferred and used by the performance monitoring, being a trigger of protection switching.
1.2.4.2 Payload Pointers Each STM-1 frame includes an AU-4 frame; each STM-4 frame includes four AU-4s; each STM-16 frame includes sixteen AU-4s. Each AU-4 includes two pointers, H1 and H2 bytes group, containing 3 bytes for positive frequency justification and 3 bytes for negative frequency justification. See Figure 1-6:
H2
N N N N S
D I
D I
D I
D I
10 Bit Pointer Value

I: Increment (positive frequency justification bits) D: Decrement (negative frequency justification bits) N: New Data Found (NDF) flags Enabled when at least 3 out of 4 bits match 1001 Disabled when at least 3 out of 4 bits match 0110 Invalid with other codes SS: AU TU type, 10 refers to AU-4 and TU-3. Positive Justification: Invert 5 I-bits Accept majority vote Negative Justification: Invert 5 D-bits Accept majority vote When AIS occurs, the pointer values and other bits are set to all 1.
Figure 1-6.
SDH AU-4 Pointer Coding
1.2.4.3 Path Overhead In addition to the section overhead (SOH), signal overhead of STM-1/4/16 system also contains VC-4/VC-3 and VC-12/VC-11 path overhead (POH). See Figure 1-7 below:
J1 B3 C2 G1 F2 H4 F3 K3 N1 260x9/84x9 bytes data payload
Figure 1-7(a).
VC-4/VC-3 Path Overhead
V5
J2
N2
K4
Figure 1-7(b).
VC-12/VC-11 Path Overhead
The first column of VC-4/VC-3 payload (9 bytes) is dedicated to path overhead information: J1 byte: Path Indication This byte is known as the trace byte, and is user programmable. The trace byte is used as an identification that allows verifying whether it is connected to the designated source/destination.
B3 byte: Quality Monitoring This byte is known as the BIP-8 or B3, and is allocated in each VC-4 for a path error monitoring function using even parity. The path BIP-8 is calculated over all bits of the previous VC-4 before scrambling. The calculated BIP-8 is placed in the B3 byte of the current VC-4 before scrambling. C2 byte: Container Format This byte is known as the signal label, and is used to indicate the composition or the maintenance status of the VC-4. G1 byte: Transmission Error Acknowledgement This byte conveys the path status and performance back to a VC-4 trail termination. This feature permits the status and performance of the complete duplex trail to be monitored at either end, or at any point along that trail. F2, F3 bytes: Path User Channels (Not Supported by V-Node) These bytes are allocated for end-user communication purpose between path elements. H4 byte: Position Indicator This byte is known as the multiframe, and is used as an end-to-end generalized multiframe indicator for payloads (a pointer). K3 byte (b1 thru b4): APS Channel (Not Supported by V-Node) These bits of K3 byte are allocated for automation protection switching (APS) signaling for protection at the VC-4 path level. N1 byte: Network Operator Byte (Not Supported by V-Node) This byte is used to provide a Tandem Connection Monitoring (TCM) function. Spare K3 (b5 thru b8): (Not Supported by V-Node) These bits of K3 byte are reserved for the future use, and have no defined values. The receiver is required to ignore their content. The column of VC-12/VC-11 payload is dedicated to path overhead information: V5 byte: Lower Order Path Signal Label The byte V5 provides the functions of error checking, signal label and path status of the VC-2/VC-1 paths.
J2 byte: Lower Order Path Trace Byte J2 is used to transmit repetitively a Low Order Path Access Point Identifier so that a path receiving terminal can verify its continued connection to the intended transmitter. N2 byte: Network Byte This byte is allocated to provide a Tandem Connection Monitoring (TCM) function. K4 byte: Extended Signal Marker Automatic Protection Switching (APS) channel: K4 (b1-b4), these bits are allocated for APS signaling for protection at the lower order path level. Reserved: K4 (b5-b7), Bit 5 to 7 of K4 are reserved for an optional use described in VII.2 of Appendix VII. If this option is not used, these bits shall be set to "000" or "111". A receiver is required to be able to ignore the contents of these bits. The use of the optional function is at the discretion of the owner of the trail termination source generating the K4 byte. Spare: K4 (b8), this bit is allocated for future use. This bit has no defined value. The receiver is required to ignore its content.
2. V-NODE WORKING PRINCIPLE

2.1 Login/Logout
Login Local NE and Remote NE When the equipment communicates with the CID by direct connection, the equipment can be defined as Local NE. The detail operation steps refer to subsection Login to Local NE of the CID OPERATING GUIDE manual. When the equipment communicates with the CID through optical transmission path and intermediate equipment, the equipment is defined as Remote NE. The detail operation steps refers to subsection Login to Remote NE of the CID OPERATING GUIDE manual. Logout of NE NE should support the following 3 types of logout function: 1) manually logout When the NE received users logout request, the system would logout the users account. 2) automatically logout User password ageing time elapsed from user login and last action, NE should automatically logout; 3) forcibly logout When the communication between the NE and CID is down, the NE would logout of all registered users forcibly. When logout of NE: NE access is over; Delete the logout user from registered user list; Logout user cannot access NE until the next successful login. Record the manually logout action;
V-Node Working Principle 2-1
2.2 Layer 2 Switch Function

V-Node can accommodate Layer 2 Switch (L2SW) function, which includes Leaning Bridge, Port based VLAN, Tagged VLAN, Spanning Tree Protocol, Trunk, Port Monitor, MAC filtering and Priority by using Ethernet package. This section introduces these functions.
2.2.1 Learning Bridge

Learning bridge means the MAC address learning function of the layer 2 switch chip, which manages MAC Address Table by analyzing received Ethernet data frame from each port of the switch chip. 2.2.1.1 MAC Address Learning As the Figure 2-1 shows, if the data frame with both destination address DA and source address SA is received from switch chips specific port such as port1, the switch chip would analyze the direction that VLAN data frame is from, then associate the source address of the received data frame with both receiving port ID and the VLAN ID where the port belongs, and then add it into the MAC Address Table, as shown in Figure 2-2 (consider that the data frame belongs to VLAN x).
Figure 2-1
Figure 2-2
The switch chip forwards the data frame according to the internal MAC Address Table, by the corresponding forwarding mechanism as shown below: When any of VLANx ports (except Port1) receives data frame with destination MAC address SA (the data frame also belongs to VLANx), where the MAC address SA is already in the MAC Address Table (see Figure 2-2), the switch chip forwards the data frame to the Port1 only. If Port1 receives the data frame with destination MAC address SA, the switch chip discards it on Port1, which is commonly said the filtering function of the switch. If MAC address SA is not in the MAC Address Table, the data frame with the destination address SA received from the switching port would be forwarded to all ports in the VLANx. 2.2.1.2 MAC Address Ageing For FE board, the switch chips MAC Address Ageing Interval can be set to No Ageing or N seconds (In V-Node, N = 300 thru 765 seconds; unit = second). When set to No Ageing, the switch chip does not time the MAC address in the MAC address table automatically. As Figure 2-2 shows, where the MAC Address Ageing Interval is set to N seconds, if the Port1 does not receive the data packet with the source address SA again before expiring the specified N seconds, the MAC address entry of SA is deleted from the MAC address table automatically; where the MAC Address Ageing Interval is set to No Ageing mode, the MAC address will be kept in the MAC address table although the Port1 does not receive the data packet with the source address SA. For GE board, the switch chips MAC Address Ageing Interval can be set to No Ageing or N seconds (In V-Node, N = 10 thru 65535 seconds; unit = second). When set to No Ageing, the switch chip does not time the MAC address in the MAC address table automatically.
NOTE: 1. For No Ageing mode, the recorded MAC address in the MAC address table for the switch chip will be deleted as well if in the following conditions: 1> For FE board, when the number of MAC addresses in the MAC address table reaches the maximum capacity (10239 per FE package), MAC addresses will be deleted from the oldest entry to add a new MAC address to the MAC address table. However, for GE board, when the number of MAC addresses in the MAC address table reaches the maximum capacity (16383 per GE package), MAC address table will stop learning the newest MAC address to MAC table. 2> When the switch chip is reset, STP topology is changed, and/or the Ethernet port is changed. 2. MAC Address Ageing may not punctually time for the specified N seconds.
2.2.2 Broadcast Storm Filtering

2.2.2.1 Process Mechanism
Broadcast Storm Filtering means the switch chip filter the Ethernet broadcast frame according to the specific condition, which relax the broadcast data flux, increase the effective network bandwidth. For FE board, the Broadcast Storm Filter functions under the following two conditions: 1. When the broadcast frame flow in the switch chip exceeds the specified threshold. The threshold value is the ratio between the data flux of the broadcast frame and the overall data flux in the internal buffer of the switch chip. 2. The rate of input data becomes greater than that of output data. For example, as shown in Figure 2-3, where all the ports in layer 2 switch work as 100 Mb/s, Port1 receives two kinds of frames: F1 (data flux is 15 Mbit/s; DA1 provides broadcast destination MAC address FF-FF-FF-FF-FF-FF), and F2 (data flux is 94 Mbit/s; DA2 does not provide broadcast destination MAC address); and other port also receives the data frame Fx (total data flux 100 Mbit/s; DAx does not provide broadcast destination MAC address). This state in the buffer of the switch chip forms the proportion of the broadcast data flux to the total as 15/200 = 7.5%, but when the threshold of Broadcast Storm Filtering is 5%, the switch chip prevents the buffer used by the broadcast data from rising over 5% by discarding the redundant broadcast data frames of F1, hence providing relief to the broadcast data flux of F1 via output port, and to the bandwidth occupied by the broadcast data frame.
Figure 2-3 For GE board, the basic principle of the Broadcast Storm Filter functions is similar as FE board. However the filtering function of GE board is more exact than FE board, the filter condition of FE board is based on rate (the rate between the data flux of the broadcast frame and the overall data flux or the rate between the ingress data and the egress data), the GE filter condition is based on PPS (packages per second) that means one port can only received a certain number of broadcast frames (that includes Ethernet broadcast traffic, multicast traffic, and the DLF traffic) per second, while the flux of the data frames exceeds the threshold specified by user, the switch chip will discard the redundant data frames to relieve the flux of the data frame and increase the effective network bandwidth.
2.2.2.2 Configuration For FE board: See Figure 2-4 below. Broadcast Storm Filtering parameter has 6 values to select: 0,5%, 10%, 15%, 20%, and 25%. Select the value, and then click the Set button.
Figure 2-4 Parameter 0 Selecting 0 disables the Broadcast Storm Filtering function. Parameter N% Set Broadcast Storm Filtering for the threshold that is the ratio between data flux of the broadcast frame and the overall data flux in the internal buffer of the switch chip. The greater number (N%) allows the greater proportion of the broadcast frames to the overall capacity of the buffer.
For GE board: See Figure 2-5 below. There are three kinds of filter functions: Broadcast traffic rate, Multicast traffic rate and DLF packets rate. When you enable these functions and enter the threshold (xxx pps means xxx packages per second), the system would carry out the filter function according to your specified threshold.
Figure 2-5 Parameter The applicable parameter ranges are from 0 to 256000, which specified the maximum flux of the data frame. If it takes over the specified threshold, the data frame is discarded.
2.2.3 Maximum Frame Size

NOTE: Maximum Frame Size is unconfigurable on GE board. For FE board, Maximum Frame Size defines the maximum length of the Ethernet frame to let it pass through the FE package. If the length of Ethernet data frame exceeds the specified size, the frame is discarded.
2.2.3.1 Configuration
Figure 2-6 As in the Figure 2-6, enter the maximum Ethernet frame length in the Maximum Frame Size field, and then click the Set button. The applicable parameter ranges are from 1522 to 1568, which should include the VLAN Tag, i.e. it specifies Maximum Frame Size N for an FE/GE package: 1. If the length of received data frame with VLAN Tag is greater than N, the frame is discarded. 2. If the length of received data frame without VLAN Tag is greater than N 4, the frame is discarded. For example, as in the Figure 2-7, F1 frame has VLAN Tag and F2 frame does not. For F1 frame, when its length exceeds the specified size N, this F1 frame is discarded, where the frame within the size passes through to the egress port of the L2SW; For F2 frame, when its length exceeds N 4, this F2 frame is discarded, where the frame within the size of N 4 passes through to the egress port of the L2SW.
Figure 2-7
2.2.4 Maximum Bridge Transmit Delay

NOTE: Maximum Bridge Transmit Delay is unconfigurable on GE board. For FE board, Maximum Bridge Transmit Delay specifies the time period for the switch to buffer the data frame. When the time delayed for the data frame in the switch is greater than Maximum Bridge Transmit Delay, it would be discarded. See Figure 2-8 for example. Since the bandwidth at the ingress is larger than that of egress (as an example of any factors), the frame Fx in the L2SW is stuck at the egress queue, and cannot go through to egress port: Where the Maximum Bridge Transmit Delay is specified to N (N = 1, 2 or 4), if the Fx in the L2SW egress queue fails to be sent to egress port within N seconds, the Fx is discarded. However, when the Maximum Bridge Transmit Delay is set to Disable, the Fx is not discarded by buffering as long as it takes.
Figure 2-8
2.2.4.1 Configuration See Figure 2-9. The Maximum Bridge Transmit Delay parameter has 4 values for selection: Disable, 1, 2, or 4. Select one, and click the Set button. This setup should be determined depending on the type or use of the service. When the system does not require the punctual or quick service, e.g., for file transferring etc., disabling this function increases forwarding capacity of the flow in FE package as possible, regardless of the internal buffer of the switch chip. When the system requires more punctual services, this function should be enabled to avoid affecting quality of service.
Figure 2-9 2.2.4.2 Configuration Parameter Specifying Disable suspends the Maximum Bridge Transmit Delay function. The data frame is allowed being in the buffer of the switch chip regardless of the time period, and is not to be discarded. N defines the time period to allow the data frame held in the internal buffer of the switch chip. If it takes over the specified time period, the data frame will be discarded.
2.2.5 Low Queue Delay Bound

NOTE: Low Queue Delay Bound is unconfigurable on GE board. For FE board, Low Queue Delay Bound specifies enabling/disabling the setting for the Maximum Queue Delay Time. Specifying Enable turns the Maximum Queue Delay Time setup effective. When disabled, the function is suspended regardless of the entry in the Maximum Queue Delay Time field.
Figure 2-10
2.2.6 Maximum Queue Delay Time

NOTE: Maximum Queue Delay is unconfigurable on GE board. For FE board, maximum Queue Delay Time specifies the time period for the data frame buffered in the low priority queue. If the data frame in low priority queue in the switch stays over the specified time period, the data frame is discarded. See Figure 2-11 for example. Since the bandwidth at the ingres is larger than that of egress (as an example of any factors), the frame Fx in the L2SW is stuck in the low egress queues to egress port: Where the Maximum Queue Delay Time is set to N (N = 2 thru 510 ms), if the Fx in the L2SW egress queue fails to be sent to egress
port within X milliseconds, the Fx is discarded. However, when the Maximum Bridge Transmit Delay or Low Queue Delay Bound is set to Disable, the Fx is not discarded by buffering as long as it takes.
Figure 2-11
2.2.6.1 Configuration As in the Figure 2-11, enter the maximum delay required in the Maximum Queue Delay Time field, and click the Set button. 2.2.6.2 Configured Parameter The applicable parameter ranges are from 2 to 510, which specifies the time period to allow the data frame with low priority held in the internal buffer of the switch chip. If it takes over the specified time period, the data frame is discarded.
Figure 2-12 NOTE: This setup is valid only when both Maximum Bridge Transmit Delay and Low Queue Delay Bound are enabled.
2.2.7 VLAN mode

The FE interface package of the V-Node equipment provides two types of VLAN modes: Port based mode and IEEE 802.1Q mode.
Figure 2-13
2.2.7.1 Port Based VLAN 2.2.7.1.1 Port Based VLAN overview
As shown in the Figure 2-13, click the VLAN Mode tab to display VLAN Operation Mode option box, and select Port based from the pull-down menu, then click the Set button. Port Based VLAN mode is a process using the mechanism based on the physical port, which does not use VLAN Tag but Port ID to sort VLAN, hence, in Port Based VLAN, the Ethernet frame will be transparently forward from ingress port to egress port of L2SW without caring the VLAN Tag. That is to say, the mode specially suits for transparent transmission of Ethernet layer 2 data frame without occupying VLAN Tag resource. Either VLAN1 and VLAN2 can use the same VLAN Tag repeatedly, but the two VLANs should be separated completely by the physical port. See Figure 2-14 below:
Figure 2-14 2.2.7.1.2 Port Based VLAN process mechanism
Following shows the mechanism of the switch chips process for the data frame regarding the Port Based VLAN mode:
Table 2-5
Process Mechanism for Port Based VLAN
Port Configuration Tagged/ Untagged In Filter Setting Tagged Frame (VID=1)
Frame on Ingress Direction( Figure Untagged Frame Priority Tagged Frame (VID is 0)
2-15 )
Tagged Frame Tagged Frame (VID=1) Untagged Frame
Frame on Egress Direction( Figure Priority Tagged Frame (VID is 0)
2-15 )
Tagged Frame with PVID Tagged Frame
Priority Tagged Frame (VID is not 0)
N/A
N/A
Transparent
Transparent
Transparent
Transparent
Transparent
Transparent
Transparent
Transparent
Transparent
N/A
Transparent
Figure 2-15
2.2.7.2 IEEE 802.1Q VLAN 2.2.7.2.1 IEEE 802.1Q VLAN overview
Click the VLAN Mode tab to display VLAN Operation Mode option box, and select IEEE 802.1Q from the pull-down menu, then click the Set button. IEEE 802.1Q VLAN mode is a process using the mechanism based on VLAN Tag, which sorts VLAN according to the VLAN Tag within ranges from 0 to 4095. This mode supports the function, such as VLAN Trunk, defined by IEEE802.1Q, and can be applied in the more complicated network. NOTE: For the frame with VID = 4095: 1. its forwarded transparently under the Port-based VLAN mode. 2. its discarded under the IEEE802.1Q mode.
2.2.7.2.2
IEEE 802.1Q VLAN process mechanism
Following shows the mechanism of the switch chips process mechanism for the data frame regarding the IEEE 802.1Q VLAN mode:
Table 1-6
Process Mechanism for IEEE802.1Q VLAN
Frame on Ingress Direction(Figure Untagged Frame Priority Tagged Frame (VID is 0)
2-15)
Frame on Egress Direction(Figure Priority Tagged Frame (VID is 0) Priority Tagged Frame (VID is not 0)
2-15)
Not Configured
Forward Match VID
Pass through
add VLAN tag with Port VID=1
change VID to Port VID=1
Discard Frame with undefined VID other than VID=1
Remove VID1 and forward frame to egress direction
N/A
N/A
Remove VID and forward only frame with VID=1 that configured by FW acquiescently
Drop Untagged Frame Enable All
Pass through
Discard
Discard
Forward only VID=1
Forward only VID=1
Pass through
Discard
Discard
Discard Frame with undefined VID other than VID=1 Forward only VID=1
Disable All
Pass through
Forward only VID=1
Untagged IF VID=x
Forward Match VID
Discard
add VLAN tag with Port VID=x
change VID to Port VID=x
Discard undefined VID Frame Forward only configured VID frame
Discard
N/A
N/A
Remove and forward only configured VID frame
Drop Untagged Frame
Pass through
Discard
Discard
Forward only configured VID frame
( Next Page Continued )

Frame on Ingress Direction(Figure Untagged Frame Priority Tagged Frame (VID is 0)
2-15)
Frame on Egress Direction(Figure Priority Tagged Frame (VID is 0) Priority Tagged Frame (VID is not 0)
2-15)
Untagged IF VID=x
Enable All
Discard
Discard
Discard
Discard
N/A
N/A
Disable All
Pass through
add VLAN tag with Port VID=x
change VID to Port VID=x
Tagged
Forward Match VID
Pass through
Remove VID1 and forward frame to egress direction
N/A
N/A
forward only configured VID frame
Drop Untagged Frame Enable All
Pass through
Discard
Discard
Pass through
Discard
Discard
Disable All
Pass through
2.2.7.2.3
IEEE 802.1Q VLAN Overview
1. Default VLAN The IEEE802.1Q VLAN mode has the default VLAN in the bridge that is defined by FW. See Figure 2-16below:
Figure 2-16 When specifying a VLAN with Untagged to some ports, these ports will be excluded from the default VLAN, where other ports with Tagged setting are taken as the default VLAN. See Figure 2-17 below:
Figure 2-17 When specifying a VLAN with Untagged to some ports, these ports will be excluded from the default VLAN, where other ports with Tagged setting are taken as the default VLAN. See Figure 2-18 below:
Figure 2-18 VLAN Setting: LAN1-a-U, WAN1-a-T 2. IEEE802.1Q VLAN
Figure 2-19 VLAN Setting: LAN1-a-U, WAN1-a-U LAN2-b-U, WAN2-b-T LAN3-c-T, WAN3-c-T LAN4-d-T, WAN4-d-U LAN4-e-U There are six VLANs in bridge included for the default VLAN. 3. Port Filtering Application Overview 3.1 Untagged Frame processing 3.1.1 Ingress Filter: Disable All or Forward Match VID on all ports
Figure 2-20 NOTE: UF denotes Untagged Frame, and TFx denotes Tagged Frame with VID x(here x represents characters a ,b ,c, etc.). See Figure 2-20 above. If an untagged frame is received from LAN1, this frame, after a VID a is added at the ingress direction, is forwarded to WAN1 only, then the VID is removed at the egress direction. If an untagged frame is received from LAN2, this frame, after a VID b is added at the ingress direction, is forwarded to WAN2 only, but the VID is not removed at the egress direction. 3.1.2 Ingress Filter: Enable All or Drop Untagged Frame on all ports
Figure 2-21 See Figure 2-21 above. If an untagged frame is received from LAN1, this frame will be dropped by ingress filter on LAN1.; If an untagged frame is received from LAN2, this frame will be dropped by ingress filter on LAN2. 3.1.3 Ingress Filter: Disable All or Forward Match VID on all ports
Figure 2-22 See Figure 2-22 above. If an untagged frame is received from LAN3, this frame will be dropped by ingress filter on LAN3. 3.1.4 Ingress Filter: Enable All or Forward Match VID on all ports
Figure 2-23 See Figure 2-23 above. If an untagged frame is received from LAN3, this frame will be dropped by ingress filter on LAN3. 3.1.5 Ingress Filter: Enable All or Forward Match VID on all ports
Figure 2-24 See Figure 2-24 above. If an untagged frame is received from LAN4, this frame will be dropped by ingress filter on LAN4. 3.1.6 Ingress Filter: Enable All or Drop Untagged Frame on all ports
Figure 2-25 See Figure 2-25 above. If an untagged frame is received from LAN4, this frame will be dropped by ingress filter on LAN4. 3.2 Tagged Frame processing 3.2.1 Ingress Filter: Disable All or Drop Untagged Frame or Enable All or Forward Match VID on all ports
Figure 2-26 See Figure 2-26 above. If a tagged frame (VID = a) is received from LAN1, this frame belongs to VLANa, so that the frame is forwarded to WAN1 only, then the VID is rmoeved at the egress direction. If a tagged frame (VID = b) is received from LAN2, this frame belongs to VLANb, so that the frame is forward to WAN2 only, but the VID is not removed at the egress direction; If a tagged frame (VID = c) is received from LAN3, this frame belongs to VLANc, so that the frame is forwarded to WAN3 only, but the VID is not removed at the egress direction; If a tagged frame (VID = d) is received from LAN4, this frame belongs to VLANd, so that the frame is forwarded to WAN4 only, then the VID is removed at the egress direction.
3.2.2 Ingress Filter: Disable All or Drop Untagged Frame or Enable All or Forward Match VID on all ports.
Figure 2-27 See Figure 2-27 above. Iif a tagged frame(VID = e) is received from LAN4, this frame belongs to VLANe, so that the frame is dropped at the egress direction. 3.2.3 Ingress Filter: Disable All or Drop Untagged Frame on all ports
Figure 2-28 See Figure 2-28 above. If a tagged frame (VID = b) is received from LAN1, this frame is dropped by ingress filter on LAN1. If a tagged frame (VID = e) is received from LAN3, this frame is dropped by ingress filter on LAN3. 3.2.4 Ingress Filter: Enable All or Forward Match VID on all ports
Figure 2-29
See Figure 2-29 above. If a tagged frame (VID = b) is received from LAN1, this frame is dropped by ingress filter on LAN1. If a tagged frame (VID = e) is received from LAN3, this frame is dropped by ingress filter on LAN3. 3.2.5 Ingress Filter: Disable All or Drop Untagged Frame on all ports
Figure 2-30 See Figure 2-30 above. If a tagged frame (VID is not specified; x a, b, c, d, e, or 1) is received from LAN1, this frame will be dropped. If a tagged frame (VID is not specified; x a, b, c, d, e, or 1) is received from LAN2, this frame will be dropped. If a tagged frame (VID is not specified; x a, b, c, d, e, or 1) is received from LAN3, this frame will be dropped. If a tagged frame (VID is not specified; x a, b, c, d, e, or 1) is received from LAN4, this frame will be dropped. 3.2.6 Ingress Filter: Enable All or Forward Match VID on all ports
Figure 2-31 See Figure 2-31 above. If a tagged frame (VID is not specified in this port; x a) is received from LAN1, this frame will be dropped by ingress filter on LAN1; If a tagged frame (VID is not specified in this port; x b) is received from LAN2, this frame will be dropped by ingress filter on LAN2; If a tagged frame (VID is not specified in this port; x c, or 1) is received
from LAN3, this frame will be dropped by ingress filter on LAN3; If a tagged frame (VID is not specified in this port; x d, or e) is received from LAN4, this frame will be dropped by ingress filter on LAN4.
2.2.8 Spanning-Tree Protocol

2.2.8.1 STP Configuration V-Node supports STP (Spanning-Tree Algorithm and Protocol) that is a link management protocol, which prevents undesirable loops in the Ethernet network. 2.2.8.2 STP protocol configuration Use STP Config option box in the Layer 2 Configuration dialog box to specify STP protocol parameter and to display the related information on STP protocol. An example of the STP Config option box is shown below:
Figure 2-32 Following are the items to be specified: 1. STP Action Specify to enable/disable the STP protocol. (default: Enable) 2. Bridge Hello Time Specify the output interval of BPDU that should be sent by the root network bridge. A range is from 1s to 10s. (default: 2s) NOTE: BPDU denotes the Bridge Protocol Data Unit. 3. Bridge Forward Delay Time
Specify a period for the timer used by STP port in the Learning and Listening state. When the port status changes from blocking to forwarding, both Learning and Listening status need to be passed. A range is from 4s to 30s. (default: 15s) 4. Bridge Max Age Specify the Maximum Age timer that measures the age of received protocol information to ensure if or not to discard it. A range from 6s to 40s. (default: 20s) 5. Bridge Priority Specify the Bridge (switch) Priority that can assign the root bridge to any bridge. This priority is used for a part of Bridge ID. The bridge with highest priority (the least number) serves as a root bridge. A range is from 0 to 65535. (default is 32768) Following are the items to be displayed: The corresponding STP protocol information displayed in the middle of STP Config is listed below: 1. STP Action Current protocol enable status. 2. Bridge Hello Time The time interval of BPDU configuration sent by root Network Bridge. 3. Bridge Forward Delay Time The learning and listening time used by STP port. 4. Bridge Max Age Maximum survived time of BPDU configuration. 5. Bridge Priority Network Bridge priority. 6. STP Standard The currently selected protocols standard. This selection cannot be changed. 7. Bridge Address MAC address of the Network Bridge (factory adjusted). Each network bridge is designated to have unique address. The address is part of Bridge ID that identifies the network bridge. 8. Root Bridge ID
The currently registered ID for the root Network Bridge. The Root Bridge ID contains both Bridge Priority and Bridge Address. Each network bridge is designated to have unique address. The ID is used for identifying the root network bridge. The ID of root Network Bridge is made of two parts, the first part indicates the priority of the Network Bridge, and the second part is the MAC address of the Network Bridge. 2.2.8.3 STP port configuration Use STP Port option box in the Layer 2 Configuration dialog box to view/edit the specified STP protocol parameter and the related information on STP protocol. An example of STP Port option box is shown below:
Figure 2-33 Following are the items to be displayed: 1. STP Control Shows/Modifies Enable(d)/Disable(d) state for the STP protocol of the target port. The port specified to disable does not manage any BPDU and is not related to any STP action. Default on LAN port is Disable, default on WAN port is Enable. 2. Link Cost Shows/Modifies the ports link cost. A range is from 0 to 255. (default: 128)
3. Port Priority Both the port priority and the No. of the port are form the port ID. Each port of the network bridge has unique port ID. The least numbered ID has the higher the priority. A range is from 0 to 255. (default: 128) 4. Port Status The STP status of the port: The port has five statuses: forwarding, learning, listening, blocking, and disabled. When the STP control is set to Disable, port has two statuses: forwarding and disabled, which is defined by STP algorithm. 2.2.8.4 STP basic principle Once Spanning-Tree Algorithm and Protocol has been carried out, the dynamic tree topologic structure will be formed, which prevents undesirable loops among any two NEs, hence it manages to provide no broadcast storms caused by the loops. At the same time, the Spanning-Tree Algorithm reconfigures the spanning-tree topology and reestablishes the link by activating the standby path. if a failure occurs in the tree structure. 2.2.8.5 Principal and algorithm 1. The term definition: Root bridge: the bridge with the highest priority: Root link cost: the summation of the link cost on all hops from the bridge to the root bridge. Root port: the port with the lowest root link cost in the bridge; among the ports with the same root link cost, the one with highest priority will be the root port. Designated bridge: the bridge with the lowest root link cost in the network Designated port: the port between the network and designated bridge; if more than one port is on the line, the one with highest priority will be the designated port.
The ports status is ruled by Spanning-Tree algorithm, which includes five statuses: forwarding, learning, listening, blocking and disable. 2. The Spanning-Ttree algorithm is based on the following: The unique group address identifies all bridges in a specific network. Each bridge has a unique bridge identifier: Each bridges port has a unique port identifier 3. The configuration management for the Spanning-Ttree requires: Coordinate a relative priority for each bridge; Coordinate a relative priority for each bridges port; Coordinate a link cost for each port. 4. BPDU coding: BPDU frame is sent periodically among the bridges to exchange the Spanning-Tree configuration information, responding the change of network topology, cost or priority quickly. Two kinds of BPDU are used: the configuration BPDU that covers configuration information, and the topology-change notification BPDU that is output when the topology structure changes. Following shows the coding of both the configuration BPDU and the topology-change notification BPDU:
(Change notification BPDU)
(Configuration BPDU) 5. Following are the necessary key elements to form a Spanning-Tree: Decide root bridge a. At the beginning, all bridges take themselves as a root bridge; b. The bridge sends the configuration BPDU with the same root ID and bridge ID to the network connected. c. The frame of its own is discarded if the value of the received root ID is greater than its own, otherwise, the parameter, such as bridges root id, root link cost, are updated, and output the broadcast configuration BPDU with new value continually. Decide root port The port with lowest root link cost in a bridge is called root port. Among the
ports with same lowest root link cost, the port with highest priority is called root port. Among the ports with the same lowest root link cost and highest priority, the port with least numbered port is called root port. Decide networks designated bridge a. At the beginning, all bridges take themselves as the networks designated bridge. b. The bridge would not affirm itself as designated bridge when the bridge receives the BPDU with lower root link cost (in the same network) from other bridge. If in the network, among the bridges with the same root link cost, the bridge with highest priority will be the designated bridge, and other bridges ports connected with root is set to block status. c. If the designated bridge receives a configuration BPDU from other bridge competing for the designated bridge, the designated bridge outputs a response configuration BPDU to declare being the designated bridge again. Decide designated port The designated port is the one connected with the network in the designated bridge. If designated bridge has two or more ports connected with this network, the one with least numbered ID will be the designated port. Except the root port and designated port, other ports will be set into the block status. Thus, a Spanning-Trees topology structure is configured when the root bridge, the bridges root port, as well as each networks designated bridge and designated port are specified. 6. Topology change Topology information transmitted in the network is limited by time; the time information is included in the each configured BPDU, which is called message time. Each bridge stores the protocol information of the designated port from the network, and monitors the time of this information buffered. In both normal and stable status, root bridge sends configuration message to ensure that the topology information is not expired. If root bridge invalid, the protocol information in the other bridges will be expired, the now topology structure will be transmitted in the network quickly. When a bridge detects the change of the topology, it will send BPDU of topology-change notification to the designated bridge in the root bridge direction periodically according to the time interval in the topology-change notification timer ( the confirmation information is configured in the BPDU and called topology change flag), at the same time, the designated bridge
repeat the above procedure, continue to send BPDU of topology-change notification to the bridge along the direction to the root bridge. The notification could be transmitted to the root bridge finally. Once the root bridge receives a notification, or itself changes the topology structure, it will send configuration BPDU for a period of time, the topology change flag in the configuration BPDU is set. All bridges would receive one or more configuration messages, and age the address in the filtering database by the forwarding delay parameter. All bridges would choose again the root bridge, the root port of the bridge and designate bridge and designated port in each network; the Spanning-Trees topology structure is reconfigured. 2.2.8.6 STP application overview See Figure 2-34 for an example regarding the STP application. Bridge 1&10: VLAN X: LAN1 (Tag),WAN1(Tag),WAN2(Tag) VLAN Y: LAN3 (Tag),WAN4(Tag) VLAN 1: LAN1(Untag), WAN1 (Untag), WAN2(Untag), LAN3(Untag), WAN4 (Untag) Bridge 2~9 & X: VLAN X: LAN1 (Tag),WAN1(Tag),WAN2(Tag) VLAN Y: LAN3 (Tag),WAN3(Tag),WAN4(Tag) VLAN 1: LAN1 (Untag),WAN1(Untag),WAN2(Untag),LAN3(Untag), WAN3(Untag), WAN4(Untag)
Figure 2-34 2.2.8.6.1 VLAN
Because the STP based on 802.1D is global STP, and it is not limited in the VLANs broadcast field, the STP cant be working on the whole network when the service is transmitted through multiple fields divided by the VLAN. The part ports STP function is required to close, and the closed ports STP protection is invalid, when these ports present on the ring, the service would be flood and the network result in the paralysis finally. As the Figure 2-35 shows, STP is effective in the VLAN xs broadcast field, VLAN y s field is not protected. The formed tree topology shows as below:
Figure 2-35
2.2.8.6.2
Ring preventing
To avoid the ring, STP function must be combined with VLAN function. Many potential rings exist, as shows below:
Figure 2-36 1. Ring Loop1 in the VLAN X The ring is prevented by STP function 2. Loop210 in the default VLAN 1 The VLAN entrance filtering function is required to configure for the ring preventing as the VLAN1 broadcast field is not protected by the STP function. The filtering rule on the WAN port can be set as Enable All to avoid Untagged frame is transmitting on the network; the filtering function on the LAN port is configured according to external subscribers equipment or network. If VLAN is supported at the subscriber side, the filtering rule on the LAN port entrance may be set as Enable All, the data input from the subscriber side carry the designated VLAN ID to avoid Untagged data frame enter network completely; otherwise, to avoid the data frame with VID = 1 enters the network, LAN port is required to assign to designated VLAN by Untagged mode, and entrance filtering rule is set as Forward Matched VID. 3. The ring Loop X networked by LAN port
Since networking directly, and any subscriber equipment is not passed, the entrance filtering rule on the LAN port is set as Enable All. 4. The ring Loop A in the VLAN Y It can not be protected for the ring of the VLAN Y broadcast field formed by the false connection. For example, the ring formed by the WAN3 of the bridge2 and WAN4 of the bridge3 by false connection. When the case is happened, it only can be found and recovered manually. 5. The ring formed by the external subscriber network The case is not caused by the V-Node equipment, it is out of protection. 2.2.8.6.3 Root bridge
STP spanning tree is based on the root node, the stability of the root node affect the one of whole networks STP function. Hence there are some basic rules on the choice of root node. The root bridge can be decided by the bridge priority. We usually choose the NE as the root node, which is located in the center node (such as aggregative node), and has the most abundant network resource. Take the Figure 2-37 as instance, since it is located in the cross point between the ring and the link network, it is more suitable that the Bridge 2 is considered as root node. Except the above, we can optimize the network load according to the final network data flux. For example, at the beginning, the Bridge 2 is set as root, suppose that blocking is happened at the port between the Bridge 6 and Bridge 7, if there are a large numbers of service flows to Bridge 6 on the Ethernet shared ring, at the same time, there is service to Bridge 6 from the branch, the root ports load of the Bridge 6 becomes more heavier, the link along this direction would congest more. At this moment, changing the network bridges priority make Bridge 6 root become the network bridge, at the same time, make the blocking happened at the port between Bridge 1 and Bridge 2, The network flow of the brdige1 and bridge7-10 will be distributed, the bandwidth requirement from the Bridge 2 to Bridge 6 is relaxed.
Figure 2-37 2.2.8.6.4 Network Diameter
The default of the STPs network diameter is 7. STP protocol parameter needs to be changed for greater network. Changing STP protocol parameter is required to satisfy the formula as below: 1. 2. Bridge Max Age >= 4*Bridge Hello Time + 2*Maximum Bridge Diameter 2 Bridge Forward Delay >= (4*Bridge Hello Time + 3*Maximum Bridge Diameter)/2
Maximum Bridge Diameter means maximum network diameter. Take the Figure 2-37 as instance, there are 10 NEs in the Ethernet ring, the network diameter is 9, when Bridge Hello Time is set as 2s: 1. 2. Bridge Max Age >= 24 Bridge Forward Delay >= 18
By the above formula, we can get the maximum network diameter 17 when set Bridge Max Age=40s, Bridge Forward Delay=30s, while the Bridge Hello Time is set as 2s.
2.2.9 Trunk
NOTE: For GE board, only the same speed ports can be configured as the trunk group. Trunk function is called as link aggregation in other word.
Figure 2-38 Both the LANm and the LANn can be configured as the TRUNK Group1, and both the WANx and the WANy can be configured as the TRUNK Group2, which is shown as Figure 2-38, then the switch chip processes each trunk group as a logical port. The Ethernet data frame from both the LANm and the LANn will be forwarded to both the WANx and the WANy averagely according to the source address as well as the destination address and the port ID, for example, the data frame from both the LANm and the LANn can be divided into many kinds according to the source address as well as the destination address and the port ID, the first kind will be forwarded to the WANx, the second kind to the port WANy, the third kind to the port WANx, and the fourth kind to the port WANy , and so on; and same thing happens along the opposite direction. Since the data frame is almost forwarded to the ports of the trunk group randomly, the maximum effective bandwidth via trunk group should be according to the actual situation. For example, when the Ethernet data frame from both the LANm and the LANn is forwarded to both the ports WANx and WANy, when the bandwidth of the WANx is not equal to the one of the WANy, and the bandwidth of the WANx is A, the bandwidth of the WANy is B (A>B), the effective bandwidth range of TRUNK Group2 is from 2*B to A+B.
NOTE: GE trunk port selection rule: 1) Each trunk has a root port. 2) For all DLF, broadcast, multicast packets, it was set from this root port. 3) For uni-cast packets, port selection rule is SA (source MAC address) XOR DA (destination MAC address), and get the last three bits, and then select a port to send. Instance: when the Ethernet data frame from both the LANm and the LANn is forwarded to both the ports WANx and WANy, when the bandwidth of the WANx is not equal to the one of the WANy, and the bandwidth of the WANx is 42*vc12, the bandwidth of the WANy is 21*vc12: 1. If the traffic forwarded to the port WANx is 21*vc12, and the traffic forwarded to the port WANy is 42*vc12, the maximum effective bandwidth of TRUNK Group2 should be the minimum: 2*21*vc1242*vc12, which shown as the Figure 2-39 below.
Figure 2-39 the maximum effective bandwidth is: 2*21*vc12=42*vc12 2. If the traffic forwarded to the port WANx is 42*vc12, the traffic forwarded to the port WANy is 21*vc12, the maximum effective bandwidth of TRUNK Group2 should be the maximum: 42*vc12+21*vc12=63*vc12, which shown as the Figure 2-40 below.
Figure 2-40 the maximum effective bandwidth is: 42*vc12+21*vc12=63*vc12 To increase transmission bandwidth, trunk function is useful. When WAN #1 and WAN #2 are in the trunk group and each VC of WAN is VC12xV, x=21, in this case, maximum transmission bandwidth reaches to more than 60Mbps. In the same VLAN group, trunk port group can be configured. To use trunk function, L2SW at the opposite side should be accommodated by FE boardof V-Node because frame distribution algorithm should match with each other at local side and remote side. In NE management dialog Box, Select LAN-InterfaceLayer 2 Configuration Trunk, the popup window Figure 2-41 is CIDs Trunk function interface. Its used to set Trunk parameters.
Figure 2-41
Trunk Function Interface
2.2.10 Port monitor configuration

The port monitor function can monitor both the input and the output data over the service port by the idle port. The function configuration is introduced chiefly as below: 2.2.10.1 Monitor configuration
The corresponding information of the monitor configuration is located at the monitor part of page Bridge in the Layer 2 Configuration configuration menu; the configuration interface is shown as below:
Figure 2-42 The items to be configured and queried:
1. Monitor Mode Configure the monitor mode. The choices include Disable, Ingress, Egress and Both. Default is Disable Disable indicates close monitor function. Ingress indicates monitor the data in input direction. Engress indicates monitor the data in output direction. Both indicates monitor the data in both input and output direction. 2. Monitoring Port Configure the port for monitoring. Ranges from LAN1 to LAN6. 3. Monitored Port Configure the port monitored. Ranges from LAN1 to LAN6 or from WAN1 to WAN4
2.2.10.2
Monitor function
The monitor function is that forward the service in certain direction from the monitored port to the monitoring port by which observes users data.
Figure 2-43 Some points need to be pay attention to use the monitor function: 1. Both the monitored port and monitoring port are required to be in the same VLAN. 2. The flow control frame cant be monitored. 3. The trunk port cant be monitored.
2.2.11 MAC filtering

According to configured information, action to incoming frame can be set. When the frame with specified MAC address as destination is incoming, if the customer wants to discard this frame and this MAC address is configured as discard frame, this frame is discarded in L2SW. For forwarding action, almost the same way is required. This function is used as filtering database with manual operation also.
In NE management dialog Box, Select LAN-Interface Layer 2 Configuration Mac Table, the popup window Figure 2-44 is CIDs Mac Filtering function interface. Its used to set Mac filtering parameters.
Figure 2-44
Mac Filtering Function Interface
The MAC Table configuration is shown as the Figure 2-45, and the Figure 2-46 shows the mechanism of the data frame A with the destination address 00-00-00-00-00-11 processed by the L2SW, when A is input from the LAN1, it is discarded, which is shown as red line; when A is input from the other port with the same VLAN, it is forwarded to the LAN1, which is shown as the blue line.
Figure 2-45
Figure 2-46 The MAC table configuration is shown as the Figure 2-47, the Figure 2-48 shows the mechanism of the data frame A with the destination address 00-00-0000-00-11 processed by the L2SW, regardless A is input from any port of the VLAN, it is discarded, which is shown as red line.
Figure 2-47
Figure 2-48 MAC table is used to define static route and special valuable when Security item of LAN-Interface port configuration is enabled. Following table describes all kinds of frames how to input or output L2SW taking LAN#1 and WAN#1 for example.
Figure 2-49
1. When Security is disabled:

Frame with Destination Address
PORT ACTION (SECURITY = DISABLE) LAN#1 PORT

Forward
00:00:00:00:00:01
WAN#1 PORT
Forward
00:00:00:00:00:01
Discard
00:00:00:00:00:01
Discard
00:00:00:00:00:01
Input
MAC:00-00-00-00-00-01 Other MAC address
Discard Forward Forward Forward
Discard Forward Discard Forward
Discard Forward Forward Forward
Discard Forward Discard Forward
Output
2. When Security is enabled (No Security enabling function for WAN port):
Frame with Destination Address
PORT ACTION (SECURITY = ENABLE) LAN#1 PORT

Forward
00:00:00:00:00:01
WAN#1 PORT
Forward
00:00:00:00:00:01
Discard
00:00:00:00:00:01
Discard
00:00:00:00:00:01
Input
Discard Discard(Note3) Forward Forward
Discard Discard Discard Forward
Output
NOTE: 1) Input and Output directions are based on L2SW (Layer 2 Switch). 2) Meaning of three results is shown below:
Forward Forward Discard Forward the frame only to the port which the MAC address be set in MAC table. Forward the frame on the port. Discard the frame on the port.
3) When the frame with the source MAC address same as the MAC address set in MAC table (in above case, the source MAC address is 00-00-00-00-00-01), this frame will be forwarded on the port.
2.2.12 Service priority configuration

Service priority has three modes: FIFO (First-In First-Out), SP (Strictly Priority), WRR (Weighted Round Robin). We will introduce the function chiefly: 2.2.12.1 Priority configuration
Used for the configuring and querying the service queue, it is located at the queue part of the page Bridge in the Layer 2 Configuration menu. The configuration interface is shown as below:
Figure 2-50 The items to be configured and queried: 1. Queue Mode Configure service queue mode. The choices include FIFO (First-In First-Out), SP (Strictly Priority), WRR (Weighted Round Robin). Default is FIFO. 2. WRR High Weight NOTE: This item only used for the FE board. The weight of high priority service queue under WRR queue mode. A range from 1 to 7, default is 1. 3. WRR Low Weight NOTE: This item only used for the FE board. The weight of low priority queue under WRR queue mode. A range from 1 to 7, default is 1.
4.
WRR Weight NOTE: This item used for the GE board. The weight of each priority queue under WRR queue mode. A range from 1 to 15, default is 1.
5.
User Priority Configure the frame with user priority to process as high or low priority in the bridge of V-Node FE/GE package. The frame with user priority has 8 types priority from 0 to 7, which is carried in "VLAN Header" field of the frame. For the FE board can process two type priorites:"0" and "1", and the 8 types user priority should be specified as "0" or "1". "0" indicates processing the frame with user priority as low priority frame in bridge of V-Node FE unit, and "1" indicates processing the frame as high priority. Default is 0 for the user priority from 0 to 3, and 1 for the user priority from 4 to 7. And for the GE board can process eight type priorities, a range from 0 to 7. Each L2SW chip on the FE package has two priority queues: one high priority queue, and another low priority queue. All switchs port shares the two queues, the input data frame from the all ports enters the corresponding queue for forwarding according to the configured priority control strategy.
Figure 2-51 Similar with the FE board, each L2SW chip on the GE package has eight queues. And all switchs port shares this eight queues; the input data frame from the all ports enters the corresponding queue for forwarding according to the configured priority control strategy.
First-In First-Out (FIFO) The data frame from each port is forwarded according to the order entering the queue not the priority. Strict priority (SP) The frame with high priority configuration is input to the high priority queue, the frame with low priority configuration is input to the low priority queue, the data frame without priority configuration is processed as low priority. The data in the low priority queue only can be sent after the data in the high priority queue. Weighted Round Robin (WRR) For FE package, the frame with high priority configuration is input to the high priority queue, the frame with low priority configuration is input to the low priority queue, the data frame without priority configuration is processed as low priority. The proportion between the output bandwidth of the high priority queue and the one of the low priority queue is assigned by the configured high priority weight and low priority weight. For GE package, each data frame with priority configuration is input into the corresponding priority queue, and the bandwidth of each queue is assigned by the configured priority weight. For instance, the priority weight of each priority queue is :4,6,3,7,9,1,2,5; and the proportion of the output bandwidth is 4:6:3:7:9:1:2:5. Notice the points below on how to use priority service function: Since the priority service is based on the frame with priority, the data is required to carry priority information, the equipment only carry out the classification of priority not addition of the priority for data. The priority service needs to be cooperated with the flow control, it requires the external subscriber equipment support flow control, thereby suppress data sending. Since the priority service is carried out by suppressing the data sending by the flow control, the granularity of the frame affects the precise of flow control. For example: the flow control for the frame with 64 bytes is far more precise than the one with 1518 bytes.
2.3 Encapsulation and LCAS Function

V-Node can accommodate Encapsulation and LCAS function by using FE board. In this section, these functions are introduced.
2.3.1 Encapsulation
NOTE: V-Node FE board supports two kinds of encapsulations: GFP and LAPS; However, GE board only supports GFP encapsulation. 2.3.1.1 GFP Function GFP provides a generic mechanism to adapt traffic from higher-layer client signals over a transport network. Client signals may be PDU-oriented (such as IP/PPP or Ethernet MAC), block-code oriented constant bit rate stream (such as Fibre Channel or ESCON/SBCON). 2.3.1.1.1 Frame Format
The GFP frame format is as following diagram:
Core head The four octets of the GFP Core Header consist of a 16-bit PDU Length Indicator field and a 16-bit Core Header Error Check (cHEC) field. This header allows GFP frame delineation independent of the content of the higher layer PDUs.
PDU Length Indicator (PLI) The two-octet PLI field contains a binary number representing the number of octets in the GFP Payload Area. The absolute minimum value of the PLI field in a GFP client frame is 4 octets. PLI values 0-3 are reserved for GFP control frame usage Core HEC (cHEC) The two-octet Core Header Error Control field contains a CRC-16 error control code that protects the integrity of the contents of the Core Header by enabling both single-bit error correction and multi-bit error detection. The cHEC sequence is calculated over the octets of the Core Header as defined in G(x) = x16 + x12 + x5 + 1. GFP Payload Area The GFP Payload Area, which consists of all octets in the GFP frame after the GFP Core Header, is used to convey higher layer specific protocol information. This variable length area may include from 4 to 65 535 octets. The GFP Payload Area consists of two common components: a Payload Header and a Payload Information field. An optional Payload FCS (pFCS) field is also supported.
GFP Payload Header The Payload Header is a variable-length area, 4 to 64 octets long, intended to support data link management procedures specific to the higher-layer client signal. The structure of the GFP Payload Header is illustrated in the figure.
GFP Type field The GFP Type field is a mandatory two-octet field of the Payload Header that indicates the content and format of the GFP Payload Information field
Payload Type Identifier (PTI) A 3-bit subfield of the Type field identifies the type of GFP client frame. Two kinds of client frames are currently defined, User Data frames (PTI = 000) and Client Manage- ment frames (PTI=100).
Payload FCS Indicator (PFI) A one bit subfield of the Type field indicating the presence (PFI=1) or absence (PFI=0) of the Payload FCS field. Extension Header Identifier (EXI) A 4-bit subfield of the Type field identifies the type of Extension Header GFP. Three kinds of Extension Headers are currently defined, a Null Extension Header (0000), a Linear Extension Header (0001), and a Ring Extension Header (0010).The other is reserved. User Payload Identifier (UPI) An 8-bit field identifying the type of payload conveyed in the GFP Payload Information field. Interpretation of the UPI field is relative to the type of GFP client frame as indicated by the PTI subfield. Type HEC (tHEC) The two-octet Type Header Error Control field contains a CRC-16 error control code that protects the integrity of the contents of the Type Field by enabling both single-bit error correction and multi-bit error detection. The Type header consists of the Type field and the tHEC. Extension HEC (eHEC) The two-octet Extension Header Error Control field contains a CRC-16 error control code that protects the integrity of the contents of the extension headers by enabling both single-bit error correction (optional) and multi-bit error detection. Payload Frame Check Sequence (pFCS) The GFP Payload FCS is an optional, four-octet long, frame check sequence. It contains a CRC-32 sequence that protects the contents of the GFP Payload Information field. The FCS generation process is defined in G(x)=x32 + x26 + x26 + x23 + x22 + x16 + x12 + x11 + x10 + x8 + x7 + x5 + x4 + x2 + x1 + 1 where x32 corresponds to the MSB and x0 corresponds to the LSB.
2.3.1.1.2
Extension Header
The extension header is including the three types: Null extension, Linear and Ring.
Null Extension The mode is not support extension header. This is for the point to point application. Linear frame extension header It is for the linear application.Now dont support Ring frame extension header Now it is not support.
2.3.1.1.3
Frame-Mapped GFP (Payload-Dependent)
2.3.1.2 LAPS Function NOTE: GE board not supports LAPS function. LAPS describes an HDLC-like framing structure to encapsulate IEEE 802.3 Ethernet MAC frame as shown as below, provide a point-to-point full-duplex simultaneous bidirectional operation. The relationship between LAPS and Ethernet and SDH physical layer is shown as below:
2.3.1.2.1
Frame Format
LAPS link entity accepts frames from the MAC layer through the reconciliation sublayer and an equivalent MII (Media Independent Interface). No address filtering function is used here. The format of LAPS information field is defined in the shaded region of Figure 6. Figure 7 presents the format of LAPS frame after encapsulating MAC field. The order of those octets and bits (shaded area as shown in Figure 7) is kept intact. The FCS computations of LAPS and MAC refer to ITU-T X.85/Y.1321 and IEEE 802.3 standard respectively. The function unit of Ethernet over LAPS forwards all incoming LAPS information field to its peer connected link except the originating link port, and is permitted to buffer one or more incoming frames before forwarding them. Figure 8 shows the relationship between the reconciliation sublayer/MII and LAPS/SDH.
2.3.1.2.2
Rate adaptation
If the Rate Adaptation is needed in the LAPS transmit processing, transmit entity adds the rate-adaptation octet(s) "0xdd" within the frame by sending sequence(s) of {0x7d, 0xdd}. This function is performed just after transparency processing and before the end flag is added. In receive direction, receive entity will remove the Rate Adaptation octet(s) "0xdd" within the LAPS frame when detecting sequence(s) of {0x7d, 0xdd}. This function will be done just before transparency processing and after the end flag is detected.
NOTE: The difference between LAPS and GFP-F are shown as bellow: Item frame delineation LAPS Use special octet7E for LAPS frame delineation, the starting octet and ending octet of the LAPS frame is 7E x43 + 1 CRC-32 0x7e -> 0x7d, 0x5e;0x7d -> 0x7d, 0x5d; Fill octet 7E Point to Point The utilization ratio of the bandwidth would be decreased if the Ethernet data include 0x7e or 0x7d,the available bandwidth would be half especially if the Ethernet data is all 0x7e or 0x7d. Narrow application, only very few users are using. The internetworking of the equipments may have problems because the equipment manufacturers haven't passed the internetworking test. GFP-F GFP frame delineation is performed based on the correlation between the first two octets of the GFP frame and the embedded two-octet cHEC field. x43 + 1 CRC-32 selected by CID Normal GFP idle Frame Point to Point, Linear,Ring The utilization ratio of the bandwidth doesn't connect with the Ethernet data; it would not be decreased because some special data is transmitted.
scrambling /descrambling FCS Payload Process Inter-Frame-Gap Protocol coverage
Bandwidth
Compatibility
Widely applied over the world. GFP is recommended when the internetworking of the equipments is required, if the equipment manufacturers have passed the internetworking test strictly.
In NE management dialog Box, Select LAN-Interface Encapsulation And LCAS Configuration, the popup window Figure 2-52. is CIDs Encapsulation And LCAS Configuration function interface. Its used to set Encapsulation and LCAS configuration function.
F5259_A05B05 FUNCTIONAL DESCRIPTION
Figure 2-52 Encapsulation Configuration and LCAS Function Interface
2.3.2 LCAS
LCAS(Link capacity adjustment scheme) provides a control mechanism to hitless increase or decrease the capacity of a VCG(Virtual Concatenation Group) link in SDH network. It will automatically decrease the capacity if a member experiences a failure in the network, and increase the capacity when the failure is repaired. The LCAS assumes that the capacity initiation, increase or decrease of is carried out by Network and Element Management Systems. The scheme is applicable to every member of the Virtual Concatenation group. LCAS defines the member status and control information, which exchanged between the source and sink side to enable the flexible resizing capacity of a VCG link. The member status and control information are carried by the multiframe of the path overhead byte H4 (in VC3/VC4 virtual concatenation case) or K4 (in VC12 virtual concatenation case). The multiframe of H4 or K4 are shown as below:
* * Bit 5 Bit 6 Bit 7 Bit 8 1 multi- 2 multiframe frame 1*multiframe indicator no. no. MF11 LS nibble (bit 1-4) MS nibble 0 1 1 1 7 CRC-8 1 0 0 0 8 Member status MST 1 0 0 1 9 Member status MST 0 0 0 RS Ack 1 0 1 0 10 n 1 0 1 1 11 Reserved ("0000") 1 1 0 0 12 Reserved ("0000") 1 1 0 1 13 Reserved ("0000") Sequence indicator SQ MSBs (bits 1-4) 1 1 1 0 14 Sequence indicator SQ MSBs (bits 5-8) 1 1 1 1 15 ** 0 0 0 0 0 2 multiframe indicator MF12 MSB (bits 1-4) ** 0 0 0 1 1 2 multiframe indicator MF12 MSB (bits 5-8) CTRL 0 0 1 0 2 0 0 0 GID 0 0 1 1 3 Reserved ("0000") 0 1 0 0 4 n+ Reserved ("0000") 0 1 0 1 5 CRC-8 0 1 1 0 6 CRC-8 0 1 1 1 7 Member status MST 1 0 0 0 8
H4 byte
Bit 1
Bit 2
Bit 3
Bit 4
Figure 2-53 VC3/VC4 H4 Multiframe Structure
Figure 2-54
VC12 K4 Multiframe Structure
LCAS Signaling In addition to the Multiframe Indicator (MFI) and Sequence Indicator used for virtual concatenation, LCAS adds the following fields. Refer to Figure 2-53 and Figure 2-54. a) Member status (MST) b) Re-sequence Acknowledge (RS-Ack) c) Control (CTRL) d) Group Identification (GID) These fields (along with the MFI and Sequence Indicator) are sent in messages which are protected by a CRC. This allows validation of the received LCAS/VC overhead within a single control message instead of using a multiframe validation. Any control messages for which the CRC indicates errors are discarded MST Member status for each member path of a VCG is transmitted on all members of a VCG simultaneously. This information is sent on each member path in 32 consecutive control messages. Current member status is continuously updated from control messages received on all healthy member paths. RS-Ack RS-Ack is toggled to acknowledge a request for a change to member status which involves re-ordering/ changing of Sequence Indicators. These requests are for adding or removing member paths to a VCG. They are transmitted on all members of a VCG every control frame. RS-Ack is updated from all received member paths. GID The GID is a group id field which contains a serialized polynomial which is used to verify that all received member paths of a VCG originate at the same transmitter. This is transmitted in all member paths every control message and compared for all received member paths every 512 ms. Any detected discrepancies are alarmed.
LCAS Command a) Addition of member(s) When a member is added it shall always be assigned a sequence number greater than the currently highest sequence number that has EOS in the CTRL code. Following an ADD command the first member to respond with MST OK shall be allocated the next highest sequence number and shall change its CTRL code to EOS coinciding with the currently highest member changing its CTRL code to NORM. NOTE: When the CTRL=ADD is sent to initiate the addition of a new member, it shall be sent continuously until the MST=OK is received. Example: Add two members after last one in the group of n.
Figure 2-55 Add two members after last one Figure 2-55 above shows an example of adding two members after the current last member. The example shows new member (n) responding with MST OK before new member (n 1). This is arbitrary and the first member to respond with MST OK shall be allocated the SQ n, then the next new member to respond with MST OK shall be allocated SQ n 1 etc. If for any reason a member being added does not respond with MST OK within the time-out period then the LCASC shall report a fail for that member.
b) Deletion of member(s) When members are deleted, the sequence numbers and corresponding member status number of the other members shall be renumbered. If the deleted member contains the highest sequence number of that group, the member containing the next highest sequence number shall change its control word to EOS in its control packet coinciding with the deleted member s control packet with the IDLE control word. If the member deletion occurs somewhere other than at the highest end of the sequence, then the other members with sequence numbers between the newly deleted member and the highest sequence number shall update their sequence indicators in their control packets coinciding with the control packet changing the status of the deleted member. Example: Remove members 4 and 5 from a VCG with n 6 members.
Figure 2-56 Remove two members in a VCG
The example above shows two members being removed with a simultaneous IDLE command from the LCASC (Source). Reassembly at the sink ceases to use the removed members immediately upon receipt of the IDLE command. The response, however, from the Sink may not be simultaneous. This does not affect the Sink since the IDLE commands will have the same Frame No. The response from the Sink to the Source is, of course, simply acknowledgement that the member is no longer in use at the sink end and the NMS may proceed with de-provisioning of that member, if desired.
LCAS to non-LCAS interworking a) LCAS transmitter and non-LCAS receiver An LCAS transmitter can inter-work with a non-LCAS receiver in non-LCAS mode without any special consideration. The LCAS transmitter will place the MFI and SQ as designated in ITU-T Recs. G.707 [1] and G.709 [2]. The receiver will ignore all other bits, i.e. the LCAS overhead information. The member status returned from sink to source will always be MST = OK. b) Non-LCAS transmitter and LCAS receiver An LCAS receiver expects a CTRL word that is not 0000 and a correct CRC. A non-LCAS transmitter will transmit 0000 in the LCAS CTRL field as well as the CRC field. Therefore when an LCAS receiver is interworking with a non-LCAS transmitter and receives both CTRL word AND CRC equal to 0000, it shall: Ignore all information (except MFI and SQ); Use MFI and SQ defect detection as defined for virtual concatenation.
2.4 Cross connection

Virtual Concatenation is for the several VC-N payload communications together (VC-N-Xv).
2.4.1 Matrix structure

Table 2-1. Cross-connect level
VC-4 VC-3 VC-12 152*152 96*96 2016*2016
Matrix Structure Size
2.4.2 Cross-connect level

In condition of SDH, the equipment can support VC12 /VC3 /VC4 cross-connect level. Table 2-2 shows the relationship between interface unit and cross-connect level. Table 2-2. Cross-connect Level for Each Interface Cross-connect level
VC-4 / 3 / 12 VC-4 / 3 / 12 VC-4 / 3 / 12 VC-3 VC-12 VC-12m/3n/4k VC-3n/4k (FE WAN) VC-3i/4j (GE WAN)
Interface Unit
STM-16 STM-1/4 S1E_2 E31/E32 E12A/E12B FE_4 GE_A
NOTE: m=1-63, n=1-3, k=1, i=1~21, j=1~7
2.4.3 Cross-connect type

V-Node supports the following cross-connect type: 1 way 2 way Broadcast Drop & Continue 2.4.3.1 One way Add
Aggregate
Tributary
Limitation: a) Connection between aggregate side and tributary side has no limitation b) One action can set the connection from CID c) Connection limitation: Table 2-3. Connection between aggregate and tributary
Tributary SDH Aggregate No SLA SLA West East West (W) West (P) East (W) East (P) O O O O O O PDH O O O O O O
NOTE:O: Connection is available.
Drop
Aggregate
Tributary
Limitation: a) Connection between aggregate and tributary side has no limitation. b) One action can set the connection from CID. c) Connection limitation is specified according to Table 2-3. Through
Aggregate Input Output
Tributary
Limitation: a) When system mode is set as 2F/ Ms-Spring, connection between west and east is on the same timeslot. b) One action can set the connection from CID. c) Connection limitation:
Table 2-4.
Connection limitation between aggregate and tributary

Output No SLA West East West (W) O O O SLA West (P) East (W) O O O East (P) -
Input
No SLA SLA
West East West (W) West (P) East (W) East (P)
O O -
O O -
O: Available -: Unavailable Loop back
Aggregate Input Output
Tributary
Limitation: a) Dont support Loop back action between working and protection side of SLA path; b) Dont support Loop back action when system works at 2F MS-Spring mode; c) One action can set it from CID. Table 2-5. Connection limitation between aggregate and tributary
Output No SLA W O SLA W O X P X O
Input
No SLA SLA
W W P
O: Available at the same timeslot X: Dont support -: Not exist
Hairpin
Aggregate
Input Tributary
Limitation:
Output
a) Connection is available between any two tributary b) One action can set it from CID Path selector
Input1
PS
Input2
Output
Table 2-6.
1 way Path selector

Input2 No SLA W W O SLA P -
Input1
No SLA SLA
W W P
O -
O: Available -: Unavailable
Service selector
Output
SS
Input1
Input2
Table 2-7. 1 way Service selector
Output No SLA W Input1 No SLA SLA W W P O W O O SLA P -
O: Available -: Unavailable
2.4.3.2 Two way Add/Drop
Aggregate
Tributary
Limitation: Same as 1 way Add/Drop.
Through
Aggregate
Tributary
Limitation: Same as 1 way through Loop back
Aggregate
Tributary
Limitation: Same as 1 way Loop back, but cannot Loop back at the same timeslot. Hairpin
Aggregate
Tributary
Limitation: Same as 1 way hairpin, but it is unavailable at the same SDH timeslot or PDH channel.
Path selector
Input1
PS
Input2
Output
Limitation: Same as 1 way path selector. Service selector
Input3 Output Input2
SS
Input1
Limitation: Output of SS is the work channel of aggregate side. One action can set it from CID.
2.4.3.3 Broadcast This system doesnt support 1 way Loop back broadcast, 1 way Hairpin broadcast. 1 way Add Broadcast/Bridge
Broadcast Aggregate Bridge
Input Tributary
1 way Drop Broadcast
Aggregate
Tributary
1 way Path selector Broadcast
PS
PS
Output
1 way Service selector Broadcast
Output
SS
Limitation: Output of SS is the work channel of aggregate side. One action can set it from CID.
2.4.3.4 Drop & Continue 1 way Drop & Continue
Aggregate
Tributary
1 way Path selector Drop & Continue
PS
2.4.3.5 Mix carrier The equipment can carry mixed VC-3 and VC-12 signal in one VC-4.
A B
VC-4 VC-3
VC-3
VC-12
2.4.3.6 MSP+SNCP
STM-N MSP STM-N SNCP STM-N MSP PS
2.4.3.7 SNCP+Broadcast
(1) VC-4/3/12 PS (2) VC-4/3/12
PS (3) VC-4/3/12
2.4.3.8 CrossConnect for Multi-ring
Path 1 Path 2 PS
Path 3 Path 4
Path 1 Path 2 PS
Path 3 Path 4
2.5 Protection
V-Node supports five kinds of protections: MSP (multiplex section protection), MS-SPRing (multiplex section shared protection ring), SNCP (sub-network connection protection), hardware protection and Overhead protection.
2.5.1 MSP
2.5.1.1 Action mode V-Node supports MSPs working mode: 1+1 Uni-directional Non-revertive, 1+1 Bi-directional Non-revertive, 1:1 Bi-directional Revertive Linear Protection. The following illustration shows the three kinds Linear Protection. Only receive side is switched in case of the line failure.
Figure 2-57 1+1 Unidirectional Linear Protection Operation
Figure 2-58 1+1 Bidirectional Linear Protection Operation
Figure 2-59 1:1 Bidirectional Linear Protection Operation
2.5.1.2 Configuration mode The boards in same level can be configured as protection in V-Node, for example, the following figure shows the protection among the STM-1, among STM-4, among STM-16 without slot limitation.
STM-4/16
E12_INF E12_INF P_INF D_INF P_INF W
V-Node V-Node
P CS CS STM-4/16 STM-4/16
2M( No TPS) 100Base-T
Figure 2-60 MSP Configuration
FE MCP
E12 E12
2.5.1.3 Switching criterion Switching requirement

SF SD SF SF SF SF
Item
B2ERR_HIGH B2ERR_LOW LOS LOF MS-AIS RS-TIM*
Monitor place
Line (Work / Prot) Line (Work / Prot) Line (Work / Prot) Line (Work / Prot) Line (Work / Prot) Line (Work / Prot)
*: J Byte must be enabled in order to make TIM function be a switch criterion.
2.5.1.4 External commands Command

Lockout of protection Lockout of working Forced switch to protection Forced switch to working Manual switch to protection Manual switch to working
Term
LKOP LKOW FSP FSW MSP MSW
Content
Protection line is forbidden to use unconditionally. Working line is forbidden to use unconditionally. If the command is set on working line, the traffic will be switched to protection line unconditionally. If the command is set on protection line, the traffic will be switched to working line unconditionally. If the command is set on working line and protection line is in normal status, the traffic will be switched to protection line. If the command is set on protection line and working liner is in normal status, the traffic will be switched to the working line.
2.5.1.5 Command priority 1+1 Uni: LKOP > FS > SF > SD >MS 1+1 Bi: 1:1 Bi: LKOP>SF on Prot>FS>SF on Work>SD on Prot>SD on Work > MS LKOP>SF on Prot>FSW(to W)>FSW(to P)>SF on Work>SD on Prot > SD on Work >MSW (to W) > SW (to P) 2.5.1.6 Switch time Switch time is the interval from the decision to switch to the completion of the switch and switch operation at a switching node initiating the switch request. When Hold Off time is set as 0sec, switch time must be less 50msec.
2.5.2 MS-SP Ring

2.5.2.1 Action mode This section is referring to ITU-T G.783/G.841 MS-SPRING protection is for the STM-4/ STM-16 optical interface.
OPTICAL INTERFACE MODE
2 Fiber MS-SP Ring 2 Fiber MS-SP Ring
SPECIFICATION
ITU-T G.841 ITU-T G.841
STM-16 STM-4
In addition, the mode (Transoceanic Application) of operation based on ITU-T G.841 Annex A decides not to support for the time being. 2.5.2.2 Configuration mode The boards in same level can be configured as protection in V-Node, for example, the following figure shows the protection among the STM-4, and among the STM-16 without slot limitation.
V-Node
STM-16 MS-Spring
V-Node
V-Node
TPS_E12P TPS_E12W TPS_E12W TPS_E12W TPS_E12W
D_INF
P_INF
P_INF
V-Node
CS CS STM-4/16 STM-4/16
FE MCP
E12 E12 E12 E12 E12
2M(With TPS) 100Base-T
Figure 2-61 MS-SP Ring Configuration
2.5.2.3 Switching criterion Table 2-8. Item

B2EXC B2DEG LOS LOF MS-AIS J0-TIM
Switching Factor Monitor place

Line (Work / Prot) Line (Work / Prot) Line (Work / Prot) Line (Work / Prot) Line (Work / Prot) Line (Work / Prot)
Switching requirement
SF SD SF SF SF SF
Table 2-9. Item

EQPT FAIL
Optical Interface Factor Monitor place

Package (Work / Prot) Package (Work / Prot) Package (Work / Prot)
SF SF SF
PKG-REMOVE PKG-TYPE
2.5.2.4 External commands Command

Lockout of protection
Term
LKOP
Content This command prevents using ring switches anywhere in the ring. If any ring switches exist in the ring, this command causes the switches to drop. Thus, all ring switching is prevented (and pre-empted). It used for whole subnet. This command performs the ring switch of normal traffic from working channels to the protection channels for the span between the node at which the command is initiated and the adjacent node to which the command is destined. It used for one port of the specifically node. This command performs the ring switch of the normal traffic from the working channels to the protection channels for the span between the node at which the command is initiated and the adjacent node to which the command is destined. It used for one port of the specifically node. This command exercises ring protection switching of the requested channel without completing the actual bridge and switch. It used for one port of the specifically node.
Forced Switch Ring
FSR
Manual Switch Ring
MSR
Exercise Ring
EXR
2.5.2.5 Command priority LKOP>FS-S>FS-R>SF-S>SF-R>SD-P>SD-S>SD-R>MS-S>MS-R>WTR>EXER-S >EXER-R>RR-S>RR-R>NR 2.5.2.6 Switch time Switch time is the interval from the decision to switch to the completion of the switch and switch operation at a switching node initiating the switch request. When Hold Off time is set as 0sec, switch time must be less 50msec.
2.5.3 SNCP
2.5.3.1 Action mode V-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: V-Node supports both SNC/N and SNC/I in SNCP ring configuration.
2.5.3.2 Configuration mode The boards in same level can be configured as protection in V-Node, for example, the following figure shows the protection among the STM-1, among STM-4, among STM-16 without slot limitation
Figure 2-62 2.5.3.3 Witching criterion For SNC/N Item

AU-LOP AU-AIS HOP
SNCP Configuration
SSF (Server Signal Fail) SSF (Server Signal Fail) TSF (Trail Signal Fail) TSF (Trail Signal Fail) TSF (Trail Signal Fail) TSD (Trail Signal Degrade) SSF (Server Signal Fail) SSF (Server Signal Fail) TSF (Trail Signal Fail) TSF (Trail Signal Fail) TSD (Trail Signal Degrade) TSF (Trail Signal Fail)
HP-UNEQ HP-TIM HP-EXC HP-DEG TU-LOP TU-AIS
LOP
LP-UNEQ LP-EXC LP-DEG LOM
NOTE: LOM is only for VC-12 but not for VC-3. For SNC/I Item
HOP AU-LOP AU-AIS TU-LOP TU-AIS
SSF (Server Signal Fail) SSF (Server Signal Fail) SSF (Server Signal Fail) SSF (Server Signal Fail)
LOP
2.5.3.4 External commands Command Term

Lockout of protection Forced switch Manual switch LKOP FSP MSP
Content
If the command is set, the protection channel will be forbidden to use unconditionally. If the command is set, the traffic will be switched to protection channel unconditionally. If the command is set and protection channel is in normal status, the traffic will be switched to protection channel.
Revertive

Nonrevertive

2.5.3.5 Command priority LKOP> FSP> SF on Prot>SF on Work> SD on Prot> SD on Work> MSP> Wait-to-restore> No request 2.5.3.6 Command value Wait for restore time: 0min ~12min, step=1 min Hold-off time: 0ms ~ 10 sec, step=50ms
2.5.4 Hardware Protection

2.5.4.1 TPS TPS carries out 2M electronic interface protection with 1:4 mode, The five slots located in the most left and most right can be installed with TPS board. TPSs working principle shows as figure below:
Normal Working Mode
Switch Working Mode TPS system is made of standby interface board, working interface board and TPS switch board. When system is normal, both the standby interface board and working board can transmitting service separately without interference. And the service transmitted by standby interface board is called ALS service. When one of the working boards fails, system send the commands about both time slot cross connection switch and TPS board switch. In one hand, the system let the CS board switch the timeslot and replace the failed boards bus time slot with the standby interface boards bus time slot; in other hand, control the TPS board physical interface switch, switch the input single of the failed electronic interface
board to standby board. By these two steps, the service can be transmitted when the board is fail; and the TPS function with 1: N is carried out. The above figure only indicates the principle of the transmitting direction; it is the same as the receiving direction. The switches on the switch board can be made of the relays, which is controlled and switched by CS board. 2.5.4.1.1 Item
EQPT FAIL CPU FAIL PKG_REMOVED
Switching criterion Switching requirement

SF SF SF
Monitor place
2.5.4.1.2 Command
Lockout of protection Forced switch to protection Manual switch to protection Clear
External commands Term

LKOP FSP MSP CLR
Content
Protection line is forbidden to use unconditionally. If the command is set on working line, the traffic will be switched to protection line unconditionally. If the command is set on working line and protection line is in normal status, the traffic will be switched to protection line. It is a command for canceling the following command according to the starting demand from NE outside: LKOP,FSP,FSW,MSP,MSW Moreover, in addition to the above, the WTR state is canceled when mode of operation is revertive.
2.5.4.2 CS Board Protection In V-Node, there are 2 CS boards in 8# and 9#, they detect their own status and transfers it to each other. the 8# CS board analyze its own status and the 9# CS boards status and decide which board should be in work-status and which should be in protect-status and control the switch process, the 9# CS board accept the 8# CS boards signal and control its status. The CS board reports their status and the cause of the switch. 2.5.4.2.1 Item
EQPT FAIL CPU FAIL PKG_REMOVED
Switching criterion Switching requirement

SF SF SF
Monitor place
2.5.4.2.2 Command
Forced switch to protection Forced switch to working Manual switch to protection Manual switch to working Clear
External commands Term

FSP FSW MSP MSW CLR
Content
If the command is set on 8#, the traffic will be switched to 9# unconditionally. If the command is set on 9#, the traffic will be switched to 8# unconditionally. If the command is set on working line and 8# is in normal status, the traffic will be switched to 9#. If the command is set on 9# and working package is in normal status, the traffic will be switched to the 8# It is a command for canceling the following command according to the starting demand from NE outside: LKOP,FSP,FSW,MSP,MSW Moreover, in addition to the above, the WTR state is canceled when mode of operation is revertive.
2.5.5 Overhead protection

DCC channel V-Node equipment can carry out DCC protection. The principle is show as below figure:
Figure 63.
DCC Protection
In normal status, IP1 is used. And in protection status IP2 is used. When configuring the linear MSP, you should set the port of both working side and protection side at the same time. The detail demand is: 1. 2. 3. Working and protection line should be set with different IP address. The value of link and physical layer of these two lines should be set as same. When linear MSP switching, the communication will base on the IP of protection line.
When configure the S1E TPS1+1, you only need to set the port of working package. The detail demand is: When the TPS switch occurring, the communication will still base on the IP of working line.
Orderwire (E1/E2) Orderwire protection and TPS 1+1 protection function are supported by V-Node equipment. And these two functions are classified as unidirectional protection and bidirectional protection respectively. For unidirectional protection, if the faults only detected in unidirectional, the switching function wont execute. The protection principle is shown as below:
Figure 64.
The Unidirectional Protection
For bidirectional protection, if the alarms detected in any direction, the switch function will execute. The bidirectional protection principle is shown as below:
Figure 65.
The Bidirectional Protection
When configuring the linear MSP, you should set the port of both working side and protection side at the same time. The detail demand is: 1. 2. 3. Working and protection line should be set with same OW byte (E1 or E2). Only working line can be set with "open" for OW channel. Protection line should be set with "close". Else NE will cut off OW channel automatically. When MSP switching occurring, the settings of working line will be set to the protection line.
When configure the S1E TPS1+1, you only need to set the port of working package. The detail demand is: 1. When TPS switch occurring, the port settings of the working package will be set to the port of protection package. User Data Channel (E2/F1) In normal status, you should select working line by switch. And in protection status, if there are some alarms occurring in receive direction, the switch function will execute.
Figure 66.
User Data Channel Protection
When configuring the linear MSP, you only need to set the port of working package. The detail demand is: 1. When MSP switching occurring, the setting of protection line will be set to the working line.
When configure the S1E TPS1+1, you only need to set the port of working package. The detail demand is: 1. When TPS switch occurring, the port settings of the working package will be set to the port of protection package.
2.6 Synchronization
2.6.1 Timing source
Internal Free run: +4.6ppm~-4.6ppm Internal Holdover: +0.37ppm~-0.37ppm / 1 day STM-N Line (any port): 2Mbps PDH Line (only #1 channel port) External port: 2Mbps or 2MHz selectable (75ohms/120ohms) 1 port: standard Another port: enhanced by Fan unit option (only 2MHZ)
Pull-in Lock in range: 9.2 ppm
2.6.2 Timing source control

2.6.2.1 Quality Level Timing source is selected by following Quality Level of S1 byte specified in ITU-T Standards. Also, the selection without specifying QL value is available. Four methods of Quality Level setting are applicable: Quality Level conveyed from SSM Support or not support SSM Forced QL Setting Timing Source Failure 2.6.2.2 Priority Level Setting The priority level can be specified to all timing sources. Priority level for each timing source must be unique. 2.6.2.3 SSM Control The following interfaces support SSM as timing source control: STM-N aggregate STM-N Tributary External 2Mbps interface
The definition of S1 byte and San bit is shown in below table. S1/San Byte Signal
Bits (5 thru 8) in S1/San Byte Timing Source Quality and Grade
0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111
Quality unknown Reserved G.811 Reserved G.812 Transit Reserved Reserved Reserved G.812 Local Reserved Reserved G.813 (SETS) Reserved Reserved Reserved Do not use for timing source
SETS: Synchronous Equipment Timing Source S1/San byte signal selection order:
G.811> Quality unknown> G.812 Transit> G.812 Local> G.813 (SETS)
In order to avoid timing loop, SSM control should conform below rules. 1) Selected timing source from STM-N
The selected time source is STM-N, so the self out SSM=DNU. And the other direction output SSM=selected timing source =G.811.
2)
Selecting timing source is External timing source which slave to NE External output timing source.
The QL of NE and extended clock is same levelG.811. 3) Selecting timing source is External timing source which is free running and dose not salve to NE External output timing source
2.6.3 Timing source selection

2.6.3.1 Switching criterion Lockout>FS> SF>MS Quality/SSM> Priority SF (STM-N): LOS, LOF, MS-AIS, AND RS-TIM SF (2Mbps tributary): LOS SF (2Mbps external): LOS, LOF, AIS SF (2MHz external): LOS
NOTE: Users can operate priority setting whether quality level selection mode is used or not.
2.6.3.2 System/Bypass System clock source is the clock source for the whole equipment to synchronize after system PLL processing. Bypass clock source is the clock source for 2M EXTCLK module to output clock signal without system PLL processing. 2.6.3.3 Hold-off Time Hold-off Time is the duration to hold executing the timing source switch, in order to determine whether a signal failure is the momentary status or not. Hold-off Time: 0~1800ms, step=300ms 2.6.3.4 Wait-to-Restore Time Wait-to-Restore Time is the duration to hold executing the timing source switch, in order to determine whether the recovery is the momentary status or not. Wait-to-Restore Time: 0~12min, step=60s 2.6.3.5 Revertive /non revertive Fixed to be Revertive. 2.6.3.6 Report to NMS items All timing source's status (QL, failure), Selected Timing Source and its QL can report to NMS. 2.6.3.7 2M BPS frame format G.704 7/95 With CRC/without CRC selectable TS1~TS31= all 1 TS 0 =frame word 2.6.3.8 Squelch When Quality level of working timing source is lower than user setting Quality level threshold, namely Squelch value, 2M bps EXTCLK output is squelched and AIS alarm occurs in far-end equipment and 2MHz EXTCLK output is squelched and LOS alarm occurs in far-end equipment.
2.6.4 DNU Group

When connect several optical ports between two equipments, it maybe bring abnormal phenomena: the clock source locked each other as a ring or the oscillator switching. For avoiding these phenomena, when the origin of the several known time sources is the same, you can configure the DNU GROUP ID of these time sources as the same (non-zero). When the time source module use one of these time sources, the other time source port with the same DNU GROUP ID send the DNU synchronously. 1. No configuration of the DNU_GROUP_ID
Figure 2-67.
No Configuration of the DNU_GROUP_ID
According to the above configuration, when the SSU is failed, the NE01s time source would be switched from PORT2, and locked by the NE02s clock source as a ring. 2. Configuration of the DNU_GROUP_ID
Figure 2-68. Configuration of the DNU_GROUP_ID According to the above configuration, when the SSU is failed, the NE01s time source will not be switched from the PORT2, thereby, the clock ring is avoided.
2.7 Trace/signal label function

Trace label function is used for receiving end to confirm that it is connected the designated transmission end. V-Node uses SOH byte: J0 and POH bytes: J1 and J2 to fulfill this function. J byte has 16 bits. The first bit is used for verifying, so user can only configure 15 byte in CID window. For J byte, available character is listed below table. Available Character of J byte
SP ! # $ % & ( ) * + , . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~
NOTE: 1) 2) SP means: space bit. (null): When there is no input value, the system will auto insert (null).
Setting value: The sended value of J byte. Default value is null. Expected value: The received value which are expected. Default value is none. Signal label function is used to indicate such information as path status, traffic type. V-Node uses path overhead bytes: C2 and V5 to fulfill this function. The C2 and V5 Byte Codes are shown as below:
C2:
S/A send Value 0x00 0x01 0x02 0x03 0x04 0x05 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1a 0x1b 0xcf 0xe1-0xfc 0xfe 0xff others CID monitor value UNEQUIPPED RESERVED TUG_STRUCTURE LOCKED_TU ASYNC_V3 UNDER_DEVELOP ASYNC_V4 ATM DQDB FDDI HDLC/PPP SDL_SSS HDLC/LAPS SDL_SRS 10GBE FTDL RESERVED RESERVED_NU TS_O181(VC4) VC_AIS(VC4) UNKNOWN
V5:
S/A send Value 0b000 0b001 0b010 0b011 0b100 0b101 0b110 0b111 CID monitor value UNEQUIPPED RESERVED ASYNC BIT_SYNC BYTE_SYNC EXTENDED_SIGNAL_LABEL TS_O181 VC_AIS
NOTE: If enable the J byte, the AIS will be insert when J byte mismatch.
2.8 Configuration Management

Configuration management includes port registration setup, working parameter setup for NE, configuration of board required for NE operation, effective timing source setup, equipment and resource control and traffic management. NE equipment management is mainly to configure attributes for NE and boards. Attributes for NE equipment are equipment types, NE interface, protection switching group, NE timing source setting, etc. Traffic management includes the management of transmission, end users and cross connection. Configuration management also provides the management of network topology, which can control and communicate the topology objects within the network management area. Below table shows the package installation limitation in release 3.10
Y: Can be equipped. NOTE: 1) The slot 24 and 25 is not used. 2) TPS_S1E, TPS_E3 packages occupy 2 slots 3) The TPS_E1W/TPS_E1P/THR_E12W board can't be inserted in the up row slot without the E1 board in the down row slot.
2.9 Performance monitor

2.9.1 The Definition of PM item
SDH PM (1of2)
monitor types RST BBE ES SES OFS UAS MST BBE ES SES UAS MST (Far End) FEBBE FEES FESES FEUAS HPT BBE ES SES UAS HPT(Far End) FEBBE FEES FESES FEUAS LPT BBE ES SES UAS LPT(Far End) FEBBE FEES FESES FEUAS Definition Near end background block error Near end errored seconds Near end severely errored seconds Out of frame seconds Unavailable seconds Near end background block error Near end errored seconds Near end severely errored seconds Unavailable seconds Far end background block error Far end errored seconds Far end severely errored seconds Far end unavailable seconds Near end background block error Near end errored seconds Near end severely errored seconds Unavailable seconds Far end background block error Far end errored seconds Far end severely errored seconds Far end unavailable seconds Near end background block error Near end errored seconds Near end severely errored seconds Unavailable seconds Far end background block error Far end errored seconds Far end severely errored seconds Far end unavailable seconds Spec. ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784 ITU-T G.826 G.784
(2of2)
monitor types MSA HPA PJE-P (see NOTE) PJE-N (see NOTE) PJE-P (see NOTE) PJE-N (see NOTE) PSC PSC PSD Definition Pointer justification event Pointer justification event Pointer justification event Pointer justification event Protection switching counts (Only for 1+1 APS) Protection switching duration (Only for 1+1 APS) Spec. ITU-T G.783,G.784 ITU-T G.783,G.784 ITU-T G.783,G.784 ITU-T G.783,G.784 ITU-T G.783 ITU-T G.783
MSP
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
Ethernet PM
(1 of 5) MONITOR TYPES ETH-DropPkt ETH-RxAlignm entErrorFrame ETH-RxBroadc astPkt ETH-RxFCSEr rorFrame ETH-RxMultica stPkt ETH-RxOctet ETH-RxPause Frame LAN ETH-RxPkt DEFINITION A count of drop packets. 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 Number of good broadcast packets received 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. Number of good multicast packets received(excluding broadcast packets) The total number of octets received on the interface, including framing characters. Number of pause frames received Number of packets received (including bad packets, all Unicast, Broadcast packets, and Multicast packets) Number of packets received that were between 1024 and the Mac_Pkt_Len octets in length (including error packets) Number of packets received that were between 128 to 255 octets in length (including error packets) Number of packets received that were between 256 to 511 octets in length (including error packets) Number of packets received that were between 512 to 1023 octets in length (including error packets) Number of packets received that were 64 octets in length (including bad packets) Number of packets received that were between 65 to 127 octets in length (including error packets) SPEC. RFC1643
RFC1643
RFC1213
RFC2665 RFC1757
ETH-RxPkt102 4toMax ETH-RxPkt128 to255 ETH-RxPkt256 to511 ETH-RxPkt512 to1023 ETH-RxPkt64 ETH-RxPkt65t o127
(2 of 5) MONITOR TYPES ETH_RxUnder sizePkt ETH_RxOversi zePkt ETH-TxBroadc astPkt ETH-TxCollisio nFrame ETH-TxDelayT ransmission DEFINITION Number of packets received that were less than 64 octets long and were otherwise well formed A count of frames received on a particular interface that exceeds1518 bytes. (see NOTE) The total number packets that higher-level protocols requested to be transmitted to a broadcast address. Number of collisions on this Ethernet segment A count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. A count of frames for which transmission on a particular interface fails due to excessive collisions. The number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet. A count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision. 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. The total number packets that higher-level protocols requested to be transmitted to a multicast address. The total number of octets transmitted out of the interface, including framing characters. SPEC. RFC1757
RFC1757
RFC1643
ETH-TxExtColli sionFrame LAN ETH-TxLateCo llisionFrame
RFC1643
RFC1643
RFC1643
ETH-TxMultiCo llisionFrame
RFC1213
ETH-TxNUcast Pkt
ETH-TxMultica stPkt
RFC1213
ETH-TxOctet
(3 of 5) MONITOR TYPES ETH-TxPause Frame ETH-TxPkt ETH-TxSingle CollisionFrame DEFINITION Number of pause frames transmited The total number of packets transmited. A count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision. The total number of packets that higher level protocols requested be transmitted to a subnetwork. Number of packets transmitted and received that were byte in length (including bad packets) Number of packets transmitted and received that were between 65 to 127 octets in length (including error packets) Number of packets transmitted and received that were between 128 to 255 octets in length (including error packets) Number of packets transmitted and received that were between 256 to 511 octets in length (including error packets) Number of packets transmitted and received that were between 512 to 1023 octets in length (including error packets) Number of packets transmitted and received that were between 1024 to 1518 octets in length (including error packets) Number of packets transmitted and received that were between 1519 to 9216 octets in length (including error packets) A count of drop packets. 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 Number of good broadcast packets received SPEC. RFC2665 RFC1643
ETH-TxUcastP kt
RFC1213
ETH-TR64
LAN
ETH-TR65to12 7 ETH-TR128to2 55 ETH-TR256to5 11 ETH-TR512to1 023 ETH-TR1024to 1518 ETH-TRJumbo Pkt ETH-DropPkt ETH-RxAlignm entErrorFrame ETH-RxBroadc astPkt
RFC1643
WAN
(4 of 5) MONITOR TYPES ETH-RxFCSEr rorFrame ETH-RxMultica stPkt ETH-RxOctet DEFINITION 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. Number of good multicast packets received(excluding broadcast packets) The total number of octets received on the interface, including framing characters. A count of frames received on a particular interface that exceeds1518 bytes. (see NOTE) Number of pause frames received Number of packets received (including bad packets, all Unicast, Broadcast packets, and Multicast packets) Number of packets received that were 64 octets in length (including bad packets) Number of packets received that were between 65 to 127 octets in length (including error packets) Number of packets received that were between 128 to 255 octets in length (including error packets) Number of packets received that were between 256 to 511 octets in length (including error packets) Number of packets received that were between 512 to 1023 octets in length (including error packets) Number of packets received that were between 1024 and the Mac_Pkt_Len octets in length (including error packets) Number of packets received that were less than 64 octets long and were otherwise well formed The total number packets that higher-level protocols requested to be transmitted to a broadcast address. RFC2665 RFC1757 SPEC. RFC1643
RFC1213
ETH-RxOverSi zePkt ETH-RxPause Frame ETH-RxPkt
RFC2577
ETH-RxPkt64 WAN ETH-RxPkt65t o127 ETH-RxPkt128 to255 ETH-RxPkt256 to511 ETH-RxPkt512 to1023 ETH-RxPkt102 4toMax ETH-RxUnder SizePkt ETH-TxBroadc astPkt
(5 of 5) MONITOR TYPES ETH-TR64 DEFINITION Number of packets transmitted and received that were byte in length (including bad packets) Number of packets transmitted and received that were between 65 to 127 octets in length (including error packets) Number of packets transmitted and received that were between 128 to 255 octets in length (including error packets) Number of packets transmitted and received that were between 256 to 511 octets in length (including error packets) Number of packets transmitted and received that were between 512 to 1023 octets in length (including error packets) Number of packets transmitted and received that were between 1024 to 1518 octets in length (including error packets) Number of packets transmitted and received that were between 1519 to 9216 octets in length (including error packets) 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. The total number packets that higher-level protocols requested to be transmitted to a multicast address. The total number of octets transmitted out of the interface, including framing characters. The total number of packets transmitted Number of pause frames transmitted The total number of packets that higher level protocols requested be transmitted to a subnetwork. SPEC.
ETH-TR65to12 7 ETH-TR128to2 55 ETH-TR256to5 11 ETH-TR512to1 023 ETH-TR1024to 1518 ETH-TRJumbo Pkt
WAN
RFC1213
ETH-TxNUcast Pkt
ETH-TxMultica stPkt
RFC1213
ETH-TxOctet ETH-TxPkt ETH-TxPause Frame ETH-TxUcastP kt
RFC2665 RFC1213
NOTE: For FE board, oversize means the count of frames received on a particular interface exceeds the specified length. However, for GE board, oversize means the count of frames received on a particular interface exceeds 1518 bytes.
Encapsulation PM
MONITOR TYPES DEFINITION SPEC.
GFP_RxEXIErro A count of received frame with rPkt HEAD errors. GFP_RxFCSErr orPkt GFP GFP_RxOctet GFP_RxPkt GFP_TxOctet GFP_TxPkt A count of received frame with FCS errors. A count of received octets. A count of received frame. A count of transmitted octets. A count of transmitted frame.
LAPS_RxFCSEr A count of received frame with rorPkt FCS errors. LAPS_RxOctet LAPS LAPS_RxPkt LAPS_TxOctet LAPS_TxPkt A count of received octets. A count of received frame. A count of transmitted octets. A count of transmitted frame.
2.9.2 Performance Counter Range

SDH PM Counter Range
PM TYPES 15m PM COUNTER RANGE MEMORY OFS BBE ES SES UAS FE-BBE FE-ES FE-SES FE-UAS PSC PSD PJE-P PJE-N 2 Byte 4 Byte 2 Byte 2 Byte 2 Byte 4 Byte 2 Byte 2 Byte 2 Byte 2 Byte 2 Byte 4 Byte 4 Byte RANGE 0-900 0-16777215 0-900 0-900 0-900 0-16777215 0-900 0-900 0-900 0-900 0-900 0-113184 0-113184 24h PM COUNTER RANGE MEMORY 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte RANGE 0-86400 0-1610612640 0-86400 0-86400 0-86400 0-1610612640 0-86400 0-86400 0-86400 0-86400 0-86400 0-10865664 0-10865664
Ethernet PM Counter Range

PM TYPES 15m PM COUNTER RANG MEMORY ETH-TxOctet ETH-RxOctet ETH-RxFCSErrorFrame ETH-RxAlignmentErrorFrame ETH-TxUcastPkt ETH-TxNUcastPkt ETH-RxMulticastPkt ETH-RxBroadcastPkt ETH-TxSingleCollisionFrame ETH-TxMultiCollisionFrame ETH-TxDelayTransmission ETH-TxExtCollisionFrame ETH-TxLateCollisionFrame ETH-TxCollisionFrame ETH-RxPkt64 ETH-RxPkt65to127 ETH-RxPkt128to255 ETH-RxPkt256to511 ETH-RxPkt512to1023 ETH-RxPkt1024toMax ETH-RxUnderSizePkt ETH-RxOverSizePkt ETH-DropPkt ETH-TR64 ETH-TR65to127 ETH-TR128to255 ETH-TR256to511 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte RANGE 0-4294967294 0-4294967294 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000 0-46875000 0-133929000 0-133929000 0-76014000 0-40760970 0-21146400 0-10775700 0-4294967294 0-7315200 0-133929000 0-265760848 0-265760848 0-152028000 0-81521940 24h PM COUNTER RANG MEMORY 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte RANGE 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294
PM TYPES
15m PM COUNTER RANG MEMORY RANGE 0-42292800 0-21551400 0-21551400 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000
24h PM COUNTER RANG MEMORY 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte RANGE 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294
ETH-TR512to1023 ETH-TR1024to1518 ETH-TRJumboPkt ETH-TxPauseFrame ETH-RxPauseFrame ETH-RxPkt ETH-TxPkt ETH-TxMulticastPkt ETH-TxBroadcastPkt
4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte
GFP PM Counter Range

PM TYPES 15m PM COUNTER RANG MEMORY GFP_TxPkt GFP_TxOctet GFP_RxPkt GFP_RxOctet GFP_RxFCSErrorPkt GFP_RxEXIErrorPkt 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte RANGE 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-133929000 0-133929000 24h PM COUNTER RANG MEMORY 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte RANGE 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294
LAPS PM Counter Range

PM TYPES 15m PM COUNTER RANG MEMORY LAPS_TxPkt LAPS_TxOctet LAPS_RxPkt LAPS_RxOctet LAPS_RxFCSErrorPkt 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte RANGE 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-133929000 24h PM COUNTER RANG MEMORY 4 Byte 4 Byte 4 Byte 4 Byte 4 Byte RANGE 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294
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.
2.9.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 are shown in below table. The Defects Causing Near End SES
PATH LAYER LO path layer NEAR END DEFECT CONDITION LP UNEQ LP TIM TU LOP TU AIS HP LOM HP PLM HO Path layer HP UNEQ HP TIM AU LOP AU AIS MST layer RST layer MS AIS RS TIM STM LOS STM LOF
The Defects Causing Far End SES

PATH LAYER LO path layer HO Path layer MST layer NEAR END DEFECT CONDITION LP RDI HP RDI MS RDI
SES PM threshold is shown in below table.

Facility VC12 VC3 VC4 RS MS SES Threshold Value 600 2400 2400 2400 2400
2.9.4 Invalid condition

Invalid condition means that PM does not correctly count. Time modified(>30s) All PM are unbelievable. Loopback(for the unit) Near end PM (Not include down stream PM) are unbelievable. Facility alarm occur Near end PM (Not include down stream PM) are unbelievable. Near end alarm Far end PM (Not include down stream PM) are unbelievable. F/W Reset All PM are unbelievable. H/W Reset All PM are unbelievable. NOTE: The detail information about invalid PM is shown as the attachment file: F5259_F05_Attachment_Invalid PM.
2.9.5 Register management

2.9.5.1 Type of register
Period
15min 1day
Current
1 1
History
maximum count is 32, more is deleted maximum count is 1, more is deleted
NOTE: Sometimes CID will not show performance value, but show over flow which means that the performance value exceeds its maximum counter value.
2.9.6 PM reset function

CID supports PM reset function. It restores PM count value to 0. For SDH and PDH interface, you can select any PM to reset it, and for Ethernet PM, all PM of the same port must be reset at the same time.
2.9.7 TCA
The equipment provide (or support) the Threshold Crossing Alert (TCA) function that issues an alert if the value of monitored PM type reaches or exceeds that of the specified threshold. The values are accumulated for every 15 minutes at 00, 15, 30, and 45 minutes of each hour (15Min) or for every 24-hour at 0:00 am (1Day). 2.9.7.1 TCA report action
TCA Threshold
TCA
Count period 15min /1 day
Count period 15min /1 day
CcCount period 15min /1 day
2.9.7.2 TCA threshold 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
(1of2)
LAYER PM TYPES 15m TCA THRESHOLD DEFAULT RS BBE ES SES UAS OFS MS BBE ES SES UAS FE-BBE FE-ES FE-SES FE-UAS MSP PSC PSD AU-4 PJE-P PJE-N VC-4 BBE ES SES UAS FE-BBE FE-ES FE-SES FE-UAS 65535 900 63 63 900 65535 900 63 63 65535 900 63 63 900 900 113184 113184 65535 900 63 63 65535 900 63 63 RANGE 0-16777215 0-900 0-900 0-900 0-900 0-16777215 0-900 0-900 0-900 0-16777215 0-900 0-900 0-900 0-900 0-900 0-113184 0-113184 0-65535 0-900 0-900 0-900 0-65535 0-900 0-900 0-900 24h TCA THRESHOLD DEFAULT 6291360 86400 4095 4095 86400 6291360 86400 4095 4095 6291360 86400 4095 4095 86400 86400 10865664 10865664 6291360 86400 4095 4095 6291360 86400 4095 4095 RANGE 0-1610612640 0-86400 0-86400 0-86400 0-86400 0-1610612640 0-86400 0-86400 0-86400 0-1610612640 0-86400 0-86400 0-86400 0-86400 0-86400 0-10865664 0-10865664 0-6291360 0-86400 0-86400 0-86400 0-6291360 0-86400 0-86400 0-86400
(2of2) LAYER PM TYPES 15m TCA THRESHOLD DEFAULT

VC-3 BBE ES SES UAS FE-BBE FE-ES FE-SES FE-UAS VC-12/VC11 BBE ES SES UAS FE-BBE FE-ES FE-SES FE-UAS TU PJE-P PJE-N 65535 900 63 63 65535 900 63 63 65535 900 63 63 65535 900 63 63 113184 113184
24h TCA THRESHOLD DEFAULT

6291360 86400 4095 4095 6291360 86400 4095 4095 6291360 86400 4095 4095 6291360 86400 4095 4095 10865664 10865664
RANGE
0-65535 0-900 0-900 0-900 0-65535 0-900 0-900 0-900 0-65535 0-900 0-900 0-900 0-65535 0-900 0-900 0-900 0-113184 0-113184
RANGE
0-6291360 0-86400 0-86400 0-86400 0-6291360 0-86400 0-86400 0-86400 0-6291360 0-86400 0-86400 0-86400 0-6291360 0-86400 0-86400 0-86400 0-10865664 0-10865664
Ethernet TCA
(1of3)
LAYER PM TYPES 15m TCA THRESHOLD DEFAULT ETH-TxOctet ETH-RxOctet ETH-RxFCSErrorFram e ETH-RxAlignmentError Frame ETH-TxUcastPkt ETH-TxNUcastPkt ETH-RxMulticastPkt ETH-RxBroadcastPkt ETH-TxSingleCollision Frame LAN ETH-TxMultiCollisionFr ame ETH-TxDelayTransmis sion ETH-TxExtCollisionFra me ETH-TxLateCollisionFr ame ETH-TxCollisionFrame ETH-RxPkt64 ETH-RxPkt65to127 ETH-RxPkt128to255 ETH-RxPkt256to511 ETH-RxPkt512to1023 RANGE 24h TCA THRESHOLD DEFAULT RANGE
4294967294 4294967294
133929000
0-4294967294 0-4294967294 0-133929000
4294967294 4294967294 4294967294
0-4294967294 0-4294967294 0-4294967294
133929000 133929000 133929000 133929000 133929000 133929000
0-133929000 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000
4294967294 4294967294 4294967294 4294967294 4294967294 4294967294
0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294
133929000
0-133929000
4294967294
0-4294967294
133929000
0-133929000
4294967294
0-4294967294
133929000
0-133929000
4294967294
0-4294967294
133929000 46875000 133929000 133929000 76014000 40760970 21146400
0-133929000 0-46875000 0-133929000 0-133929000 0-76014000 0-40760970 0-21146400
4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294
0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294
(2of3) LAYER PM TYPES 15m TCA THRESHOLD DEFAULT ETH-RxPkt1024toMax 10775700 429496729 4 7315200 133929000 265760848 265760848 152028000 81521940 42292800 21551400 21551400 133929000 133929000 133929000 133929000 133929000 133929000 RANGE 0-10775700 0-429496729 4 0-7315200 0-133929000 0-265760848 0-265760848 24h TCA THRESHOLD DEFAULT 4294967294 RANGE 0-4294967294
ETH-RxUnderSizePkt ETH-RxOverSizePkt ETH-DropPkt ETH-TR64 ETH-TR65to127 ETH-TR128to255 ETH-TR256to511 LAN ETH-TR512to1023 ETH-TR1024to1518 ETH-TRJumboPkt ETH-TxPauseFrame ETH-RxPauseFrame ETH-RxPkt ETH-TxPkt ETH-TxMulticastPkt ETH-TxBroadcastPkt ETH-TxOctet ETH-RxOctet ETH-RxFCSErrorFram e WAN ETH-RxAlignmentError Frame ETH-TxUcastPkt ETH-TxNUcastPkt ETH-RxMulticastPkt
4294967294 4294967294 4294967294 4294967294 4294967294
0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294
0-152028000 0-81521940 0-42292800 0-21551400 0-21551400 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000 0-4294967294 0-4294967294 0-133929000
4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294
0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294
4294967294 4294967294
133929000
133929000 133929000 133929000 133929000
0-133929000 0-133929000 0-133929000 0-133929000
4294967294 4294967294 4294967294 4294967294
0-4294967294 0-4294967294 0-4294967294 0-4294967294
(3of3) LAYER PM TYPES 15m TCA THRESHOLD DEFAULT ETH-RxBroadcastPkt ETH-RxPkt64 ETH-RxPkt65to127 ETH-RxPkt128to255 ETH-RxPkt256to511 ETH-RxPkt512to1023 ETH-RxPkt1024toMax ETH-RxUnderSizePkt ETH-RxOverSizePkt ETH-DropPkt ETH-TR64 WAN ETH-TR65to127 ETH-TR128to255 ETH-TR256to511 ETH-TR512to1023 ETH-TR1024to1518 ETH-TRJumboPkt ETH-TxPauseFrame ETH-RxPauseFrame ETH-RxPkt ETH-TxPkt ETH-TxMulticastPkt ETH-TxBroadcastPkt 133929000 133929000 133929000 76014000 40760970 21146400 10775700 429496729 4 7315200 133929000 265760848 265760848 152028000 81521940 42292800 21551400 21551400 133929000 133929000 133929000 133929000 133929000 133929000 RANGE 24h TCA THRESHOLD DEFAULT RANGE
0-133929000 0-133929000 0-133929000 0-76014000 0-40760970 0-21146400 0-10775700

0-429496729 4 0-7315200
4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294

4294967294 4294967294
0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294

0-4294967294 0-4294967294
0-133929000 0-265760848 0-265760848 0-152028000 0-81521940 0-42292800 0-21551400 0-21551400 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000 0-133929000
4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294 4294967294
0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294
GFP TCA
LAYER PM TYPES 15m TCA THRESHOLD DEFAULT GFP_TxPkt GFP_TxOctet GFP_RxPkt Encapsula tion GFP_RxOctet GFP_RxFCSError Pkt GFP_RxEXIErrorP kt 4294967294 4294967294 4294967294 4294967294 133929000 RANGE 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-133929000 24h TCA THRESHOLD DEFAULT 4294967294 4294967294 4294967294 4294967294 4294967294 RANGE 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294
133929000
0-133929000
4294967294
0-4294967294
LAPS TCA
LAYER PM TYPES 15m TCA THRESHOLD DEFAULT LAPS_TxPkt LAPS_TxOctet Encapsulatio n LAPS_RxPkt LAPS_RxOctet LAPS_RxFCSErro rPkt 4294967294 4294967294 4294967294 4294967294 133929000 RANGE 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-133929000 24h TCA THRESHOLD DEFAULT 4294967294 4294967294 4294967294 4294967294 4294967294 RANGE 0-4294967294 0-4294967294 0-4294967294 0-4294967294 0-4294967294
2.10 Fault management

2.10.1 Fault monitor items
SDH Alarm
(1of6) INDICATION CATEGORY DESCRIPTION AIS (only 2Mbps) APSD_n n=1,2 APSIN_n n=1,2 Facility Alarm indication signal Default APS Byte Receive Inconsistent APS Code Node ID Mismatch Improper APS Code Alarm indication signal FAULT LOCATION EXT CLK IN External timing source MST Upstream equipment MST Upstream equipment MST Upstream equipment MST Upstream equipment MSA MSA function in upstream equipment MSA MSA function in upstream equipment BUS_ERR OR CLKFAIL Equipment BUS defect BUS BUS_ERROR Facility Clock fail SETS Clock module CLKDRIF T Facility Frequency drift SETS Clock sending function in upstream equipment Protection Channel Mismatch Failure out of communicate MST Upstream equipment PKG can not communicate with PKG(eg.HDLC bus error,CPU reset) MN MJ MN MN MN MJ MJ MJ MJ MJ MJ DEFAULT CLASS MN
Protection
Protection
APSNIM_ Protection nn=1,2 APSIM_n n=1,2 AU-AIS Protection
Facility
AU-LOP
Facility
Loss of pointer
CMF
COMMUN ICATE_FA IL
Equipment
(2 of 6) INDICATION CATEGORY HKAn (n = 1 thru 8) HP-DEG Environme nt Facility DESCRIPTION House keeping alarms VC-4 B3 byte error(10-5) FAULT LOCATION Environment Environment device HPT HPT in upstream equipment or optical fiber and connector HPT HPT in upstream equipment or optical fiber and connector HPA Configuration in upstream equipment HPT Upstream equipment detecting HP alarm HPT J1 setting or upstream equipment setting HP-UNEQ Facility Unequipment HPT No crossconnect setting in upstream equipment LINK-FAIL Network LAPD communication fail F port link failed DCC Upstream equipment DCC failure DCC Ethernet port(F) is active,but it 's link down LOF Facility Loss of frame RST Upstream equipment LOF (only 2Mbps) LOM Facility Loss of frame EXT CLK IN External timing source Facility Los of multi-frame HPA HPA function in upstream equipment MJ MN CR MN MN MJ MJ MJ MJ MJ MN DEFAULT CLASS MN
HP-EXC
Facility
VC-4 B3 byte error(10-3)
HP-PLMF
Facility
Payload mismatch
HP-RDI
Facility
Remote defect indicate
HP-TIM
Facility
Trace mismatch
LINK_DOWN
Network
(3 of 6) INDICATION CATEGORY LOS Facility DESCRIPTION No signal input FAULT LOCATION SPI Optical fiber or upstream equipment 2M 2M input cable or upstream equipment EXT CLK IN (2Mbps) Input cable or external timing source LOS (2MHz) Facility No signal input EXT CLK IN Input cable or external timing source LOS (electrical INTF) LP-DEG Facility No signal input SPI Cable or upstream equipment Facility VC-3 B3 byte error (10-5) VC12 BIP-2 error (10-5) LP-EXC Facility VC-3 B3 byte error (10-3) VC12 BIP-2 error (10-3) LP-PLMF Facility Payload mismatch LPT LPT in upstream equipment or optical fiber and connector LPT LPT in upstream equipment or optical fiber and connector LPA Configuration in upstream equipment LPT Upstream equipment detecting LP alarm LPT J2 setting or upstream equipment setting LP-UNEQ Facility Unequipped LPT No crossconnect setting in upstream equipment MJ MJ MJ MJ MJ MN CR MN MN CR DEFAULT CLASS CR
LP-RDI
Facility
Remote defect indicate
LP-TIM
Facility
Trace mismatch
(4 of 6) INDICATION CATEGORY LTI Facility DESCRIPTION Los of External timing source Memory defect FAULT LOCATION SETS All the timing source MEM Memory fail MS-AIS Facility Alarm indication signal MS B2 byte error(10-5) MS B2 byte error (10-3) Remote defect indicate MST Upstream equipment MST Optical fiber or connector MST Optical fiber or connector MST Upstream equipment detecting alarm PKG (see NOTE) Cant be identified board PKG_REMO VED PKG_TYPE Equipment Remove board PKG (see NOTE) Not install board Equipment Wrong PKG install Remove port PKG (see NOTE) Wrong configuration PORT Not install port Equipment Wrong port install Remove port PORT Wrong configuration PORT Not install port Equipment Wrong port install Remove port PORT Wrong configuration PORT Not install port CR CR CR CR CR CR CR CR MJ MJ MN CR MN DEFAULT CLASS MJ
MEM_FAIL
Equipment
MS-DEG
Facility
MS-EXC
Facility
MS-RDI
Facility
PKG_FAIL
Equipment
Package defect
PORT_REM OVED (STM_1(O) ) PORT_TYPE (STM_1(O) ) PORT_REM OVED (STM_4(O) ) PORT_TYPE (STM_4(O) ) PORT_REM OVED (STM_16(O) ) PORT_TYPE (STM_16(O) )
Equipment
Equipment
Equipment
Equipment
Wrong port install
PORT Wrong configuration
CR
(5 of 6) INDICATION CATEGORY PORT_REM OVED (E1/VC12) PORT_REM OVED (EXTCLK IN) PORT_TYPE (EXTCLK IN) PORT_REM OVED (EXTCLK OUT) PORT_TYPE (EXTCLK OUT) PORT_REM OVED (V.11_Port) PORT_TYPE (V.11_Port) PORT_REM OVED (100BT_LAN _PORT) PORT_TYPE (100BT_LAN _PORT) PORT_REM OVED (100BT_WA N_PORT) PORT_TYPE (100BT_WA N_PORT)v PPI_AIS PPS-FAIL Facility Equipment Wrong port install PORT Wrong configuration PPI Frame all "1" HPC, LPC Both not receiving signals CR MN CR Equipment Equipment Wrong port install PORT Wrong configuration PORT Not install port CR CR Equipment Equipment Wrong port install Remove port PORT Wrong configuration PORT Not install portv CR CR Equipment Equipment Wrong port install PORT Wrong configuration PORT Not install port CR CR Equipment Equipment Wrong port install Remove port PORT Wrong configuration PORT Not install port CR CR Equipment Remove port PORT Not install port CR Equipment DESCRIPTION Remove port FAULT LOCATION PORT Not install port DEFAULT CLASS CR
Remove port
Remove port
Alarm indication signal PPS failed
Protection
(6 of 6) INDICATION CATEGORY PSBF Protection DESCRIPTION Protection Switch Byte Failure SSM failure FAULT LOCATION MST Upstream equipment SETS Upstream equipment RINGSW_FA Protection IL_nn=1,2 RS-TIM Facility RING SW Failure Trace mismatch MST Both not receiving signals RST J0 setting or upstream equipment setting TAF Protection Type of Architecture Failure Alarm indication signal MST Upstream equipment HPA, LPA HPA function in upstream equipment HPA HPA function in upstream equipment MJ MJ MJ CR MJ MN DEFAULT CLASS MJ
REF_FAIL
Facility
TU-AIS
Facility
TU-LOP
Facility
Loss of pointer
NOTE: PKG (Package) indicates boards.
Ethernet Alarm
INDICATION CATEGORY DESCRIPTION Loss of Client Signal CSF_LCS CSF_LCSync CSF_R_LCS CSF_R_LCS ync DropPkt_EX C LINK_DOWN LOS HP-Xv-LOA PORT_TYPE RxAlignment ErrorFrame_ EXC Facility Facility Facility Facility Facility Facility Facility Facility Facility Facility Loss of Client Character Synchronization Remote end Loss of Client Signal Remote end Loss of Client Character Synchronization A count of drop packets. Alarm for the link status. No signal input Loss of Alignment Wrong port install 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 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. Number of collisions on this Ethernet segment 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. FAULT LOCATION Ethernet (WAN) Ethernet (WAN) Ethernet (WAN) Ethernet (WAN) Ethernet (LAN&WAN) Ethernet (LAN&WAN) Ethernet (LAN) Ethernet (WAN) Ethernet (LAN&WAN) Ethernet (LAN&WAN) DEFAULT CLASS MJ MJ MN MN MJ CR CR MJ CR MJ
RxFCSErrorF rame_EXC
Facility
Ethernet (LAN&WAN)
MJ
TxCollisionFr ame_EXC RxAlignment ErrorFrame_ EXC
Facility Facility
Ethernet (LAN) Ethernet (LAN&WAN)
MJ MJ
(2of2) INDICATION CATEGORY RxFCSErrorF rame_EXC Facility DESCRIPTION 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. A count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy A count of frames for which transmission on a particular interface fails due to excessive collisions. The number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet WAN port DEG WAN port fail FAULT LOCATION Ethernet (LAN&WAN) DEFAULT CLASS MJ
TxDelayTran smissionFra me_EXC
Facility
Ethernet (LAN)
MJ
TxExtCollisio nFrame_EXC
Facility
Ethernet (LAN)
MJ
TxLateCollisi onFrame_EX C
Facility
Ethernet (LAN)
MJ
WAN_PORT _SD WAN_PORT _SF
Facility Facility
Ethernet (WAN) Ethernet (WAN)
MN MJ
NOTE: 1. CR: Critical, MJ:Major, MN:Minor, WN:Warning. 2. 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 DropPkt_EXC RxAlignmentErrorFrame _EXC RxFCSErrorFrame_EX C TxCollisionFrame_EXC TxDelayTransmission_E XC TxExtCollisionFrame_E XC TxLateCollisionFrame_ EXC PERFORMANCE ETH-DropPkt ETH-RxAlignmen tErrorFrame ETH-RxFCSErrorFram e ETHTxCollisionFrame ETHTxDelayTransmission ETH-TxExtCollisionFra me ETHTxLateCollisionFrame DEFAULT THRESHOLD 4294967294 4294967294 0~4294967294 4294967294 0~4294967294 4294967294 0~4294967294 4294967294 0~4294967294 4294967294 0~4294967294 4294967294 0~4294967294 THRESHOLD SETTING RANGE 0~4294967294
Encapsulation Alarm
INDICATION SSF_LGS LAPS_FAIL CATEGORY Facility Facility DESCRIPTION Loss of GFP frame Synchronization LAPS Layer Fail FAULT LOCATION WAN WAN DEFAULT CLASS MJ MJ
Virtual Concatenation Alarm

INDICATION LP-Xv-LOA LP-Xv-LOM LP-Xv-PLM LP-Xv-SQM HP-Xv-LO M HP-Xv-SQ M HP-Xv-LOA CATEGORY Facility Facility Facility Facility Facility Facility Facility DESCRIPTION Loss of Alignment Loss of Multi-frame defect Extended signal label mismatch Loss of Sequence defect Loss of Multi-frame defect Loss of Sequence defect Loss of Alignment VC4 VC4 MJ MJ FAULT LOCATION VC12/VC3 VC12/VC3 VC12 VC12/VC3 VC4 DEFAULT CLASS MJ MJ MJ MJ MJ
2.10.2 Alarm management

The alarm severity of each failure is indicated by the following alarm level and alarm class. Alarm classes can be modified. Modification is done by using Alarm Severity Assignment 2.10.2.1 Alarm Class
CR Critical: service-affecting condition has occurred and an immediate corrective action is required, such as when a managed object becomes totally out of service and its capability must be restored. MJ Major: service-affecting condition has developed and an immediate corrective action is required, such as when there is a severe degradation in the capability of the managed object and its full capability must be restored. MN Minor: existence of non-service-affecting fault and a corrective action should be taken to prevent a more serious (i.e., service-affecting) fault. This severity can be used, for example, when the detected alarm is not currently degrading the capacity of the managed object. WN Warning: existence of non-service-affecting fault and a corrective action should be taken to prevent a more serious (i.e., service-affecting) fault. All alarms in V-Node don't belong to this class by default. 2.10.2.2 Delay/Stretch Time
The following describes the functions of Delay and Stretch Time. Delay and stretch are only applied on alarm report function and they are not effective alarm action, for example, when AIS inserts at LOS detection: Delay Time Delay Time is a specific period for the process to determine if the detected failure is an alarm to be reported. Delay Time: 0 to 2.5 seconds, step=0.5 Stretch Time Stretch Time is a specific period for the process to determine if the alarm has been cleared. Stretch Time: 0 to 10 seconds, step=0.5
2.10.3 Alarm report

When an alarm is detected, alarm notification is made to the user by lighting up the LEDs on the rack, and reporting the alarm to user interface (for example, the Equipment CID display). The alarm notification is also made to the user by an Office alarm, such as the station alarm bell and lamps. 2.10.3.1 LED Process
LED on front of rack lights up/turn off when alarm is generated/cleared to report the alarm to the user. Detail LED indication rule refer to 11_04 of the F5259_F10 OPERATION AND MAINTENANCE manual.
2.10.3.2
Report to User Interface
The Time, location etc information should be report to CID/NMS. Alarm is automatically reported to User Interface when alarm is generated/cleared; Alarm report includes time information when equipment confirms alarm occurrence and recovery; Alarm report include the alarm location information which board and section the alarm locates; User can set whether automatic report is on or off to each user port. All the alarm status in NE can be read collectively. 2.10.3.3 Office Alarms
V-Node has four types of office alarms output: Alarm output for Bell (AB), Alarm Lamp (AL), Prompt Maintenance (PM), Differed Maintenance (DM) and LED on front of Rack. Following table lists the relationship of alarm class and office alarm.
RANK OF ALARM CR (Critical) MJ (Major) MN (Minor) WN (Warning) ACO function
REPORT TO OS V V V V
PM V V
DM
AB V V
AL V V V
LED V V V
NOTE: 1) 2) 2.10.3.4 V denotes corresponding office alarm in the column will report when corresponding class alarm in the row occurs. LED means each package fail LED. ACO Function
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.
2.11 Maintenance Management

Maintenance management provides convenient equipment maintenance operation for users and helps them to find out the failure rapidly and clear it in time to ensure the normal operation of SDH sub-network. Main function of the maintenance management is unit reset, loopback control, software download online, simple upgrade, EMS memory management, automatic laser shutdown, overhead access, house keeping, and security: Unit reset Equipment initialization function Loopback control Loopback control for each tributary. Software upgrade Configuration download /upload Automatic laser shutdown Overhead function House keeping Security The software can be downloaded via online and the current version can be obtained (updated) smoothly without influence of running traffic.
2.11.1 Unit Rest

When reset the unit, the service signal, current switch status, performance, alarm and clock would not be influenced. During the reset, both the alarm and the performance count would not be recorded. And the first 15 minutes performance after reset is invalid. Reset function availability of all the units is shown as following:
Table 2-10.
Reset Function of Units
2.11.1.1
Hot start reset
The unit should startup using the backup data after reset action. Within this period the main signal should not be interrupt, and the network communication should be normal. This type of reset should be issued from NMS/CID (local or remote), and also possible from a push button. 2.11.1.2 Cutover reset
Cutover is issued manually; only available for the units, which obtain the backup F/W, the equipment uses the backup data to startup. This action should not interrupt the main signal, and the network communication should be normal. It is issued from NMS/CID (local or remote). 2.11.1.3 System initialization
If this action is operated, the system should cold start. It is only available from CID (local)
2.11.2 Equipment Initialization

The equipment initialization operation would clear all database records, and recover the default users account. When finish the initialization, the equipment would reset automatically, and you need to log in the CID again. (For the IP addresses are cleared from the database, you must log in CID by the default users account through the f port).then the equipments configuration before the delivery is recovered.
2.11.3 Loopback
NOTE: In remote login loopback for SDH interface is forbidden, but that for PDH interface is allowed. 2.11.3.1 Facility loopback
STM-N optical signal When Facility loopback is operated AIS signal shall be sent to cross connect side.
STM-1/4 o and STM-16
MST
RST
SPI
OPT OUT
FAC LPB
SA
MST
RST
MS-AIS
SPI
OPT IN
STM-1e signal When Facility loopback is operated AIS signal shall be sent to cross connect side.
STM-1 e
MST
RST
SPI
OUT
FAC LPB
SA
MST
RST
MS-AIS
SPI
IN
PDH signal The signal which is at instant behind the PDH signal input side is returned to opposite end. In facility loopback action, the AIS signal is sent to SDH side in mapping PDH signal.
PDH
AIS PI LPA LPT HPA
INTF
PI
LPA
LPT
HPA
2.11.3.2
Terminal loopback
STM-N signal
The signal sent to opposite end is same as the signal returned to local end (cross connect)
STM-1/4 o and STM-16
MST
RST
SPI
OPT OUT
TRM LPB
SA
MST
RST
SPI
OPT IN
STM-1e Signal
The signal sent to opposite end is same as the signal returned to local end (cross connect).
STM-1e
MST
RST
SPI
OUT
TRM LPB
SA
MST
RST
SPI
IN
PDH signal
The 2M/34M/45M signal which is at instant before the PDH signal output side of the electronic signal sent out port is returned to local end. In Terminal loop back action no handling with the returned signal. The signal sent to the PDH line side in loop back action is AIS signal.
2.11.4 Software Download

F/W is the software program for CPU on the PKG. In order to upgrade or downgrade the NE, the F/W needs to be downloaded from CID to NE firstly. Download object:
PKG Name MCP CS FW FPGA FW FPGA A FPGA B STM-16 STM-1/4 S1E E1 E31/E32 FE GE FPGA FPGA FPGA FPGA FPGA FW FPGA FW FPGA F/W or FPGA
Download trace 1. CID -> MCP download (F/W and FPGA) Download F/W: CID -> MCP temporary memory -> MCP Flash ROM.
Download FPFA: CID -> MCP temporary memory -> MCP Flash ROM -> initial FPGA. 2. CID -> CS download (F/W and FPGA) Download F/W: CID -> MCP agent -> CS temporary memory -> CS Flash ROM.
Download FPFA: CID -> MCP agent -> CS temporary memory -> CS Flash ROM -> initial FPGA. 3. CID -> SDH board download Download F/W: CID-> MCP agent -> CS temporary memory -> CS Flash ROM -> initial FPGA. 4. CID -> FE download Download F/W: CID -> MCP agent -> FE temporary memory -> FE Flash ROM. Download FPGA: CID-> MCP agent -> FE temporary memory -> FE Flash ROM -> initial FPGA. F/W download sequence The following is an example for downloading the F/W of the MCP board. The procedures about downloading the F/W of the other boards are similar.
Procedure 2-1.
Downloading the F/W of the MCP Board
2.11.5 Software Upgrade

FW upgrade does not influence the service. FW upgrade files can be saved to 2 copies in the equipment which can be served as the active or the standby. The current running version is served as the active and another version as the standby. FW upgrade means that save the new version file to the standby area, and it would not influence the running version. After FW upgrade, the system would take the new FW version trial running in the 5 minutes, if reset or power off-on the equipment, the system will run the FW version before upgrade. The operation of the FPGA upgrade would influence the service and DCC communication. When upgrade FPGA, there is not a trial running period, that is to say, the system would download the FPGA file to the hardware immediately.
2.11.6 Configuration Download/Upload

Configuration uploading will upload the configuration data in the equipment to the directory which specified by user, and save it as the file. Configuration download operation will download the configuration file to the equipment. When user makes this configuration effective, the equipment will save it to the Flash, and reconfigure the system according to the configuration. Otherwise, this configuration would not be used, and only saved in the DRAM of the equipment, if reset or power off-on is happened on the equipment, these configuration data would be lost, and the equipment would run with the configuration data in Flash before.
2.11.7 Automatic Laser Shutdown

ALS function is described in ITU-T G.958 appendix II. When optical fiber breaks, in order to prevent the personnel from damage with the laser signal, it is need to shut down the output signal from optical transceiver, called ALS (Automatic Laser Shutdown) function. For this system, ALS is required only for STM-16 interface. 2.11.7.1 ALS Action Criteria
When signal LOS occurs at the optical input port of unit, if it last over 500 50 msec from unit detecting the LOS, unit start to operate the command of shut down the optical signal, unit stop outputting optical signal within 700 msec from signal LOS occurs. Following is the time sequence from signal LOS occurs to stopping optical signal.
Figure 2-69.
The time sequence from signal LOS occurs to stopping optical signal.
Figure 2-70.
ALS release
2.11.7.2
ALS release criteria
Auto-restart: The unit should output optical signal last 2sec 0.25sec and 9sec 0.5sec period, which is controlled by a timer. If the fault restore, the ALS status will be released automatically. The timer is set with every single interface, the setting range is: 60sec / 180 sec / 300sec. Manual restart: Command of manual restart can be sent from CID/NMS to make unit interface output optical signal, release the ALS status. The parameter of this command is: Short-on: 2sec 0.25sec (9sec 0.5sec) Long-on: 90sec 10sec ALS release restrain The response time from input port receive the optical signal to output port starting send optical signal should be within 0.85sec. Following is the ALS auto-release sequence:
Figure 2-71. 2.11.7.3
ALS release steps
ALS Function enable/disable
ALS enable/disable setting can be designated from CID/NMS, with every single interface. 2.11.7.4 Force optical signal shut down
The optic signal can be forced shut down by the command from CID/NMS, with every single interface. The forced shut down status can be released by the command. 2.11.7.5 ALS status
ALS status indicating the state of whether output optic signal or not, with every single interface. ALS status can be acquired from CID/NMS
2.11.7.6
ALS setting items Table 2-11.

General
ALS setting items

Command
Items ALS UI enable/disable setting CID NMS Yes Yes Output optic signal command (long/short) Yes Yes Force optic signal shut down Yes Yes ALS status acquire Yes Yes
2.11.8 Overhead Function

The OH function extract E2 or F1 byte from optical/electric interface to user channel (V.11), and insert them along the opposite direction. 2.11.8.1 OH Cross Connection/OH Through
Bypass the E2 or F1 byte from the different direction and different user data channel. Please pay attention: The bypass operation can not be performed between E2 and F1. 2.11.8.2 Accessible OH kind
The OH byte of the user data channel includes the E2 and F1 byte which can be configured by CID. 2.11.8.3 Co/Contra Direction
The co/contra direction function means the working mode of the user channel. Co-direction: the data receiving direction is the same as the clock output/input direction. Contra direction: the data receiving direction is different from the clock output/ input direction.
2.11.9 House Keeping

2.11.9.1 HKA function
The system must support the housekeeping alarm function. This function supply users a way to monitor other assistant equipments status and keep both the station and system suitable and safe. Input port: Port number: 8 Alarm logic:
CloseLoop Open Default Alarm Normal
Alarm logic can be changed and selectable by user for each port from NMS/CID. Alarm name setting: External alarm can be named for each HKA port (max character number is 32). The characters can be used refer to the table character code table. The HKA name can be changed when this HKA is occurring. The new name will display after the name is changed. And then the history of old name clear, remain the history of new name HKA. 2.11.9.2 HKC function
This function is used to operate a command issued from NMS/LCT to control external equipment remotely. HKC Ports: Port number: 4 Control Logic: HKC alarm polarity and duration time can be set per port. Default is CLOSED" Control signal Setting Controlling signal name can be set for each HKC port via NMS/LCT. (Max number is 20). The characters can be used in name refer to the table character code table.
Control time Table 2-12. Momentary Control Time Setting Note 2sec (by eye)
Continually
Control time 0min 1c 254min Infinity
Default
- Momentary timer setting: 0 to 254min with 1 min step - When the setting is 0, no any pulse is generated.
2.11.10
Security management
Security Management provides security environment for user, which permits only registered user, for example, to configure NE, to monitor alarm and status from NE, and to download firmware to NE. Usable functions for each user are limited according to user level of each user. Below table shows the detail information of user authority. NOTE: 1) O: means the permission of operation X: means the denial of operation *: means the user only have the right to operate the lower level user 2) Level 4 System Administrator (Highest) Level 3 System Maintenance Level 2 System Operator Level 1 System Watcher (Lowest)
(1of3)
Function List PM Browse Current Performance (including of 15M and 24H) Browse History Performance (including ,of 15M and 24H) Reset the performance counters Set the performance threshold (including of 15M and 24H) Inhibit the reporting of the performance Set the switch state of reporting zero value Set the switch state of recording zero value Set the switch state of reporting event of performance Browse the attributes of all kinds of performance ALM Retrieve and browse the current Alarm Retrieve and browse the history alarm Inhibit the alarm reporting Set the delay time of reporting alarm generation Set the stretch time of reporting alarm disappear Set the alarm severity Browse the attributes of all kinds of alarm Retrieve and browse a variety of events (including protection switch, time source switch,) Configuration Modify NE's attributes Browse NE's attributes Install panel Uninstall panel Set the attributes of network administration port(Ethernet) Browse the attributes of network administration Port (Ethernet) Set the attributes of environment ports Browse the attributes of environment ports Set the attributes of out environment ports Browse the attributes of out environment ports Set the orderwire numbers of broadcasting, group and individual Browse the orderwire numbers of broadcasting, group and individual Set the sending and expecting value of J byte (including J0/ J1 / J2) User Level Level4 Level3 Level2 Level 1
O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O
O O X X X X X X O O O X X X X O O X O X X X O X O X O X O X
(2of3)
Function List Browse the J value (including J0,J1 and J2) Browse the C2/V5 value Set terminal and facility loopback Cancel the loopback Install Cross-Module Uninstall Cross-Module Download firmware Upgrade firmware Browse the version information and working state of firmware Establish Cross-Connect Set Cross-Connect attributes (including path label, path attribute, direction, restore, switch holdoff time, restore delay time, switch condition (such as EXEC,SD, TIM and Extra Command) and support of extra command (such as Lockout, Force, Manual, Exercise)) Browse Cross-Connect attributes (including path label, path attribute, direction, restore, switch holdoff time, restore delay time, switch condition (such as EXEC, SD, TIM and Extra Command), support of extra command (such as Lockout, Force, Manual, Exercise) and working state) Delete Cross-Connect Delete All Cross-Connect Modify Cross-Connect Attribute Set SNCP Set the attributes of system clock source (including priority, restorable, lockout threshold, switch holdoff time, delay time of restore, the forced sending SSM value, the switch state of sending forced SSM value, and support of extra command (such as Lockout, Force, Manual)) Browse the attributes of system clock source (including priority, restorable, lockout threshold, switch holdoff time, delay time of restore, the forced sending SSM value, receiving SSM value, the switch state of sending forced SSM value and support of extra command (such as Lockout, Force, Manual)) User Level Level4 Level3 Level2 Level 1
O O O O O O O O O O
O O O O O O O O O O
O O O O O O X X O O
O O X X X X X X O X
O O O O O
O O O O O
O O X O O
O X X X X
(3of3)
Function List Set the attributes of pass through clock source (including priority, restorable, lockout threshold, switch holdoff time, delay time of restore, the forced sending SSM value, the switch of sending forced SSM value and support of extra command (such as Lockout, Force, Manual)) Browse the attributes of pass through clock source (including priority, restorable, lockout threshold, switch holdoff time, delay time of restore, the forced sending SSM value, the switch of sending forced SSM value, receiving SSM value and support of extra command (such as Lockout, Force, Manual)) Set NE time Browse NE time Database up/download Security Create user Delete user Change password Modify the user level Set the life of user Browse the user information Browse the log of operation User Level Level4 Level3 Level2 Level 1
O O O O O O O O O O O
O O O O O* O* O* O* O* O* X
O O O X X X X X X X X
O X O X X X X X X X X
2.12 Memory Management

Database includes all the configuration information of system and software save the database in Flash ROM. Then even if system is power off and on, software can resume all traffic based on the database.
2.12.1 Database Distribution

In this system the MCP unit, Cross-connection unit have Flash ROM to save database. In MCP unit, the working and protection CS unit, the Flash ROM save all the databases of the system. In the FE/GE unit only that databases relate to FE/GE are saved to the DRAM. Table 2-13.
MCP unit
Database distribution table

Protection CS unit FE Unit
Primary CS unit
All databases in Flash ROM
Databases relate to FE in DRAM
The database in working CS unit is the core. Database in MCP, protection CS unit, FE units and GE unit are got from the working CS unit and is checked whether keeping with working CS unit periodically.
2.12.2 Database Action

2.12.2.1 Database Cycle Synchrony
When write each database into flash, the working CS unit record the current date and save it into flash too. This is called Time flag. MCP unit retrieves the Time flag of all databases from the working CS unit every 10 seconds. If there are some Time flag of databases differing to itself, then MCP unit send database upload command to the working CS and CS will send the indicated database and Time flag to MCP. So MCP can keep the database same as the working CS.
Figure 2-72.
Database cycle synchrony between MCP and working CS
The working CS unit sends the Time flag of all databases to the protection CS unit every 10 seconds. If all of the Time flag of databases are same as protection CS, protection CS send success result to the working CS. If there are some differences, protection CS will send the database ID which has different Time flag to working CS and working CS will send the indicated database and Time flag to protection CS.
Figure 2-73.
Database cycle synchrony between working CS and protection CS
NOTE: Database cycle synchrony for FE unit or GE unit is same as for protection CS.
2.12.2.2
Download Database
When LCT/EMS download database, MCP receive it and send to working CS unit. In working CS unit database is send to the protection CS Unit then written into Flash ROM of working CS unit. And MCP writes the database into itself Flash ROM after working CS unit save database and responds the success to MCP unit. Please the following Figure 2-74.
Figure 2-74. Database download 2.12.2.3 Upload Database
When CID uploads system database, MCP will send the command to working CS unit and databases in the Flash ROM of working CS unit are reported to CID.
Figure 2-75. 2.12.2.4 System Power On
Database upload
After system power on, the working CS will start up with itself database. MCP unit start up as the following.
Figure 2-76.
MCP unit start up
Figure 2-77.
Protection CS unit start up
For FE unit or GE unit, it use itself database to initial MIB and HW after power. After the working CS finish initialization, it will start cycle synchrony database for FE unit or GE unit. If there are some database with different time flag, working CS will send database to FE unit or GE unit and then the FE unit or the GE unit initialize the database to MIB and HW. 2.12.2.5 Unit Replace
Unit replacing is same as power on. 2.12.2.6 Database Restore from MCP
In V-Node design, the database in the working CS unit is the core. Database in other boards is from the working CS unit. It calls Online Mode. The descriptions from 2.12.2.1 to 2.12.2.5 are under Online Mode. Sometime without CS unit, customer want to configure something to NE (with MCP) at first and once CS unit inserting the configuration in MCP can be saved to the working CS unit. So in this system, Offline Mode is supplied to implement it. In MCP unit, there is a switch with 8 switch points. If the 5th switch point is set to ON, it means Offline Mode. OFF means Online Mode The following is to describe the Offline Mode. First, without CS unit insertion:
Secondly, inserting CS unit, MCP will retrieve the DB time flag in CS unit and download DB to CS unit if there are some time flags difference between MCP and CS unit.
Offline Mode is useful in some cases. For example, NE is installed with one CS unit only and this CS unit is failed now. Customer need replace a new CS unit and expect all of the previous configurations of this NE are saved into new CS unit automatically and do not need do all settings from LCT again. Then customer can poll out MCP unit and set it into Offline Mode and insert again. Continuously insert new CS unit. After CS unit normal lighter blinking and waiting more than 30 seconds for DB synchrony between MCP and CS, then customer can restore the MCP to Online Mode again. The following figure is describing the flowchart of MCP unit with Offline Mode after power on or resetting.
2.13 OW Function
Figure 2-78
The OW Overlap Module
The function of OW OVERLAP module is overlap local OW and multi-way OWs from tributary into 64k PCM digital signal, then send it to tributary and realize re-connection without loss.
2.13.1 OW interface
TEL set is used for OW, RJ11 interface is specific, and both the E1 and E2 OH byte is used for OW.
2.13.2 OW function
Coding law: A law/ law Calling method: the equipment must support the following calling type: all-call; selective-call; group-call. Calling number consists of three-digit number User setting: User can do the setting to select the coding law, calling number; and the group-call ID of the every single equipment on CID.
2.13.3 Calling method

All-Call
Send code: Default 000(DTMF); General Spec: 000(DTMF) Receive code: If receive the code of 000 (DTMF), the buzzer rings.
Selective-Call
At call-originating station, connect the telephone set to TEL SET terminal, and dial the number (call ID) of the NE that you want to communicate with. Only the dialed station is called. NOTE: Because the codes of 0,00,000 are used in all call, so they cannot be used here.
Group-Call
At call-originating station, connect telephone set to the TEL SET terminal, and dial the number (group call ID) of NE that you want to communicate with. Dialed station(s) that has (have) same group call ID in the network is (are) called. NOTE: The Group ID can be set in CID.
2.13.4 Branch function

In order to communicate with the branches (Up to 6 orderwire branches are available at the same time though up to 26 optical ports are provided in VNODE.), the tone signal of each order wire interface will synthesize branch. The branch is synthesized by digital way.
Figure 2-79. OW branch process NOTE: In the digital circuit not connected, insert idle code. Call sequence description Voltage level Tx: -3 ~ -10 dBm Rx: -2 ~ -25 dBm
2.13.5 Sequence description

Tx: Tone: 100ms Interval: 100ms Ring tone: one-second ring; two seconds silence Rx: Tone time: 500msec ~ 1000msec Interval: 150msec ~ 2s
2.13.6 Idle code

Fault When optical input failed, E1 byte is sent to STM-N line as idle code Not-used Optical output (E1 byte) is: A law: 55h law: FFh
2.14 LAPD/Network /Routing Protocol

Data Link Layer : IEEE 802.3, LAPD IEEE 802.3 IEEE LAN protocol can carry out the MAC sub-layer of between the physical layer and the data link layer. The IEEE 802.3s CSMA/CD is used with different speed on many physical mediums. The expansion version of the IEEE 802.3 protocol specifies the fast Ethernet. The changes of the original IEEE 802.3 protocol on the physics cover 10Base2, 10Base5, 10BaseF, 10BaseT and 10Broad36. The changes of the fast Ethernet cover 100BaseT, 100BaseT4 and 100BaseX. LAPD (link access protocol on D channel): ISDN data link layer protocol on D channel. LAPD is originated from LAPB protocol, mainly designed for the signaling of the primary rate ISDN. It is specified by the ITU-T Q.920 and Q.921. Network Layer : IP IP (internet protocol): network layer protocol in the TCP/IP stack, it provides a connection-less internet service. IP provides addressing function, rule of service type, segment store and re-united, and security. It is recorded in the document RFC 791. Transport Layer: TCP, UDP TCP (transport control protocol): connection oriented transport layer protocol, which provides reliable, full duplex data transmission. TCP is part of TCP/IP protocol stack. UDP (user datagram protocol): connection-less transport protocol in the TCP/IP protocol stack. User datagram protocol is a simple protocol, exchange message under non-confirmation and guaranteed transmission, both error process and re-transmitted are processed by other protocols,. User datagram protocol is specified in the RFC 768. Network Layer: RIP RIP V1 is on the UDP layer, but it should be described into Network Layer RIP (route information protocol): a kind of IGP (inter gateway protocol) provided by the UNIX BSD system, which is the most popular IGP in the internet. Route information protocol use hops of network segment as measure unit.
PFC socket and RM Interface should be over TCP layer. PFC socket: PFC Socket is the socket supporting send buffer status management function, confirmation for arrival status of transmitted data function, and Health-check function.
2.15 Real Time Clock System

The Real Timer is used to provide Equipment with accurate time. After equipment reset or power on, the time of Real Timer is accurate.
2.15.1 Features
Real Time Clock/Calendar Tracks time in Hours, Minutes, and Seconds Day of the Week, Day, Month, and Year Battery Switch After equipment power down, the battery is power supply. High Reliability Data Retention: 100 years Endurance: 100,000 cycles per byte Low Power CMOS 1.25A Operating Current (Typical)
2.15.2 Block Diagram
Figure 2-80
Block Diagram of Real Timer
2.16 Equipment Cooling System

The fan would adjust its speed according to the temperature changing of the corresponding board slots.
2.16.1 The threshold of the fan speed

Under 60C: low speed 60C ~ 80C: middle speed Up 80C: high speed
2.16.2 The LED Status of FAN Board

Table 2-14. LED Status of the FAN Board
LED PWR STAUS ON OFF DESCRIPTION The fan is working The fan stop
2.17 Power Management System

The equipment adopts two power boards to protect the power supply interface system and the each board adopts the fusing type fuse to protect its internal circuit.
2.18 Retiming Buffer

2.18.1 Functional Description and Block Diagram
The retiming buffer is used for retiming function in E1 board. Its block diagram is shown as below:
Figure 2-81
The Retiming Function Diagram
The part closed in the dash line carries out retiming function. The key part is a 256 bits FIFO, a writing pointer producing circuit and a reading pointer producing circuit. The three part circuits function is described as below: FIFO: The part of circuit provides a retiming buffer memory; the capacity for 2Mbit/s service retiming is 256 bits. It is separated as two 128 bits, one avoiding reading empty, another avoiding FIFO overflow. Hence the available depth is 128 bits (the capacity is 62.5us for 2Mbit/s service).
Writing pointer producing circuit: The part of circuit is mainly used for producing pointer for data written into FIFO. The clock for producing the pointer is the clock sent from E1 side by Mapper. The part also compares whether the reading pointer and writing pointer are same or not, if same, the writing pointer is adjusted 128 bits to avoid FIFO overflow or empty. Reading pointer producing circuit: The part of circuit is mainly used for producing pointer for data read from FIFO. The clock for producing the pointer is local system clock which is SEC of SDH network and provided by system clock module.
2.19 LOG
A list of the operation logs and event logs of the NE can be recorded. Event Log: max 500 items for each event log (TCA,PPS 3000) Command Log: max 500 items.
3. EXTERNAL INTERFACES
3.1 User channel
Physical interface: V.11, 64kb/s Mode: Co- directional/Contra-directional Max Cable length: 1KM Connector: RJ45 Interface control: Add/Drop or Bypass Accessible OH Byte: F1, E2 Maximum user data channel interface:6
3.2 Orderwire
Level Diagram: Rx: 2 dBm Tx 0 dBm DTMF Tone Level: Impedance: 600ohm Signal Instruction Mode: dual tone multi-frequency mode (DTMF) Single Tone: Frequency: Dialing tone: Ring back tone: Busy tone: Notice mode: 450Hz long continuous tone 1 second connecting, 2 seconds disconnecting 0.4 seconds disconnecting and continuing buzzer-producing tone Rx 10 dBm Tx: 10 dBm
Station addresses: up to 999
External Interfaces 3-1
Operation mode: All call/ Group call/Selective call All call: Group call: All NEs whose orderwire channel(s) is (are) opened and corresponding optical port(s) connected by fibers are called. The NEs whose orderwire channel(s) is (are) opened and corresponding optical port(s) connected by fibers and group calling number is matched are called. The NEs whose orderwire channel(s) is (are) opened and corresponding optical port(s) connected by fibers and selective calling number is matched are called.
Selective call:
Connector: RJ11 Accessible OH Byte: E1,E2 Up to 6 orderwire branches are available at the same time though up to 26 optical ports are provided in V-Node. NOTE: At least one direction of one port must be close to prevent OW loop in a ring network.
3.3 User Interface

3.3.1 CID Interface
Physical Layer: f port: RS232C F port: 10BaseT Protocol: Connector: Both OSI and TCP/IP f port: the pin assignment between RJ45 and D-sub 9pin F port: the pin assignment between RJ45 and RJ45 (Shown as below figure) f port:RS232C Cable (Detail refers to Chapter 8) F port: UTP Straight cable (via HUB)
Connection:
Figure 3-1.
RJ45 connector of f port
Figure 3-2.
D-sub 9pin connector of f port
Figure 3-3.
RJ45 connector of F port
3.3.2 NMS
Physical Layer: Connector: Connection: Protocol: 10Base-T (Half/10M) RJ-45 (by F port) UTP Straight cable (via Hub) Both OSI and TCP/IP
3.4 Physical Specification

3.4.1 V-Node Subrack Dimensions
Height: Width: Depth: Weight: NOTE: 1. Above dimension includes any projection of subrack. 2. The rearpanel means the PCB board in the back of the V-Node equipment, and the backpanel is a steel board on the back of the V-Node equipment subrack. 487.6 mm 524.4 mm (with rack ear) 272.3 mm 11 Kg (backpanel and filter box are included, but rearpanel is excepted)

F05 Work

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

F05 Work

Încărcat de

Drepturi de autor:

Formate disponibile

F5259_F05

F5259_F05 FUNCTIONAL DESCRIPTION

SpectralWave is a registered trademark of NEC Corporation.

F5259_F05 FUNCTIONAL DESCRIPTION

2. V-NODE WORKING PRINCIPLE

2.1 Login/Logout..................................................................................... 2-1 2.2 Layer 2 Switch Function .................................................................. 2-2

2.3 Encapsulation and LCAS Function ............................................... 2-57

2.4 Cross connection ........................................................................... 2-72

2.5 Protection........................................................................................ 2-84

F5259_F05 FUNCTIONAL DESCRIPTION

2.5.2 2.5.3 2.5.4 2.5.5

2.6 Synchronization............................................................................ 2-100

2.10 Fault management ........................................................................ 2-131

2.11 Maintenance Management ........................................................... 2-143

2.12 Memory Management ................................................................... 2-161

F5259_F05 FUNCTIONAL DESCRIPTION

2.13 OW Function ................................................................................. 2-169

2.16 Equipment Cooling System ......................................................... 2-174

2.19 LOG................................................................................................ 2-176

3.4 Physical Specification...................................................................... 3-4

This page is intentionally left blank.

F5259_F05 FUNCTIONAL DESCRIPTION

1. SDH WORKING PRINCIPLE

Figure 1-1. STM-N Signal Multiplexing Paths

SDH Working Principle 1-1

F5259_F05 FUNCTIONAL DESCRIPTION

1.2 Basic Parameters

Figure 1-2. Basic Frame Structure

Table 1-1. Frame Structure Parameter of STM-N

Grade STM-1 STM-4 STM-16

Rate 155.520 Mb/s 622.080 Mb/s 2488.32 Mb/s

Frame length 2430 BYTES 9720 BYTES 38880 BYTES

Frame cycle 125 us 125 us 125 us

1.2.2 Multiplexing Structure and Multiplexing Methods

SDH Working Principle 1-2

F5259_F05 FUNCTIONAL DESCRIPTION

1.2.3 Frame Synchronization and Line Code Type

1.2.4 Overhead Function

SDH Working Principle 1-3

F5259_F05 FUNCTIONAL DESCRIPTION

Administrative Unit pointer(s) B2 B2 D4 D7 D10 S1 B2 K1 D5 D8 D11 K2 D6 D9 D12 M1 E2

SDH Working Principle 1-4

F5259_F05 FUNCTIONAL DESCRIPTION

SDH Working Principle 1-5

F5259_F05 FUNCTIONAL DESCRIPTION

Summary for RSOH/MSOH of STM-1, STM-4, and STM-16

13 25 15 1 29 thru 36 5 thru 12 17 thru 20

49 97 51 1 113 thru 144

SDH Working Principle 1-6

F5259_F05 FUNCTIONAL DESCRIPTION

Bits (5 thru 8) in S1 Byte Timing Source Quality and Grade

SETS: Synchronous Equipment Timing Source

F5259_F05 FUNCTIONAL DESCRIPTION

BIP-8 (B1) STM-1, STM-4,STM-16

BIP-24 (B2) STM-1

BIP-96 (B2) STM-4

BIP-384 (B2) STM-16

After scrambling Regenerator Section

Computing All bits in the previous frame after Range

SDH Working Principle 1-8

F5259_F05 FUNCTIONAL DESCRIPTION

10 Bit Pointer Value