F05 Work PDF

F2880_F05
SpectralWave C-Node
STM-4/ STM-1 Compact Multiplexer
RELEASE 3.20
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 E-mail:mcj@onw.nec.co.jp

F2880_F05
SpectralWave is a registered trademark of NEC Corporation.
Copyright 2002-2004 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 Aug 2004
Printed in China
F2880_F05
CONTENTS
1. SDH WORKING PRINCIPLE 1-1

1.1 Signal Multiplexing Paths ................................................................ 1-1
1.2 Basic Parameters ............................................................................. 1-2
1.2.1 Frame Structure .................................................................................... 1-2
1.2.2 Multiplexing Structure and Multiplexing Methods............................. 1-2
1.2.3 Frame Synchronization and Line Code Type ..................................... 1-3
1.2.4 Overhead Function ............................................................................... 1-3
1.3 Layer 2 Switch Function ................................................................ 1-11

1.3.1 Learning Bridge .................................................................................. 1-11
1.3.2 Broadcast Storm Filtering.................................................................. 1-13
1.3.3 Maximum Frame Size ......................................................................... 1-14
1.3.4 Maximum Bridge Transmit Delay ...................................................... 1-16
1.3.5 Low Queue Delay Bound.................................................................... 1-18
1.3.6 Maximum Queue Delay Time ............................................................. 1-18
1.3.7 VLAN mode.......................................................................................... 1-20
1.3.8 Spanning Tree Protocol ..................................................................... 1-32
1.3.9 Trunk .................................................................................................... 1-44
1.3.10 Port monitor configuration ................................................................ 1-46
1.3.11 MAC filtering........................................................................................ 1-48
1.3.12 Service priority configuration............................................................ 1-53
1.4 Encapsulation and LCAS Function ............................................... 1-55

1.4.1 Encapsulation ..................................................................................... 1-55
1.4.2 LCAS .................................................................................................... 1-57
2. C-NODE WORKING PRINCIPLE 2-1

2.1 Cross connection ............................................................................. 2-1
2.1.1 Matrix structure..................................................................................... 2-1
2.1.2 Cross-connect level.............................................................................. 2-1
2.1.3 Cross-connect type .............................................................................. 2-1
2.1.4 Mix carrier.............................................................................................. 2-3
2.2 Protection.......................................................................................... 2-3

2.2.1 MSP ........................................................................................................ 2-3
Contents
i
F2880_F5
2.2.2 SNCP ...................................................................................................... 2-5
2.3 Synchronization.............................................................................. 2-10

2.3.1 Timing source ..................................................................................... 2-10
2.3.2 Timing source control ........................................................................ 2-10
2.3.3 Timing source selection..................................................................... 2-12
2.4 Trace/signal label function ............................................................ 2-14

2.5 Configuration Management ........................................................... 2-14
2.6 Performance monitor ..................................................................... 2-16
2.6.1 The Definition of PM item................................................................... 2-16
2.6.2 Performance Counter Range ............................................................. 2-22
2.6.3 SES....................................................................................................... 2-25
2.6.4 Suspect condition............................................................................... 2-26
2.6.5 Register management ........................................................................ 2-26
2.6.6 PM reset function................................................................................ 2-26
2.6.7 TCA ...................................................................................................... 2-27
2.7 Fault management .......................................................................... 2-33

2.7.1 Fault monitor items............................................................................. 2-33
2.7.2 Alarm management............................................................................. 2-40
2.7.3 Alarm report ........................................................................................ 2-41
2.8 Security management .................................................................... 2-43

2.9 Maintenance Management ............................................................. 2-47
2.9.1 Loopback ............................................................................................. 2-47
2.10 LOG.................................................................................................. 2-49

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 CID Interface.......................................................................................... 3-2
3.3.2 NMS ........................................................................................................ 3-2
3.4 Physical Specification...................................................................... 3-2

3.4.1 C-Node Subrack Dimensions............................................................... 3-2
Contents
ii
E
F2880_F05
1. SDH WORKING PRINCIPLE
1.1 Signal Multiplexing Paths
Figure 1-1 shows the functional diagram of signal multiplexing paths:
STM-N AUG AU-4 VC-4 C-4 139264kbit/s
TUG-3 TU-3 VC-3
C-3 44736kbit/s
34368kbit/s
TUG-2
Pointer processing
Location and calibration TU-12 VC-12 C-12 2048kbit/s
multiplexing
VC-11 C-11 1544kbit/s
mapping
Figure 1-1. STM-N Signal Multiplexing Paths
SDH Working Principle

1-1
F2880_F05
1.2 Basic Parameters
1.2.1 Frame Structure

Basic frame structure is shown in Figure 1-2.
See alsoTable1-1 for the frame structure parameter of STM-1 and STM-4:
270 N
9N 261 N
1 Segment head
RSOH
3
AU-n pointer
4
9 rows
5 STM-1/4 Payload
Segment head
MSOH
Figure 1-2. Basic Frame Structure
Table1-1. Frame Structure Parameter of STM-1

Grade Rate N Frame length Frame cycle
STM-1 155.520Mb/s 1 2430 BYTES 125us
STM-4 622.080Mb/s 4 9720 BYTES 125us
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
F2880_F05
1.2.3 Frame Synchronization and Line Code Type

1.2.3.1 Frame Synchronization
Frame synchronization bytes A1, A2 are output at STM-1 and STM-4 to sending end
according to frame structure requirement, and at receiving end marks it with A1 and
A2 to aim at. 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. After
OOF lasts 3 ms (24 frames), it should be considered that the system goes into LOF
status (lost of frame). While in the LOF status, the location of A1 and A2 is searched
again, so long as finding these codes, let it as benchmark and check it after a frame.
Counting A1 and A2 of new position, it is considered to have searched frame signal
when continuously counting 2. After 3 ms (24 frames) of in-frame-synchronization
status is held, LOF disappears; otherwise keep searching them again.
1.2.3.2 Line Code Type
z STM-4 optical line interface:

NRZ code after serial scrambling by polynomial 1+X6+X7
z STM-1 optical line interface:

NRZ code after serial scrambling by polynomial 1+X6+X7
z STM-1 electrical line interface: CMI code
z 45M electrical tributary interface: B3ZS code
z 34M electrical tributary interface: HDB3 code
z 2M electrical tributary interface: HDB3 code
z 1.5M electrical tributary interface: B8ZS code
1.2.4 Overhead Function

1.2.4.1 Section Overhead ( SOH )
C-Node supports section and path OH.
The definition of SOH is shown in Figure 1-3 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.

1-3
F2880_F05
9 bytes
A1 A1 A1 A2 A2 A2 J0 * *
B1 E1 F1 RSOH
D1 D2 D3
Administrative Unit pointer(s)
9 rows
B2 B2 B2 K1 K2
D4 D5 D6
D7 D8 D9 MSOH
D10 D11 D12
S1 M1 E2
T1523130-96
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).
STM-1
STM-4
Figure 1-3. SOH of STM-1 and STM-4

1-4
F2880_F05
Table 1-2. Summary for RSOH/MSOH of STM-1 and STM-4
Byte Position (STM-1 frame) Position (STM-4 frame)

Row Byte Row Byte Description
Sequence Sequence Sequence Sequence
A1 1 1,2,3 1 1 thru 12 Frame Location
A2 1 4,5,6 1 13 thru 24 A1: 11110110
A2:00101000
As signal of frame locating
J0 1 7 1 25 Section Trace, STM Identifier
Substitute C1 in new versions suggestion,
encoding to regeneration section
D1 3 1 3 1 DCC (Data Communication Channel)
D2 3 4 3 13
The 192 kbit/s DCC for regenerator section.
D3 3 7 3 25
D4 6, 7, 8 1, 4, 7 6, 7, 8 1, 13, 25 DCC (Data Communication Channel)
thru The 576 kbit/s DCC for multiplex section.
D12 * Not supported in C-Node
E1 2 4 2 13 Orderwire Channel
The 64 kbit/s orderwire channel for
regenerator section; available on VF
communication orderwire channel.
E2 9 7 9 25 Orderwire Channel
The 64 kbit/s orderwire channel for multiplex
section; available on VF communication
orderwire channel.
F1 2 7 2 25 User Channel
The 64 kbit/s clear channel reserved for user
definition.
B1 2 1 2 1 Error Monitor
Detects regenerator section error by BIP-8.
B2 5 1,2,3 Error Monitor on STM-1

Detects multiplex section error by BIP-24.
B2 5 1 thru 12 Error Monitor on STM-4

Detects multiplex section error by BIP-24.
K1 5 4 5 13 APS (Automatic Protection Switching)

K2 5 7 5 25 Used to divert the traffic signal; MS-AIS,
MS-RDI
M1 9 6 9 15 Multiplex Section REI (Remote Error

Indication)
S1 9 1 9 1 Synchronization Status Message
12, 9 8, 9 12, 9 29 thru 36 National uses

* Not supported in C-Node
2, 3 2, 3, 5 2, 3 5 thru 12 Illustrating types of transmission media

17 thru 20 * Not supported in C-Node

1-5
F2880_F05
In it:
z 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.
z K2 Bytes (b6 thru b8):

Multiplex Section Alarm Indicator (MS-AIS), 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.
z S1 Bytes (b5 thru b8):

Synchronization status byte. The 5 thru 8 bits in S1 byte are arranged to indicate
synchronization status message. Table 1-3 gives bits 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 Quality unknown
0001 Reserved
0010 G.811
0011 Reserved
0100 G.812 Transit
0101 Reserved
0110 Reserved
0111 Reserved
1000 G.812 Local
1001 Reserved
1010 Reserved
1011 G.813 (SETS)
1100 Reserved
1101 Reserved
1110 Reserved
1111 Do not use for timing source
SETS: Synchronous Equipment Timing Source

1-6
F2880_F05
z M1 Byte:
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).
BIP operation is listed in Table 1-4:
Table 1-4. BIP Operations
Signal Level BIP-8 (B1) BIP-24 (B2) BIP-96 (B2)
STM-1, STM-4 STM-1 STM-4
Insertion After scrambling Before scrambling Before scrambling
Target Regenerator Section Multiplex Section Multiplex Section
Computing All bits in the Except the first row of Except the first rows of
Range previous frame after SOH in the previous SOH in the previous
scrambling frame, all bits with even frame, all bits with even
parity of every 24 bits, parity of every 96 bits,
after scrambling after scrambling
Processing The receiving system The receiving system The receiving system
Principle at recomputes the recomputes the recomputes the
Reception checksum based upon checksum based upon checksum based upon
the received data for the received data for the received data for
regenerator section, multiplex section, and multiplex section, and
and compares the compares the values. compares the values.
values. Results are Results are transferred Results are transferred
transferred and used and used by the and used by the
by the performance performance performance
monitoring at the monitoring, being a monitoring, being a
far-end. trigger of protection trigger of protection
switching. switching.

1-7
F2880_F05
1.2.4.2 Payload Pointers
Each STM-1 frame includes an AU-4 frame, while each STM-4 frame includes four
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-4:
H1 H2
N N N N S S I D I D I D I D I D
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-4. SDH AU-4 Pointer Coding

1-8
F2880_F05
1.2.4.3 Path Overhead
Besides section overhead (SOH), signal overhead of STM-4 system also contains
VC-4/VC-3 and VC12/VC11 path overhead (POH). See Figure 1-5 below:
J1
B3
C2
G1
F2 260x9/84x9 bytes data payload
H4
F3
K3
N1
Figure 1-5(a). VC-4/VC-3 Path Overhead
V5
J2
N2
K4
Figure 1-5(b). VC-12/VC-11 Path Overhead
The first column of VC-4/VC-3 payload (9 bytes) is dedicated to path overhead

information:
z 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.
z 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

1-9
F2880_F05
B3 byte of the current VC-4 before scrambling.
z 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.
z 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.
z F2, F3 bytes: Path User Channels (Not Supported in C-Node)

These bytes are allocated for end-user communication purpose between path
elements.
z 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).
z K3 byte (b1 thru b4): APS Channel (Not Supported in C-Node)

These bits of K3 byte are allocated for automation protection switching (APS)
signaling for protection at the VC-4 path level.
z N1 byte: Network Operator Byte (Not Supported in C-Node)

This byte is used to provide a Tandem Connection Monitoring (TCM) function.
z Spare K3 (b5 thru b8): (Not Supported in C-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 VC12/VC11 payload is dedicated to path overhead information:
z V5 byte: Low Path Indication
z J2 byte: Low Path Trace
z N2 byte: Network Byte
z K4 byte: Extended Signal Marker

1-10
F2880_F05
1.3 Layer 2 Switch Function

C-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 100Base-T/100Base-T2 subboard. In this section,
these functions are introduced.
1.3.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.
1.3.1.1 MAC Address Learning
As the Figure 1-6 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 which VLAN the data frame is from, then associate the
source address of the received data frame with both receiving port ID and the VLAN
ID whom the port belongs to, and then add it into the MAC Address Table, As the
Figure 1-7 shows (suppose that the data frame belongs to VLAN x).
Figure 1-6
Figure 1-7

1-11
F2880_F05
The switch chip forwards the data frame according to the internal MAC Address
Table, the corresponding forwarding mechanism shows as below:
If the MAC address SA is already in the MAC Address Table (as Figure 1-7
shows), when the ports (except Port1) which belongs to VLANx received the data
frame with destination MAC address SA (the data frame also belongs to VLANx),the
switch chip would forward the data frame to the Port1 only. If Port1 received the data
frame with destination MAC address SA, the switch chip would discard it on Port1,
which is commonly said the filtering function of switch. If there is not the MAC
address SA 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.
1.3.1.2 MAC Address Ageing
The switch chips MAC Address Ageing Interval can be set as No Ageing or N
seconds (In C-Node, N=300~765 seconds, and step=1 second). If set as No Ageing,
the switch chip wouldnt age the MAC address in the MAC address table
automatically.
As Figure 1-7 shows, if that the MAC Address Ageing Interval is set as N seconds,
within N seconds, when the Port1 doesnt receive the data packet with the source
address SA again, the MAC address entry of SA would be deleted from the MAC
address table automatically; If the MAC Address Ageing Interval is set as No
Ageing mode, although the Port1 doesnt receive the data packet with the source
address SA in long time, the MAC address will be kept in the MAC address table.
NOTE:
1. When MAC Address Ageing Interval is set as No Ageing mode, the record of
MAC address in the MAC address table of the switch chip will be deleted only in
below cases:
1> The MAC address number in the MAC address table is up to the maximum
capacity(in one 100Base_T or 100Base_T2 unit, the maximum capacity is
10239),in this situation, the oldest MAC address entry will be deleted, and
the newest MAC address will be added to the MAC address table;
2> When the switch chip resets, or STP topology is changed or the Ethernet port
is changed.
2. When MAC Address Ageing Interval is set as N seconds, the timer for the MAC
Address Ageing Interval is not very accurate, and the actual value may deviate
from the configured value.

1-12
F2880_F05
1.3.2 Broadcast Storm Filtering
1.3.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 flow, increase the
effective network bandwidth. The broadcast filter function is effective under the
following two situations:
1. The broadcast frame flow in the switch chip exceeds the configured threshold.
The threshold configured is the ratio between the data flow of the broadcast
frame and the overall data flow in the internal buffer of the switch chip.
2. Input data rate exceeds that via the output port.
As Figure 1-8 shows, suppose the all ports in layer 2 switch can work as 100Mb/s,if
Port1 in the switch chip receives two kinds of frame: F1 whose data flow is 15MBit/s
and DA1 is broadcast destination MAC address FF-FF-FF-FF-FF-FF, and F2
whose data flow is 94MBit/ and DA2 is non-broadcast destination MAC address; At
the same time, the other port receive the data frame Fx with total data flow
100MBit/s and non-broadcast destination MAC address DAx. In this case, in the
buffer of the switch chip, the proportion of the broadcast data flow to the total is
15/200=7.5%, when threshold of the Broadcast Storm Filtering is 5%, the switch
chip would ensure the buffer used by the broadcast data is not more than 5% by
discarding the redundant broadcast data frames of F1, hence relaxed the broadcast
data flow of F1 via output port, and decreased the bandwidth occupied by the
broadcast data frame.
Figure 1-8

1-13
F2880_F05
1.3.2.2 Configuration
As the Figure 1-9 shows below, Broadcast Storm Filtering parameter has 6 choices:
0,5%,10%,15%,20%,25%.Choose the required parameter, and then click the button
Set.
Figure 1-9
1.3.2.2.1 Parameter 0
Means disable Broadcast Storm Filtering function.
1.3.2.2.2 Parameter x%
Set Broadcast Storm Filtering threshold which is the ratio between data flow of the
broadcast frame and the overall data flow in the internal buffer of the switch chip.
The greater the x% is, the greater the proportion of the broadcast frames to the
overall capacity of the buffer.
1.3.3 Maximum Frame Size
Maximum Frame Size is used for setting the maximum length of the Ethernet frame
passed through the FE unit, the Ethernet data frame whose length is greater than the
configured would be discarded.

1-14
F2880_F05
Figure 1-10
As the Figure 1-10 shows, fill the maximum Ethernet frame length required in the
right area of the maximum Frame Size, and then click the button Set.
The configured parameter ranges from 1522 to 1568, pay attention to the maximum
length of the Ethernet frame including the VLAN Tag, i.e. for the FE unit with
Maximum Frame Size N:
1. It would be discarded when the data frame with VLAN Tag is received and its
length is greater than N.
2. It would be discarded when the data frame without VLAN Tag is received and
its length is greater than N-4.
As the Figure 1-11 shows, F1 frame has VLAN Tag, F2 frame doesnt have, when
Maximum Frame Size is set as N, the F1 would be discarded if the length of the F1
frame is more than N, otherwise, F1 would be passed to the egress port of the L2SW;
the F2 would be discarded if the length of the F2 frame is more than N-4, otherwise,
the F2 would be passed to the egress port of the L2SW.

1-15
F2880_F05
Figure 1-11
1.3.4 Maximum Bridge Transmit Delay
Maximum Bridge Transmit Delay is used for setting the maximum time of the data
frame buffered by the switch, when the time delayed for the data frame in the switch
is greater than Maximum Bridge Transmit Delay, it would be discarded.
As the Figure 1-12 shows, there is such a situation in the practical application: for
example, the ingresss bandwidth is more than egresss, the frame Fx in the L2SW
cant be sent from the egress queues to egress port in timely. If Maximum Bridge
Transmit Delay is configured as X (x=1,2,4), and the Fx in the L2SW egress
queue cant be sent to egress port in X seconds, the Fx would be discarded; if
Maximum Bridge Transmit Delay is configured as Disable, the Fx would not be
discarded even if its delay time is too long in buffer.
Figure 1-12

1-16
F2880_F05
As the Figure 1-13 shows, Broadcast Storm Filtering parameter has 4 choices,
Disable,1,2,4.Choose the time to be configured, then click the button Set, the
configuration is based on the service the customer is using, if the service is not
sensitive for the time delay, for example: file transferring etc, the function would be
closed by the internal buffer of the switch chip, it can increase the forward capacity
of flatting burst flow in FE unit as possible, if the service is sensitive for the time
delay, the function should be enabled to avoid affecting quality of service.
Figure 1-13
1.3.4.2 Configuration Parameter
Disable means close Maximum Bridge Transmit Delay function, the delayed data
frame will be kept in the buffer of the switch chip, not be discarded as the time is
delayed.
x means how long the data frame is kept in the internal buffer of the switch chip, it
will be discarded if the configured time is over.

1-17
F2880_F05
1.3.5 Low Queue Delay Bound
Low Queue Delay Bound is used for enabling the setting of the low queue delay time.
When it is set as Enable, Maximum Queue Delay Time configuration is effective;
otherwise, it is not.
Figure 1-14
1.3.6 Maximum Queue Delay Time
Maximum Queue Delay Time is used for setting the maximum time of the data frame
buffered in the low priority queue, when the data frame in low priority queue in the
switch stays over the configured Maximum Queue Delay Time, it will be discarded.
As the Figure 1-15 shows, there is such a situation in the practical application: for
example, the ingresss bandwidth is more than egresss, the frame Fx in the L2SW
cant be sent from the low egress queues to egress port in timely. If Maximum
Queue Delay Time is configured as X (x=2 - 510ms), and the Fx in the L2SW
egress queue cant be sent to egress port in X milliseconds, the Fx would be
discarded; if Maximum Bridge Transmit Delay or Low Queue Delay Bound is
configured as Disable, the Fx would not be discarded even its delay time is too
long in buffer.

1-18
F2880_F05
Figure 1-15
As the Figure 1-16 shows below, fill the maximum delay required in the parameter
area Maximum Queue Delay Time, and then click button set.
1.3.6.2 Configured Parameter
The configured parameter ranges from 2 to 510, the configured parameter means how
long the data frame with low priority in the internal buffer of the switch chip is kept,
the data frame whose buffered time is greater than the configured time is discarde

1-19
F2880_F05
Figure 1-16
NOTE: The configuration is valid only when enable both Maximum Bridge Transmit
Delay and Low Queue Delay Bound
1.3.7 VLAN mode

The FE interface unit of the C-node equipment provides two kinds of VLAN mode:
Port based mode and IEEE 802.1Q mode.
Figure 1-17

1-20
F2880_F05
1.3.7.1 Port Based VLAN
1.3.7.1.1 Port Based VLAN overview

As the Figure 1-17 shows above, in the VLAN Mode interface, Choose the item
Port based from the pull-down menu VLAN Operation Mode, then click
button set.
Port Based VLAN mode is a process mechanism based on the physical port, which
makes VLAN divided by Port ID not VLAN Tag, hence specially suits for
transparent transmission of Ethernet layer 2 data frame without occupying
VLAN Tag resource. That is to say, in Port Based VLAN, the Ethernet frame will
be transparently forward from ingress port to egress port of L2SW without caring
the VLAN Tag. Both VLAN1 and VLAN2 can use same VLAN Tag repeatedly,
but the two VLANs are separated completely by the physical port. As the Figure
1-18 shows below:
Figure 1-18
1.3.7.1.2 Port Based VLAN process mechanism
Switch chips process mechanism for the data frame shows as below on Port
Based VLAN mode:

1-21
F2880_F05
Table 1-5 Process Mechanism for Port Based VLAN
Port Configuration Frame on Ingress Direction( Figure 1-19 ) Frame on Egress Direction( Figure 1-19 )
Tagged/ In Filter Tagged Frame Untagged Priority Tagged Priority Tagged Tagged Frame Tagged Frame Untagged Priority Priority Tagged Tagged Tagged Frame
Untagged Setting (VID=1) Frame Frame Frame (VID=1) Frame Tagged Frame Frame Frame with
(VID is 0) (VID is not 0) (VID is 0) (VID is not 0) PVID
N/A N/A Transparent Transparent Transparent Transparent Transparent Transparent Transparent Transparent Transparent N/A Transparent
Figure 1-19

1-22
F2880_F05
1.3.7.2 IEEE 802.1Q VLAN
1.3.7.2.1 IEEE 802.1Q VLAN overview
In the VLAN Mode interface, Choose item IEEE 802.1Q from the pull-down
menu VLAN Operation Mode, then click button set.
IEEE 802.1Q VLAN is a process mechanism based on VLAN Tag, Which makes
VLAN divided according to the VLAN Tag, makes VLAN separated and
processed for all Ethernet data frames whose Tag ranges from 0 to 4095, 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.
1.3.7.2.2 IEEE 802.1Q VLAN process mechanism
Switch chips process mechanism for the data frame shows as below on IEEE
802.1Q VLAN mode:

1-23
F2880_F05
Table 1-6 Process Mechanism for IEEE802.1Q VLAN
Port Configuration Frame on Ingress Direction(Figure 1-19) Frame on Egress Direction(Figure 1-19)
Tagged/ In Filter Tagged Untagged Priority Priority Tagged Tagged Frame Tagged Frame Untagged Priority Tagged Priority Tagged Tagged Frame with Tagged Frame
Untagged Setting Frame Frame Tagged Frame Frame (VID=1) Frame Frame Frame PVID
(VID=1) (VID is 0) (VID is not 0) (VID is 0) (VID is not 0)
Not Forward Pass add VLAN tag change VID to Discard Frame with Discard Frame with Remove VID1 and N/A N/A Remove VID and Remove VID and Remove VID
Configured Match VID through with Port Port VID=1 undefined VID other undefined VID forward frame to forward only frame forward only frame and forward only
VID=1 than VID=1 other than VID=1 egress direction with VID=1 that with VID=1 that frame with VID=1
configured by FW configured by FW that configured
acquiescently acquiescently by FW
acquiescently
Drop Pass Discard Discard Forward only VID=1 Forward only VID=1
Untagged through
Frame
Enable All Pass Discard Discard Discard Frame with Discard Frame with
through undefined VID other undefined VID
than VID=1 other than VID=1
Disable All Pass add VLAN tag change VID to Forward only VID=1 Forward only VID=1
through with Port Port VID=1
VID=1
Untagged Forward Discard add VLAN tag change VID to Discard undefined Discard undefined Discard N/A N/A Remove and Remove and Remove and
IF VID=x Match VID with Port Port VID=x VID Frame VID Frame forward only forward only forward only
VID=x Forward only Forward only configured VID configured VID configured VID
configured VID frame configured VID frame frame frame
frame
Drop Pass Discard Discard Forward only Forward only

Untagged through configured VID frame configured VID
Frame frame
( Next Page Continued )

1-24
F2880_F05
Port Configuration Frame on Ingress Direction(Figure 1-19) Frame on Egress Direction(Figure 1-19)
Tagged/ In Filter Tagged Untagged Priority Priority Tagged Tagged Frame Tagged Frame Untagged Priority Tagged Priority Tagged Tagged Frame with Tagged Frame
Untagged Setting Frame Frame Tagged Frame Frame (VID=1) Frame Frame Frame PVID
(VID=1) (VID is 0) (VID is not 0) (VID is 0) (VID is not 0)
Untagged Enable All Discard Discard Discard Discard undefined Discard undefined Discard N/A N/A Remove and Remove and Remove and
IF VID=x VID Frame VID Frame forward only forward only forward only
Forward only Forward only configured VID configured VID configured VID
configured VID frame configured VID frame frame frame
frame
Disable All Pass add VLAN tag change VID to Forward only Forward only
through with Port Port VID=x configured VID frame configured VID
VID=x frame
Tagged Forward Pass add VLAN tag change VID to Discard undefined Discard undefined Remove VID1 and N/A N/A forward only forward only forward only
Match VID through with Port Port VID=1 VID Frame VID Frame forward frame to configured VID configured VID configured VID
VID=1 Forward only Forward only egress direction frame frame frame
configured VID frame configured VID
frame
Drop Pass Discard Discard Forward only Forward only

Untagged through configured VID frame configured VID
Frame frame
Enable All Pass Discard Discard Discard undefined Discard undefined

through VID Frame VID Frame
Forward only Forward only
configured VID frame configured VID
frame
Disable All Pass add VLAN tag change VID to Forward only Forward only
through with Port Port VID=1 configured VID frame configured VID
VID=1 frame

1-25
F2880_F05
1.3.7.2.3 IEEE 802.1Q VLAN instance
1. About default VLAN

When we set IEEE802.1Q VLAN, there has a default VLAN in the bridge
defined by FW. Please see the Figure 1-20 below.
Figure 1-20
Then if we set a VLAN with Untagged setting in some ports, these ports will
be removed from default VLAN; And other ports with Tagged setting also
belongs default VLAN. Please see the Figure 1-21 below.
Figure 1-21
VLAN Setting: LAN1-a-U, WAN1-a-T
2. About IEEE802.1Q VLAN
Figure 1-22
VLAN Setting:
LAN1-a-U, WAN1-a-U

1-26
F2880_F05
LAN2-b-U, WAN2-b-T
LAN3-c-T, WAN3-c-T
LAN4-d-T, WAN4-d-U
LAN4-e-U
Then there are six VLANs in bridge include default VLAN.
3. Port Filtering Application Instances
3.1 Untagged Frame processing cases
3.1.1 Ingress Filter: Disable All or Forward Match VID on all ports
Figure 1-23
NOTE: UF means Untagged Frame, and TFx means Tagged Frame with
VID x(here x represents character a,b,c, etc.).
Shows in Figure 1-23 on above,
If a untagged frame received from LAN1, this frame is added a VID a at
ingress direction, then forwards to WAN1 only and removed VID on egress
direction.
If a untagged frame received from LAN2, this frame is added a VID b at
ingress direction, then forwards to WAN2 only and do not remove VID on
egress direction.
3.1.2 Ingress Filter: Enable All or Drop Untagged Frame on all ports
Figure 1-24
If a untagged frame received from LAN1, this frame will be dropped by ingress

1-27
F2880_F05
filter on LAN1;
If a untagged frame received from LAN2, this frame will be dropped by ingress
filter on LAN2.
Figure 1-25
Shows in Figure 1-25 on above, If a untagged frame received from LAN3, this
frame belongs VLAN1(Default VLAN),so it is added a VID 1 at ingress
direction, then forwards to WAN2 and WAN3 only and removed VID on egress
direction.
Figure 1-26
Shows in Figure 1-26 on above, if a untagged frame received from LAN3, this
frame will be dropped by ingress filter on LAN3.
Figure 1-27
frame belongs VLANe, so it is added a VID e at ingress direction, and then
dropped on egress direction.

1-28
F2880_F05
Figure 1-28
frame will be dropped by ingress filter on LAN4.
3.2 Tagged Frame processing cases
3.2.1 Ingress Filter: Disable All or Drop Untagged Frame or Enable All or
Forward Match VID on all ports
Figure 1-29
If a tagged frame(VID=a) received from LAN1, this frame belongs VLANa, so
it will forward to WAN1 only and removed VID on egress direction;
If a tagged frame(VID=b) received from LAN2, this frame belongs VLANb, so
it will forward to WAN2 only and does not removed VID on egress direction;
If a tagged frame(VID=c) received from LAN3, this frame belongs VLANc, so
it will forward to WAN3 only and does not removed VID on egress direction;
If a tagged frame(VID=d) received from LAN4, this frame belongs VLANd, so
it will forward to WAN4 only and removed VID on egress direction.
3.2.2 Ingress Filter: Disable All or Drop Untagged Frame or Enable All or
Forward Match VID on all ports

1-29
F2880_F05
Figure 1-30
Shows in Figure 1-30 on above, If a tagged frame(VID=e) received from LAN4,
this frame belongs VLANe, so it is dropped on egress direction.
3.2.3 Ingress Filter: Disable All or Drop Untagged Frame on all ports
Figure 1-31
If a tagged frame(VID=b) received from LAN1, this frame belongs VLANb, so
it will forward to WAN2 and LAN2 only and removed VID on LAN2, do not
removed VID on WAN2;
If a tagged frame (VID=e) received from LAN3, this frame belongs VLANe, so
it will forward to LAN4 only and removed VID on egress direction.
3.2.4 Ingress Filter: Enable All or Forward Match VID on all ports
Figure 1-32
Shows in Figure 1-32 on top,
If a tagged frame (VID=b) received from LAN1, this frame will be dropped by
ingress filter on LAN1;
If a tagged frame (VID=e) received from LAN3, this frame will be dropped by
ingress filter on LAN3.

1-30
F2880_F05
3.2.5 Ingress Filter: Disable All or Drop Untagged Frame on all ports
Figure 1-33
If a tagged frame(Not configured VID:xa,b,c,d,e,1) received from LAN1, this
frame will be dropped;
If a tagged frame(Not configured VID:xa,b,c,d,,e,1) received from LAN4,
this frame will be dropped.
3.2.6 Ingress Filter: Enable All or Forward Match VID on all ports
Figure 1-34
If a tagged frame(Not configured VID in this port:xa) received from LAN1,
this frame will be dropped by ingress filter on LAN1;
If a tagged frame(Not configured VID in this port:xb) received from LAN2,
If a tagged frame(Not configured VID in this port:xc,1) received from LAN3,
If a tagged frame(Not configured VID in this port:xd,e) received from LAN4,
this frame will be dropped by ingress filter on LAN4.

1-31
F2880_F05
1.3.8 Spanning Tree Protocol
1.3.8.1 STP Configuration
STP (Spanning Tree Algorithm and Protocol) is used for keeping Ethernet service
away from ring, at the same time protect service by redundant capacity, we will
introduce the STP function configuration chiefly as below:
1.3.8.2 STP protocol configuration
STP Config page in Layer 2 Configuration menu is used for setting STP protocol
parameter and querying corresponding information on STP protocol, the
configuration interface shows as below:
Figure 1-35
The items to be configured:
1. STP Action
Used for enable STP protocol. Default is Enable.
2. Bridge Hello Time
The time interval of BPDU configuration sent by root network bridge. Range
from 1s to 10s, default is 2s.
NOTE: BPDU means the Bridge Protocol Data Unit.
3. Bridge Forward Delay Time

1-32
F2880_F05
Learning and Listening time used by STP port. When port status changes from
blocking to forwarding, both Listening and Learning status need to be passed.
Range from 4s to 30s, default is 15s.
4. Bridge Max Age
Maximum survived time of BPDU information. When the time is over, BPDU
information would be discarded if not updated. Range from 6s to 40s, default is
20s.
5. Bridge Priority
Bridge Priority is part of Bridge ID, Bridge ID identify root Network Bridge.
Smaller the configuration value of Bridge Priority, higher the priority. Range
from 0 to 65535, default is 32768.
The items to be queried:
The corresponding STP protocol information located at the left of STP Config is
listed as 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 current protocols standard. The current is IEEE802.1D changelessly.
7. Bridge Address
Network Bridges MAC address. Be fixed in the factory. Each network bridge
has exclusive designated address. The address is part of Bridge ID, identify the
network bridge exclusively.
8. Root Bridge ID

1-33
F2880_F05
The ID of current root Network Bridge, it is made of both Bridge Priority and
Bridge Address.
Each network bridge has exclusive designated 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.
1.3.8.3 STP port configuration
STP Port page in Layer 2 Configuration menu is used for setting STP protocol
parameter and querying corresponding information on STP protocol, configuration
interface shows as below:
Figure 1-36
The items to be configured and queried:
1. STP Control
Enable the ports STP protocol. The port with disable attribution will not deal
with any BPDU and not relate with any STP action. Default on LAN port is
Disable, default on WAN port is Enable.
2. Link Cost
Used for designate the ports link cost. Range from 0 to 255, default is 128.
3. Port Priority

1-34
F2880_F05
Both the port priority and the No. of the port form the port ID, Each port of the
network bridge has exclusive port ID. the smaller the configured, the higher the
priority. Range from 0 to 255. the default is 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 configured as disable, Port Status has two
statuses: forwarding and disabled, which ruled by STP algorithm.
1.3.8.4 STP basic principle
Once spanning Tree Algorithm and Protocol has been carried out, the dynamic
tree topologic structure will be formed, it makes the loop among any two NEs not
exist, hence avoid the broadcast storm by the loop. At the same time, the spanning
Tree Algorithm monitor the change of the physical topological structure, can
create new spanning Tree before change of the topological structure, and carry out
service protection.
1.3.8.5 Principal and algorithm
1. The term definition:
Root bridge: the bridge with 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 lowest root link cost in the bridge, if one more port
has same root link cost, the one with highest priority is root port.
Designated bridge: the bridge with the lowest root link cost in the network
Designated port: the designated port means the port between the network and
designated bridge, if two more ports are online, the one with highest
priority is designated port.
The ports status is ruled by spanning tree algorithm, which include five
statuses: forwarding, learning, listening, blocking and disable.

1-35
F2880_F05
2. The spanning tree algorithm is based on the following:
The exclusive group address identifies all bridges in a specific network,

which can be identified by all bridges.
Each bridge has a exclusive bridge identifier:
Each bridges port has a exclusive port identifier
3. The configuration management for the spanning tree require:
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; exchange the spanning
tree configuration information to be able to respond the change of network
topology, cost or priority quickly.
BPDU has two kinds, the configuration BPDU which covers configuration
information, and the topology change notification BPDU which is sent when
the topology structure change. The coding of both the change notification
BPDU and the configuration BPDU show as the two figures below:
(Change notification BPDU)

1-36
F2880_F05
(Configuration BPDU)
5. The necessary key elements to form a spanning tree:
Decide root bridge
a. At the beginning, all bridges think itself as root bridge;
b. The bridge sends the configuration BPDU with same root id and bridge id to
the network connected.
c. The frame is discarded if the value of root id is greater than the one in the
bridge when the bridge receive the configuration BPDU from another bridge,
otherwise, update the parameter such as bridges root id, root link cost, the
bridge will send broadcast configuration BPDU with new value continually.
Decide root port
The port with lowest root link cost in a bridge is called root port. The port

1-37
F2880_F05
with highest priority is called root port if some ports have same lowest root
link cost. The port with lowest port number is called root port if two or more
port has same lowest root link cost and highest priority.
Decide networks designated bridge
a. At the beginning, all bridges think itself 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, two or more bridges have the same root link cost,
the bridge with highest priority is thought as designated bridge, other bridges
port connected with root is set as block status.
c. If the designated bridge receives a configuration BPDU from other bridge in
the specific time as other bridge compete designated bridge. The designated
bridge sends a response configuration BPDU to decide designated bridge
again.
Decide designated port
The designated port is the one connected with this network in the designated
bridge. If designated bridge has two or more port connected with this network,
the one with lowest ID is designated port. Except root port and designated
port, other port will be set as block status. So, a spanning trees topology
structure has been decided when the root bridge, the bridges root port, as
well as each networks designated bridge and designated port are decided.
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 monitor the time of this information buffered. In
both normal and stable status, root bridge sends configuration message to
ensure the topology information 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 detect 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

1-38
F2880_F05
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 change 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 message, 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 created again.
1.3.8.6 STP application instance
Take the Figure 1-37 as an example to show what need to pay attention to 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)

1-39
F2880_F05
Figure 1-37
1.3.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 field 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 1-37 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 1-38

1-40
F2880_F05
1.3.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 1-39
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

1-41
F2880_F05
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 C-Node equipment, it is out of protection.
1.3.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 1-40 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 flow. 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.

1-42
F2880_F05
Figure 1-40
1.3.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. Bridge Max Age >= 4*Bridge Hello Time + 2*Maximum Bridge Diameter -
2
2. Bridge Forward Delay >= (4*Bridge Hello Time + 3*Maximum Bridge

Diameter)/2
Maximum Bridge Diameter means maximum network diameter.
Take the Figure 1-40 as instance, there are 10 NEs in the Ethernet ring, the
network diameter is 9, when Bridge Hello Time is set as 2s:
1. Bridge Max Age >= 24
2. 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.

1-43
F2880_F05
1.3.9 Trunk
Trunk function is called as link aggregation in other word.
Figure 1-41
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 the Figure 1-41, 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.
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-44
F2880_F05
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 1-42 below.
Figure 1-42
the maximum effective bandwidth is: 2*21*vc1242*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 1-43 below.
Figure 1-43
the maximum effective bandwidth is: 42*vc12+21*vc1263*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
100Base-T/100Base-T2 subboard of C-Node because frame distribution algorithm

1-45
F2880_F05
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 1-44 is CIDs Trunk function
interface. Its used to set Trunk parameters.
Figure 1-44. Trunk Function Interface
1.3.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:
1.3.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:

1-46
F2880_F05
Figure 1-45
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 LAN4.
3. Monitored Port
Configure the port monitored. Ranges from LAN1 to LAN4 or from WAN1 to
WAN4

1-47
F2880_F05
1.3.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 1-46
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.
1.3.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.

1-48
F2880_F05
In NE management dialog Box, Select LAN-InterfaceLayer 2

Configuration Mac Table, the popup window Figure 1-47 is CIDs Mac
Filtering function interface. Its used to set Mac filtering parameters.
Figure 1-47. Mac Filtering Function Interface
The MAC Table configuration is shown as the Figure 1-48, and the Figure 1-49
shows the mechanism of the data frame A with the destination address
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.

1-49
F2880_F05
Figure 1-48
Figure 1-49
The MAC table configuration is shown as the Figure 1-50, the Figure 1-51 shows
the mechanism of the data frame A with the destination address 00-00-00-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.

1-50
F2880_F05
Figure 1-50
Figure 1-51
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 1-52

1-51
F2880_F05
1. When Security is disabled:
Frame with Destination Address PORT ACTION (SECURITY = DISABLE)
LAN#1 PORT WAN#1 PORT
Forward Discard Forward Discard

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

00:00:00:00:00:01 00:00:00:00:00:01 00:00:00:00:00:01 00:00:00:00:00:01
Input MAC:00-00-00-00-00-01 Discard Discard
Other MAC address Discard(Note3) Discard
Output MAC:00-00-00-00-00-01 Forward Discard
Other MAC address Forward Forward
NOTE:
1) Input and Output directions are based on L2SW (Layer 2 Switch).
2) Meaning of three results is shown below:
Forward Forward the frame only to the port which the MAC address be set in MAC table.
Forward Forward the frame on the port.
Discard 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.

1-52
F2880_F05
1.3.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:
1.3.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 1-53
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
The weight of high priority service queue under WRR queue mode. A range from
1 to 7, default is 1.
3. WRR Low Weight
The weight of low priority queue under WRR queue mode. A range from 1 to 7,
default is 1.
4. User Priority
Configure the frame with user priority to process as high or low priority in the

1-53
F2880_F05
bridge of C-Node FE unit. The frame with user priority has 8 types priority
from 0 to 7, which is carried in "VLAN Header" field of the frame. C-Node FE
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 C-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.
Each L2SW chip on the FE unit 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 1-54
First comes first serves (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 priority(WRR)
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.

1-54
F2880_F05
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.
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.
1.4 Encapsulation and LCAS Function

C-Node can accommodate Encapsulation and LCAS function by using 100Base-T/
100Base-T2 subboard. In this section, these functions are introduced.
1.4.1 Encapsulation
C-Node supports two kinds of encapsulations: GFP and LAPS.
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-codeoriented constant bit rate stream (such as Fiber Channel or
ESCON/SBCON). Currently, two modes of client signal adaptation are defined for GFP.
GFP uses a variation of the HEC-based frame delineation mechanism defined for
Asynchronous Transfer Mode (ATM) (see ITU-T Rec. I.432.1). Two kinds of GFP
frames are defined: GFP client frames and GFP control frames. GFP also supports a
flexible (payload) header extension mechanism to facilitate the adaptation of GFP for use
with diverse transport mechanisms. For Ethernet over GFP, there is a one-to-one mapping
between a higher-layer PDU and a GFP PDU. Specifically, the boundaries of the GFP
PDU are aligned with boundaries of the framed higher layer PDUs.

1-55
F2880_F05
LAPS describes an HDLC-like framing structure to encapsulate IEEE 802.3 Ethernet

MAC frame, provide a point-to-point full-duplex simultaneous bidirectional operation.
For Ethernet over LAPS, 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 default maximum frame size of LAPS shall be
capable of supporting an information field of 1600 octets (at least) for Ethernet over
LAPS.
NOTE: The difference between LAPS and GFP-F are shown as bellow:
Item LAPS GFP-F

frame delineation Use special octet7E for GFP frame delineation is
LAPS frame delineation, the performed based on the
starting octet and ending correlation between the first
octet of the LAPS frame is two octets of the GFP
7E frame and the embedded
two-octet cHEC field.
scrambling x43 + 1 x43 + 1
/descrambling
FCS CRC-32 CRC-32 selected by CID
0x7e -> 0x7d, 0x5e;0x7d -> Normal
Payload Process
0x7d, 0x5d;
Inter-Frame-Gap Fill octet 7E GFP idle Frame
Protocol coverage Point to Point Point to Point, Linear,Ring
The utilization ratio of the The utilization ratio of the
bandwidth would be bandwidth doesn't connect
decreased if the Ethernet with the Ethernet data; it
data include 0x7e or would not be decreased
Bandwidth
0x7d,the available bandwidth because some special data is
would be half especially if transmitted.
the Ethernet data is all 0x7e
or 0x7d.
Narrow application, only very Widely applied over the
few users are using. The world. GFP is recommended
internetworking of the when the internetworking of
equipments may have the equipments is required, if
Compatibility
problems because the the equipment manufacturers
equipment manufacturers have passed the
haven't passed the internetworking test strictly.
internetworking test.
In NE management dialog Box, Select LAN-Interface Encapsulation Configuration,

the popup window Figure 1-55 is CIDs Encapsulation Configuration and LCAS
function interface. Its used to set Encapsulation configuration and LCAS function.

1-56
F2880_F05
Figure 1-55. Encapsulation Configuration and LCAS Function Interface
1.4.2 LCAS
Link capacity adjustment scheme (LCAS) is used to increase or decrease the capacity of a
container that is transported in an SDH/OTN network using Virtual Concatenation. In
addition, it will automatically decrease the capacity if a member experiences a failure in
the network, and increase the capacity when the network fault is repaired. The scheme is
applicable to every member of the Virtual Concatenation group.
LCAS defines the required states at the source and at the sink side of the link as well as
the control information exchanged between both the source and the sink side of the link
to enable the flexible resizing of this Virtual Concatenated signal. The LCAS assumes
that in cases of capacity initiation, increase or decrease, the construction or destruction of
the end-to-end path of each individual member is the responsibility of the Network and
Element Management Systems.
In NE management dialog Box, Select LAN-Interface Encapsulation Configuration,

the popup window Figure 1-55 is CIDs Encapsulation Configuration and LCAS
function interface. Its used to set Encapsulation configuration and LCAS function.

1-57
E
This page is intentionally left blank
F2880_F05
2. C-NODE WORKING PRINCIPLE
2.1 Cross connection
2.1.1 Matrix structure

Table 2-1. Matrix Structure
Cross-connect level Size
VC-4 16*16 (8*8 in mini 155M version)
VC-3 48*48 (24*24 in mini 155M version )
VC-12 1008*1008 (504*504 in mini 155M version)
2.1.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
Interface Unit Cross-connect level
STM-4 VC-4 / 3 / 12
STM-1o/STM-1e VC-4 / 3 / 12
45M VC-3
34M VC-3
2M VC-12
1.5M VC-12
100Base-T/100Base-T2 VC-12m/3n/4k
NOTE: m=1-63, n=1-3, k=1
2.1.3 Cross-connect type

C-Node supports the following cross-connect type: one way, two way, loopback.
2.1.3.1 One way
z LXC (Local Cross-Connect)
A B
C-Node Working Principle

2-1
F2880_F05
z PPS (Path Protection Selector)
Drop and continue
z Broadcast
2.1.3.2 Two way
z LXC (Local Cross-Connect)
z PPS (Path Protection Selector)
2.1.3.3 Loopback

2-2
F2880_F05
2.1.4 Mix carrier

The equipment can carry mixed VC-3 and VC-12 signal in one VC-4.
VC-4
A B VC-3
VC-3 VC-12
2.2 Protection
C-Node supports two kinds of protections: MSP (multiplex section protection) and
SNCP (sub-network connection protection).
2.2.1 MSP
2.2.1.1 Action mode
C-Node supports MSP in action mode: 1+1 Uni-directional Non-revertive Linear

Protection. The following illustration shows 1+1 Unidirectional Linear Protection
Operation. Only receive side is switched by line failure.
Figure 2-1. 1+1 Unidirectional Linear Protection Operation

2-3
F2880_F05
Following tables show some kinds of MSP settings.
Case1: primary/backup ports on Mainboard
Mainboard Aggregate Tributary:2M/1.5M/34M/45M/STM-1o(e)

Mainboard slot1 slot2 slot3 slot4
slot1 slot3 STM-4oD OK OK OK OK
slot2 slot4 STM-1o(e)D OK OK OK OK
Red line means MSP setting.
Case2: primary/backup ports on same subboard. Mainboard does not use.
Aggregate Tributary:2M/1.5M/34M/45M/STM-1o(e)
Mainboard Mainboard slot1 slot2 slot3 slot4
STM-N slot3 STM-1o(e)D OK OK OK
slot2 slot4 STM-1o(e)D OK OK OK
Red line means MSP setting. STM-1o(e)D OK OK OK
STM-1o(e)D OK OK OK
STM-N subboard in different slot
2.2.1.2 switching criterion
Switching
Item requirement Monitor place
B2ERR_HIGH SF Line (Work / Prot)
B2ERR_LOW SD Line (Work / Prot)
LOS SF Line (Work / Prot)
LOF SF Line (Work / Prot)
MS-AIS SF Line (Work / Prot)
RS-TIM* SF Line (Work / Prot)
*: J Byte must be enabled in order to make TIM function be a switch criterion.

2-4
F2880_F05
2.2.1.3 External Commands
Command Term Content

Lockout of LKOP Protection line is forbidden to use unconditionally.
protection
Lockout of working LKOW Working line is forbidden to use unconditionally.
Forced switch to FSP If the command is set on working line, the traffic will be
protection switched to protection line unconditionally.
Forced switch to FSW If the command is set on protection line, the traffic will be
working switched to working line unconditionally.
Manual switch to MSP If the command is set on working line and protection line is in
protection normal status, the traffic will be switched to protection line.
Manual switch to MSW If the command is set on protection line and working liner is in
working normal status, the traffic will be switched to the working line.
2.2.1.4 Command priority
LKOP>LKOW>FSW>FSP>SF on Prot>SF on Work>SD on Prot>SD on Work>

MSW>MSP
2.2.1.5 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.2.2 SNCP
2.2.2.1 Action mode
C-Node supports SNCP in action methods: 1+1 Uni-directional Non-Revertive/

Revertive and monitor methods: SNC/I (Sub-Network Connection Protection with
Inherent Monitoring) and SNC/N (Sub-Network Connection Protection with
Non-intrusive Monitoring).
NOTE: C-Node supports both SNC/N and SNC/I in SNCP ring configuration,
according to the following table.

2-5
F2880_F05
Subboard 504*504 cross-connect module 1008*1008 cross-connect module
Slot 1 Slot 2 Slot 3 Slot 4 Slot 1 Slot 2 Slot 3 Slot 4
8 * E12(2M) SNC/N SNC/N SNC/I SNC/I SNC/N SNC/N SNC/N SNC/N
32 * E12(2M) SNC/N SNC/N SNC/I SNC/I SNC/N SNC/N SNC/N SNC/N
STM-1o SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I
STM-4 - - - - SNC/I SNC/I SNC/I SNC/I
STM-1e SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I
100Base-T2 SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I
100Base-T SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I
8 * E11(1.5M) SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I
32 * E11(1.5M) SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I
3*E31(34M) SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I
3*E32(45M) SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I SNC/I

Following tables show some kinds of PPS settings.
Case1: primary/backup ports on Mainboard

Mainboard
slot1 slot2 slot3 slot4
slot1 slot3 STM-4oD OK OK OK OK
slot2 slot4 STM-1o(e)D OK OK OK OK
Red line means PPS setting.
Case2: primary/backup ports on same subboard. Mainboard does not use.
Mainboard Mainboard
STM-N slot3 STM-1o(e)D OK OK OK
slot2 slot4 STM-1o(e)D OK OK OK
Red line means PPS setting. STM-1o(e)D OK OK OK
STM-1o(e)D OK OK OK

2-6
F2880_F05
Case3: one of primary/backup ports on Mainboard, the other one on subboard

Mainboard
STM-N slot3 STM-1(4)o/1o(e) OK OK OK
slot2 slot4 STM-1(4)o/1o(e) OK OK OK
Red line means PPS STM1-(4)o/1o(e) OK OK OK
setting.
STM-1(4)o/1o(e) OK OK OK
STMn subboard in different slot
Case4: one of primary/backup ports on subboard, the other one on another subboard.
Mainboard does not use.
Mainboard Mainboard
STM-N slot3 STM-1o(e)D OK OK
STM-N slot4 STM-1o(e)D OK OK
Red line means PPS STM-1o(e)D OK OK
setting.
STM-1o(e)D OK OK
STM-1o(e)D OK OK
STM-1o(e)D OK OK
NOTE: Above cases combination use in one C-Nod has no limitation

2-7
F2880_F05
2.2.2.2 witching criterion

For SNC/N
Item Switching
requirement
AU-LOP SSF (Server Signal Fail)
AU-AIS SSF (Server Signal Fail)
HP-UNEQ TSF (Trail Signal Fail)

HOP
HP-TIM TSF (Trail Signal Fail)
HP-EXC TSF (Trail Signal Fail)
HP-DEG TSD (Trail Signal Degrade)
TU-LOP SSF (Server Signal Fail)
TU-AIS SSF (Server Signal Fail)
LP-UNEQ TSF (Trail Signal Fail)
LOP LP-TIM TSF (Trail Signal Fail)
LP-EXC TSF (Trail Signal Fail)
LP-DEG TSD (Trail Signal Degrade)
LOM TSF (Trail Signal Fail)
For SNC/I
Item Switching
requirement
AU-LOP SSF (Server Signal Fail)
HOP
AU-AIS SSF (Server Signal Fail)
TU-LOP SSF (Server Signal Fail)

LOP
TU-AIS SSF (Server Signal Fail)
2.2.2.3 External Commands

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

2-8
F2880_F05
2.2.2.4 Command priority

LKOP> FSP> SF on Prot>SF on Work> SD on Prot> SD on Work> MSP>
Wait-to-restore> No request
2.2.2.5 Command value
Wait for restore time: 0min ~12min, step=1 min

Hold-off time: 0ms ~ 10 sec, step=50ms

2-9
F2880_F05
2.3 Synchronization
2.3.1 Timing source

z Internal Free run: +4.6ppm~-4.6ppm
z Internal Holdover: +0.37ppm~-0.37ppm / 1 day
z STM-N Line (any port):
z 2Mbps PDH Line (only #1 channel port)
z External port: 2Mbps or 2MHz selectable (75ohms/120ohms)
1 port: standard
Another port: enhanced by Fan unit option (only 2MHZ)
z Pull-in Lock in range: 9.2 ppm
2.3.2 Timing source control

2.3.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:
z Quality Level conveyed from SSM
z Support or not support SSM
z Forced QL Setting
z Timing Source Failure
2.3.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.3.2.3 SSM Control
The following interfaces support SSM as timing source control:

z STM-N aggregate
z STM-N Tributary

2-10
F2880_F05
z 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 Quality unknown
0001 Reserved
0010 G.811
0011 Reserved
0100 G.812 Transit
0101 Reserved
0110 Reserved
0111 Reserved
1000 G.812 Local
1001 Reserved
1010 Reserved
1011 G.813 (SETS)
1100 Reserved
1101 Reserved
1110 Reserved
1111 Do not use for timing source
SETS: Synchronous Equipment Timing Source
In order to avoid timing loop, SSM control should conform below rules.
1) Selected timing source from STM-N
Node1 SSM = Node2 SSM = Node3

G.811 IN OUT G.811
SSM = SSM =
DNU OUT IN G.812L
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-11
F2880_F05
2) The QL of NE and extended clock is same (Slave to EXT clock)

BITS/SSU
SSM = SSM =
G.811 G.811
Node1 SSM = Node2 SSM = Node3
G.811 IN OUT G.811
SSM = SSM =
DNU OUT IN G.812L
The QL of NE and extended clock is same levelG.811.
3) Selected timing source is from extended clock timing source (can not slave to
EXT clock)
2.3.3 Timing source selection

2.3.3.1 Switching criterion
Lockout>FS> SF>MS
Quality/SSM> Priority
SF (STM-N): LOS, LOF, MS-AIS, AND RS-TIM
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-12
F2880_F05
2.3.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.3.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.3.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.3.3.5 Revertive /non revertive
Fixed to be Revertive.
2.3.3.6 Report to NMS items
All timing source's status (QL, failure), Selected Timing Source and its QL can
report to NMS.
2.3.3.7 2M BPS frame format
z G.704 7/95
z With CRC/without CRC selectable
z TS1~TS31= all 1
z TS 0 =frame word
2.3.3.8 Squelch
When Quality level of working timing source is lower than user setting Quality level
threshold, namely Squelch value, 2M EXTCLK output is squelched and LOS alarm
occurs in far-end equipment.

2-13
F2880_F05
2.4 Trace/signal label function

Trace label function is used for receiving end to confirm that it is connected the
designated transmission end. C-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 bit in CID window. For J byte, available character is listed below
table..
Available Character of J byte

SP 0 @ P ` p
! 1 A Q a q
2 B R b r
# 3 C S c s
$ 4 D T d t
% 5 E U e u
& 6 F V f v
7 G W g w
( 8 H X h x
) 9 I Y i y
* : J Z j z
+ ; K [ k {
, < L \ l |
- = M ] m }
. > N ^ n ~
/ ? O _ o
Signal label function is used to indicate such information as path status, traffic type.
C-Node uses path overhead bytes: C2 and V5 to fulfill this function.
2.5 Configuration Management

Configuration management includes working parameter setup for NE, configuration
of extended 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, Mainboard and

extended 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

2-14
F2880_F05
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.20.
Subboard 504*504 cross-connect module 1008*1008 cross-connect module
Main Slot 1 Slot 2 Slot 3 Slot 4 Main Slot 1 Slot 2 Slot 3 Slot 4
1*STM-1o Y Y Y Y Y Y Y Y Y Y
2*STM-1o Y Y Y X X Y Y Y Y Y
1*STM-1e Y Y Y Y Y Y Y Y Y Y
2*STM-1e Y Y Y X X Y Y Y Y Y
1*STM-4 (NOTE) X X X X X Y Y X Y X
2*STM-4 X X X X X Y X X X X
32*E12(2M) X Y Y Y Y X Y Y Y Y
32*E11(1.5M) X Y Y Y Y X Y Y Y Y
8*E11(1.5M) X Y Y Y Y X Y Y Y Y
100Base-T2 X Y Y Y Y X Y Y Y Y
100Base-T X Y Y Y Y X Y Y Y Y
NOTE:
1) Y denote can be configured in corresponding slot, X denotes can not

be configured in corresponding slot.
2) When 1xSTM-4 is inserted in Slot 1, any other subboards are forbidden to

be inserted in Slot 2. When STM-4 x1 is inserted in Slot 3, any other
subboards are forbidden to be inserted in Slot 4.

2-15
F2880_F05
2.6 Performance monitor
2.6.1 The Definition of PM item
SDH PM
(1of2)
MONITOR TYPES DEFINITION SPEC.
RST BBE Near end background block error ITU-T G.826 G.784
ES Near end errored seconds ITU-T G.826 G.784
SES Near end severely errored seconds ITU-T G.826 G.784
OFS Out of frame seconds ITU-T G.784
UAS Unavailable seconds ITU-T G.826 G.784
MST BBE Near end background block error ITU-T G.826 G.784
MST FEBBE Far end background block error ITU-T G.826 G.784
(Far End)
FEES Far end errored seconds ITU-T G.826 G.784
FESES Far end severely errored seconds ITU-T G.826 G.784
FEUAS Far end unavailable seconds ITU-T G.826 G.784
HPT BBE Near end background block error ITU-T G.826 G.784
HPT FEBBE Far end background block error ITU-T G.826 G.784
(Far End)
LPT BBE Near end background block error ITU-T G.826 G.784

2-16
F2880_F05
(2of2)
LPT FEBBE Far end background block error ITU-T G.826 G.784
(Far End)
MSA PJE-P Pointer justification event ITU-T G.783,G.784
(see
NOTE1)
PJE-N Pointer justification event ITU-T G.783,G.784
(see
NOTE1)
HPA PJE-P Pointer justification event ITU-T G.783,G.784
(see
NOTE1)
PJE-N Pointer justification event ITU-T G.783,G.784
(see
NOTE1)
MSP PSC Protection switching counts ITU-T G.783
(Only for 1+1 APS)
PSD(see Protection switching duration ITU-T G.783
NOTE2)
(Only for 1+1 APS)
NOTE:
1. PJE is the pointer justification event, and justification because of AU pointer stuff:
AU pointer positive stuff=>PJE-P
AU pointer Negative stuff=>PJE-N
No AU pointer stuff=>No PJE counter
2. PSD is not supported now.

2-17
F2880_F05
Ethernet PM
(1of3)
ETH-Drop A count of drop packets.

Pkts
A count of frames received on a RFC1643
ETH-RxAli
particular interface that are not an
gnmentErr
integral number of octets in length and
orFrames
do not pass the FCS check
ETH-RxBr Number of good broadcast packets
oadcastPkt received
s
ETH-RxFC
particular interface that are an integral
SErrorFra
number of octets in length but do not
mes
pass the FCS check.
ETH-RxMu Number of good multicast packets
lticastPkts received(excluding broadcast packets)
The total number of octets received on RFC1213
ETH-RxOc
the interface, including framing
tets
characters.
Number of packets received that were
ETH-RxPkt
between 1024 and the Mac_Pkt_Len
1024toMax
octets in length (including error packets)
LAN
ETH-RxPkt
between 128 to 255 octets in length
128to255
(including error packets)
ETH-RxPkt
256to511
ETH-RxPkt
512to1023
ETH-RxPkt
64 octets in length (including bad
64
packets)
ETH-RxPkt
65to127
ETH-TxCol Number of collisions on this Ethernet
lision segment
A count of frames for which the first RFC1643
ETH-TxDel
transmission attempt on a particular
ayTransmi
interface is delayed because the
ssions
medium is busy.

2-18
F2880_F05
(2of3)
ETH-TxExt A count of frames for which RFC1643
CollisionFr transmission on a particular interface
ames fails due to excessive collisions.
The number of times that a collision is RFC1643
ETH-TxLat detected on a particular interface later
eCollision than 512 bit-times into the transmission
of a packet.
A count of successfully transmitted RFC1643
ETH-TxMul
frames on a particular interface for
tiCollisionF
which transmission is inhibited by more
rames
than one collision.
The total number of packets that RFC1213
higher-level protocols requested be
ETH-TxNU transmitted to a non-unicast (i.e., a
LAN castPkts subnetwork-broadcast or subnetwork
-multicast) address, including those that
were discarded or not sent.
The total number of octets transmitted RFC1213
ETH-TxOct
out of the interface, including framing
ets
characters.
A count of successfully transmitted RFC1643
ETH-TxSin
frames on a particular interface for
gleCollisio
which transmission is inhibited by
nFrames
exactly one collision.
higher-level protocols requested to be
ETH-TxUc
transmitted to a subnetwork-unicast
astPkts
address, including those that were
discarded or not sent.
ETH-Drop A count of drop packets.
Pkts
ETH-RxAli
particular interface that are not an
gnmentErr
integral number of octets in length and
orFrames
do not pass the FCS check
WAN ETH-RxBr Number of good broadcast packets
oadcastPkt received
s
ETH-RxFC
particular interface that are an integral
SErrorFra
number of octets in length but do not
mes
pass the FCS check.

2-19
F2880_F05
(3of3)
ETH-RxMu Number of good multicast packets
lticastPkts received(excluding broadcast packets)
The total number of octets received on RFC1213
ETH-RxOc
the interface, including framing
tets
characters.
ETH-RxPkt
between 1024 and the Mac_Pkt_Len
1024toMax
octets in length (including error packets)
ETH-RxPkt
128to255
ETH-RxPkt
256to511
ETH-RxPkt
512to1023
WAN
ETH-RxPkt
64 octets in length (including bad
64
packets)
ETH-RxPkt
65to127
higher-level protocols requested be
ETH-TxNU transmitted to a non-unicast (i.e., a
castPkts subnetwork-broadcast or subnetwork
-multicast) address, including those that
were discarded or not sent.
The total number of octets transmitted RFC1213
ETH-TxOct
out of the interface, including framing
ets
characters.
The total number of packets that higher RFC1213
ETH-TxUc
level protocols requested to be
astPkts
transmitted to a subnetwork.

2-20
F2880_F05
Encapsulation PM
GFP_RxE A count of received frame with HEAD
XIErrorPkt errors.
s
GFP_RxF A count of received frame with FCS
CSErrorPkt errors.
s
GFP_RxO A count of received octets.
GFP ctets
GFP_RxPk A count of received frame.
ts
GFP_TxOc A count of transmitted octets.
tets
GFP_TxPk A count of transmitted frame.
ts
LAPS_RxF A count of received frame with FCS
CSErrorPkt errors.
s
LAPS_Rx A count of received octets.
Octets
LAPS LAPS_RxP A count of received frame.
kts
LAPS_TxO A count of transmitted octets.
ctets
LAPS_TxP A count of transmitted frame.
kts

2-21
F2880_F05
2.6.2 Performance Counter Range
SDH PM Counter Range
PM TYPES 15m PM COUNTER RANGE 24h PM COUNTER RANGE
MEMORY RANGE MEMORY RANGE
OFS 2 Byte 0-900 4 Byte 0-86400
BBE 4 Byte 0-4294967295 4 Byte 0-4294967295
ES 2 Byte 0-900 4 Byte 0-86400
SES 2 Byte 0-900 4 Byte 0-86400
UAS 2 Byte 0-900 4 Byte 0-86400
FE-BBE 4 Byte 0-4294967295 4 Byte 0-4294967295
FE-ES 2 Byte 0-900 4 Byte 0-86400
FE-SES 2 Byte 0-900 4 Byte 0-86400
FE-UAS 2 Byte 0-900 4 Byte 0-86400
PSC 4 Byte 0-4294967295 4 Byte 0-4294967295
PSD 2 Byte 0-900 4 Byte 0-86400
PJE-P 4 Byte 0-4294967295 3 Byte 0-4294967295
PJE-N 4 Byte 0-4294967295 3 Byte 0-4294967295

2-22
F2880_F05
Ethernet PM Counter Range
PM TYPES 15m PM COUNTER RANG 24h PM COUNTER RANG
ETH-TxOctets 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-RxOctets 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-RxFCSErrorFrames 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-RxAlignmentErrorFrames 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-TxUcastPkts 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-TxNUcastPkts 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-RxMulticastPkts 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-RxBroadcastPkts 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-TxSingleCollisionFrames 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-TxMultiCollisionFrames 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-TxDelayTransmissions 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-TxExtCollisionFrames 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-TxLateCollision 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-TxCollision 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-RxPkt64 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-RxPkt65to127 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-RxPkt1024toMax 4 Byte 0-4294967295 4 Byte 0-4294967295
ETH-DropPkts 4 Byte 0-4294967295 4 Byte 0-4294967295

2-23
F2880_F05
GFP PM Counter Range
GFP_TxPkts 4 Byte 0-4294967295 4 Byte 0-4294967295
GFP_TxOctets 4 Byte 0-4294967295 4 Byte 0-4294967295
GFP_RxPkts 4 Byte 0-4294967295 4 Byte 0-4294967295
GFP_RxOctets 4 Byte 0-4294967295 4 Byte 0-4294967295
GFP_RxFCSErrorPkts 4 Byte 0-4294967295 4 Byte 0-4294967295
GFP_RxEXIErrorPkts 4 Byte 0-4294967295 4 Byte 0-4294967295
LAPS PM Counter Range
LAPS_TxPkts 4 Byte 0-4294967295 4 Byte 0-4294967295
LAPS_TxOctets 4 Byte 0-4294967295 4 Byte 0-4294967295
LAPS_RxPkts 4 Byte 0-4294967295 4 Byte 0-4294967295
LAPS_RxOctets 4 Byte 0-4294967295 4 Byte 0-4294967295
LAPS_RxFCSErrorPkts 4 Byte 0-4294967295 4 Byte 0-4294967295
NOTE: when the PM value exceeds the maximum value in the range showed in all above
tables, the PM will be regarded as overflow and showed in PM monitor screen of CID.

2-24
F2880_F05
2.6.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 NEAR END DEFECT CONDITION
LO path layer 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 MS AIS
RST layer RS TIM
STM LOS
STM LOF
The Defects Causing Far End SES
PATH LAYER NEAR END DEFECT CONDITION

LO path layer LP RDI
HO Path layer HP RDI
SES PM threshold is shown in below table.

Facility SES Threshold Value
VC11 600
VC12 600
VC3 2400
VC4 2400
RS 2400
MS 2400

2-25
F2880_F05
2.6.4 Suspect condition

Suspect condition means that PM does not correctly count.
z Overflow
z Near end failure for 100Base-T/100Base-T2 PM
z Reset
z Path create/delete*
*NOTE: when the path delete, there is no report.
2.6.5 Register management

2.6.5.1 Type of register
Period Current History
15min 1 maximum count, more is deleted
1day 1 maximum count, 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.6.6 PM reset function

CID supports PM reset function. It restores PM count value to 0.

2-26
F2880_F05
2.6.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.6.7.1 TCA report action
TCA TCA
Threshold
Count period 15min /1 day Count period 15min /1 day CcCount period 15min /1 day
2.6.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.

2-27
F2880_F05
SDH TCA
(1of2)
LAYER PM TYPES 15m TCA THRESHOLD 24h TCA THRESHOLD
DEFAULT RANGE DEFAULT RANGE
RS BBE 65535 0-16777215 6291360 0-1610612640
ES 900 0-900 86400 0-86400
SES 63 0-900 4095 0-86400
UAS 63 0-900 4095 0-86400
OFS 900 0-900 86400 0-86400
MS BBE 65535 0-65535 6291360 0-6291360
ES 900 0-900 86400 0-86400
SES 63 0-900 4095 0-86400
UAS 63 0-900 4095 0-86400
FE-BBE 65535 0-65535 6291360 0-6291360
FE-ES 900 0-900 86400 0-86400
FE-SES 63 0-900 4095 0-86400
FE-UAS 63 0-900 4095 0-86400
MSP PSC 900 0-900 86400 0-86400
PSD 900 0-900 86400 0-86400
AU-4 PJE-P 113184 0-113184 10865664 0-10865664
PJE-N 113184 0-113184 10865664 0-10865664
VC-4 BBE 65535 0-65535 6291360 0-6291360
ES 900 0-900 86400 0-86400
SES 63 0-900 4095 0-86400
UAS 63 0-900 4095 0-86400
FE-BBE 65535 0-65535 6291360 0-6291360
FE-ES 900 0-900 86400 0-86400
FE-SES 63 0-900 4095 0-86400
FE-UAS 63 0-900 4095 0-86400

2-28
F2880_F05
(2of2)
VC-3 BBE 65535 0-65535 6291360 0-6291360
ES 900 0-900 86400 0-86400
SES 63 0-900 4095 0-86400
UAS 63 0-900 4095 0-86400
FE-BBE 65535 0-65535 6291360 0-6291360
FE-ES 900 0-900 86400 0-86400
FE-SES 63 0-900 4095 0-86400
FE-UAS 63 0-900 4095 0-86400
VC-12 BBE 65535 0-65535 6291360 0-6291360
ES 900 0-900 86400 0-86400
SES 63 0-900 4095 0-86400
UAS 63 0-900 4095 0-86400
FE-BBE 65535 0-65535 6291360 0-6291360
FE-ES 900 0-900 86400 0-86400
FE-SES 63 0-900 4095 0-86400
FE-UAS 63 0-900 4095 0-86400
TU PJE-P 113184 0-113184 10865664 0-10865664
PJE-N 113184 0-113184 10865664 0-10865664

2-29
F2880_F05
Ethernet TCA
(1of2)
ETH-TxOctets 4294967294 0-4294967294 4294967294 0-4294967294
ETH-RxOctets 4294967294 0-4294967295 4294967294 0-4294967294
ETH-RxFCSErrorF
133929000 0-133929000 4294967294 0-4294967294
rames
ETH-RxAlignment
133929000 0-133929000 4294967294 0-4294967294
ErrorFrames
ETH-TxUcastPkts 133929000 0-133929000 4294967294 0-4294967294
ETH-TxNUcastPkt
133929000 0-133929000 4294967294 0-4294967294
s
ETH-RxMulticastP
133929000 0-133929000 4294967294 0-4294967294
kts
ETH-RxBroadcast
133929000 0-133929000 4294967294 0-4294967294
Pkts
ETH-TxSingleColli
133929000 0-133929000 4294967294 0-4294967294
sionFrames
ETH-TxMultiCollisi
133929000 0-133929000 4294967294 0-4294967294
LAN onFrames
ETH-TxDelayTran
133929000 0-133929000 4294967294 0-4294967294
smissions
ETH-TxExtCollisio
133929000 0-133929000 4294967294 0-4294967294
nFrames
ETH-TxLateCollisi
133929000 0-133929000 4294967294 0-4294967294
on
ETH-TxCollision 46875000 0-46875000 4294967294 0-4294967294
ETH-RxPkt64 133929000 0-133929000 4294967294 0-4294967294
ETH-RxPkt65to12
133929000 0-133929000 4294967294 0-4294967294
7
ETH-RxPkt128to2
76014000 0-76014000 4294967294 0-4294967294
55
ETH-RxPkt256to5
40760970 0-40760970 4294967294 0-4294967294
11
ETH-RxPkt512to1
21146400 0-21146400 4294967294 0-4294967294
023

2-30
F2880_F05
(2of2)
ETH-RxPkt1024to
10775700 0-10775700 4294967294 0-4294967294
LAN Max
ETH-DropPkts 133929000 0-133929000 4294967294 0-4294967294
ETH-TxOctets 4294967294 0-4294967294 4294967294 0-4294967294
ETH-RxOctets 4294967294 0-4294967294 4294967294 0-4294967294
ETH-RxFCSErrorF
133929000 0-133929000 4294967294 0-4294967294
rames
ETH-RxAlignment
133929000 0-133929000 4294967294 0-4294967294
ErrorFrames
ETH-TxUcastPkts 133929000 0-133929000 4294967294 0-4294967294
ETH-TxNUcastPkt
133929000 0-133929000 4294967294 0-4294967294
s
ETH-RxMulticastP
133929000 0-133929000 4294967294 0-4294967294
kts
ETH-RxBroadcast
133929000 0-133929000 4294967294 0-4294967294
WAN Pkt
ETH-RxPkt64 133929000 0-133929000 4294967294 0-4294967294
ETH-RxPkt65to12
133929000 0-133929000 4294967294 0-4294967294
7
ETH-RxPkt128to2
76014000 0-76014000 4294967294 0-4294967294
55
ETH-RxPkt256to5
40760970 0-40760970 4294967294 0-4294967294
11
ETH-RxPkt512to1
21146400 0-21146400 4294967294 0-4294967294
023
ETH-RxPkt1024to
10775700 0-10775700 4294967294 0-4294967294
Max
ETH-DropPkts 133929000 0-133929000 4294967294 0-4294967294

2-31
F2880_F05
GFP TCA
GFP_TxPkts 4294967294 0-4294967294 4294967294 0-4294967294
GFP_TxOctets 4294967294 0-4294967295 4294967294 0-4294967294
GFP_RxPkts 4294967294 0-4294967294 4294967294 0-4294967294

Encapsula
GFP_RxOctets 4294967294 0-4294967294 4294967294 0-4294967294
tion
GFP_RxFCSError
133929000 0-133929000 4294967294 0-4294967294
Pkts
GFP_RxEXIErrorP
133929000 0-133929000 4294967294 0-4294967294
kts
LAPS TCA
LAPS_TxPkts 4294967294 0-4294967294 4294967294 0-4294967294
LAPS_TxOctets 4294967294 0-4294967295 4294967294 0-4294967294
Encapsula LAPS_RxPkts 4294967294 0-4294967294 4294967294 0-4294967294

tion
LAPS_RxOctets 4294967294 0-4294967294 4294967294 0-4294967294
LAPS_RxFCSErro
133929000 0-133929000 4294967294 0-4294967294
rPkts

2-32
F2880_F05
2.7 Fault management
2.7.1 Fault monitor items

SDH Alarm
(1of4)
INDICATION CATEGORY DESCRIPTION FAULT LOCATION DEFAULT CLASS
AIS Facility Alarm indication EXT CLK IN MN

(only signal External timing source
2Mbps)
AU-AIS Facility Alarm indication MSA MJ
signal MSA function in
upstream equipment
AU-LOP Facility Loss of pointer MSA MJ
MSA function in
upstream equipment
BUS_ERR Equipment BUS defect BUS MN
OR BUS_ERROR
CLKFAIL Facility Clock fail SETS MN
Clock module
CLKDRIF Facility Frequency drift SETS MN
T Clock sending function in
upstream equipment
FAN_FAIL Equipment Fan defect Fan MN
HKAn Environme House keeping Environment MN
(n = 1 thru nt alarms Environment device
8)
HP-DEG Facility VC-4 B3 byte HPT MN
error(10-5) HPT in upstream
equipment or optical fiber
and connector
HP-EXC Facility VC-4 B3 byte HPT MJ
error(10-3) HPT in upstream
equipment or optical fiber
and connector
HP-PLMF Facility Payload HPA MJ
mismatch Configuration in
upstream equipment
HP-RDI Facility Remote defect HPT MJ
indicate Upstream equipment
detecting HP alarm

2-33
F2880_F05
(2of4)
HP-TIM Facility Trace mismatch HPT MJ

J1 setting or upstream
equipment setting
HP-UNEQ Facility Unequipped HPT MJ
No crossconnect setting
in upstream equipment
LINK-FAIL Network LAPD DCC MN
communication
fail Upstream equipment
DCC failure
LOF Facility Loss of frame RST CR
Upstream equipment
LOF (only Facility Loss of frame EXT CLK IN MN
2Mbps)
External timing source
LOM Facility Los of HPA MJ
multi-frame
HPA function in
upstream equipment
LOS Facility No signal input SPI CR
Optical fiber or upstream
equipment
45M CR
45M input cable or
upstream equipment
34M CR
34M input cable or
upstream equipment
2M CR
2M input cable or
upstream equipment
1.5M CR
1.5M input cable or
upstream equipment
EXT CLK IN (2Mbps) MN
Input cable or external
timing source

2-34
F2880_F05
(3of4)
LOS Facility No signal input EXT CLK IN MN

(2MHz)
Input cable or external
timing source
LOS Facility No signal input SPI CR
(electrical
INTF) Cable or upstream
equipment
LP-DEG Facility VC-4 B3 byte LPT MN
error(10-5)
VC12 BIP-2 LPT in upstream
error(10-5) equipment or optical fiber
and connector
LP-EXC Facility VC-4 B3 byte LPT MJ
error(10-3)
VC12 BIP-2 LPT in upstream
error(10-3) equipment or optical fiber
and connector
LP-PLMF Facility Payload LPA MJ
mismatch
Configuration in
upstream equipment
LP-RDI Facility Remote defect LPT MJ
indicate
Upstream equipment
detecting LP alarm
LP-TIM Facility Trace mismatch LPT MJ
equipment setting
LP-UNEQ Facility Unequipped LPT MJ
No crossconnect setting
in upstream equipment
LTI Facility Los of External SETS MJ
timing source
All the timing source
MEM_FAI Equipment Memory defect MEM MN
L
Memory fail
MS-AIS Facility Alarm indication MST CR
signal
Upstream equipment
MS-DEG Facility MS B2 byte MST MN
error(10-5)
Optical fiber or connector

2-35
F2880_F05
(4of4)
MS-EXC Facility MS B2 byte MST MJ

error
Optical fiber or connector
MS-RDI Facility Remote defect MST MJ
indicate
Upstream equipment
detecting alarm
PKG_FAIL Equipment Package defect PKG (see NOTE) CR
Cant be identified board
PKG_REM Equipment Remove board PKG (see NOTE) CR
OVED
Not install board
PKG_TYP Equipment Wrong PKG PKG (see NOTE) CR
E install
Wrong configuration
PPS_FAIL Facility PPS failed HPC, LPC CR
Both not receiving signals
REF_FAIL Facility SSM failure SETS MN
Upstream equipment
RS-TIM Facility Trace mismatch RST CR
equipment setting
TU-AIS Facility Alarm indication HPA, LPA MJ
signal
HPA function in upstream
equipment
TU-LOP Facility Loss of pointer HPA MJ
HPA function in upstream
equipment
NOTE: PKG (Package) indicates Mainboard and subboards.

2-36
F2880_F05
Ethernet Alarm
(1of2)
FAULT DEFAULT
INDICATION CATEGORY DESCRIPTION
LOCATION CLASS
Loss of Client Signal Ethernet MJ

CSF_LCS Facility (WAN)
Loss of Client Character Ethernet MJ
CSF_LCSync Facility Synchronization (WAN)
Remote end Loss of Client Ethernet MN
CSF_R_LCS Facility Signal (WAN)
CSF_R_LCS Remote end Loss of Client Ethernet MN
ync Facility Character Synchronization (WAN)
DropPkts_EX Facility A count of drop packets. Ethernet MJ
C
(LAN&WAN)
LINK_DOWN Facility Alarm for the link status. Ethernet CR
(LAN&WAN)
RxAlignment Facility A count of frames received Ethernet MJ
ErrorFrames on a particular interface that
_EXC are not an integral number of (LAN&WAN)
octets in length and do not
pass the FCS check
RxFCSErrorF Facility A count of frames received Ethernet MJ
rames_EXC on a particular interface that
are an integral number of (LAN&WAN)
octets in length but do not
pass the FCS check.
TxCollision_ Facility Number of collisions on this Ethernet MJ
EXC Ethernet segment
(LAN)
TxDelayTran Facility A count of frames for which Ethernet MJ
smission_EX the first transmission attempt
C on a particular interface is (LAN)
delayed because the
medium is busy
TxExtCollisio Facility A count of frames for which Ethernet MJ
n_EXC transmission on a particular
interface fails due to (LAN)
excessive collisions.

2-37
F2880_F05
(2of2)
FAULT DEFAULT
LOCATION CLASS
TxLateCollisi Facility The number of times that a Ethernet MJ

on_EXC collision is detected on a
particular interface later than (LAN)
512 bit-times into the
transmission of a packet
WAN_PORT Facility WAN port DEG Ethernet MN
_SD
(WAN)
WAN_PORT Facility WAN port fail Ethernet MJ
_SF
(WAN)
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

DEFAULT THRESHOLD
ALARM PERFORMANCE
THRESHOLD SETTING RANGE
DropPkts_EXC ETH-DropPkts 4294967294 0~4294967294

RxAlignmentErrorFrame ETH-RxAlignmen 4294967294
s_EXC tErrorFrames 0~4294967294
RxFCSErrorFrames_EX ETH-RxFCSErrorFram 4294967294
C es 0~4294967294
TxCollision_EXC ETH- TxCollision 4294967294 0~4294967294
TxDelayTransmission_E ETH- 4294967294
XC TxDelayTransmissions 0~4294967294
ETH-TxExtCollisionfra 4294967294
TxExtCollision_EXC
mes 0~4294967294
TxLateCollision_EXC ETH- TxLateCollision 4294967294 0~4294967294

2-38
F2880_F05
Encapsulation Alarm
FAULT DEFAULT
LOCATION CLASS
SSF_LGS Facility Loss of GFP frame WAN MJ

Synchronization
LAPS_FAIL Facility LAPS Layer Fail WAN MJ
Virtual Concatenation Alarm

FAULT DEFAULT
LOCATION CLASS
LP-Xv-LOA Facility Loss of Alignment VC12/VC3 MJ

LP-Xv-LOM Facility Loss of Multi-frame defect VC12/VC3 MJ
LP-Xv-PLM Facility Extended signal label VC12 MJ
mismatch
LP-Xv-SQM Facility Loss of Sequence defect VC12/VC3 MJ

2-39
F2880_F05
2.7.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.7.2.1 Alarm Level
z SA (Service Affecting condition)
This level shows when a service affecting alarm is occurring and continuing.
z NSA (Non-Service Affecting condition)
This level shows when a non-service affecting alarm is occurring and continuing.
2.7.2.2 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
C-Node don't belong to this class by default.
2.7.2.3 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:
z Delay Time
Delay Time is a specific period for the process to determine if the detected failure is
an alarm to be reported.

2-40
F2880_F05
Delay Time: 0 to 2.5 seconds, step=0.5

z 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.7.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.7.3.1 LED Process
LED on front of rack lights up when alarm is generated/cleared to report the alarm to
the user.
2.7.3.2 Report to User Interface
The Time, location etc information should be report to CID/NMS.

z Alarm is automatically reported to User Interface when alarm is
generated/cleared;
z Alarm report includes time information when equipment confirms alarm
occurrence and recovery;
z Alarm report include the alarm location information which board and section the
alarm locates;
z 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.7.3.3 Office Alarms
C-Node has four types of office alarms output: Alarm output for Bell (AB), Alarm
Lamp (AL), Prompt Maintenance (PM), Differed Maintenance (DM) and LED on
front of Rack.
Following table lists the relationship of alarm class and office alarm.

2-41
F2880_F05
RANK OF ALARM REPORT TO OS PM DM AB AL LED
CR (Critical) V V V V V
MJ (Major) V V V V V
MN (Minor) V V V V V
WN (Warning) V
ACO function V
NOTE: V denotes corresponding office alarm in the column will report when
corresponding class alarm in the row occurs.
2.7.3.4 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-42
F2880_F05
2.8 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)

2-43
F2880_F05
(1of3)
User Level
Command List
Level4 Level3 Level2 Level 1
PM
Browse Current Performance (including of 15M and 24H) O O O O
Browse History Performance (including ,of 15M and 24H) O O O O
Reset the performance counters O O O X
Set the performance threshold (including of 15M and 24H) O O O X
Inhibit the reporting of the performance O O O X
Set the switch state of reporting zero value O O O X
Set the switch state of recording zero value O O O X
Set the switch state of reporting event of O O O X
Browse the attributes of all kinds of performance O O O O
ALM
Retrieve and browse the current Alarm O O O O
Retrieve and browse the history alarm O O O O
Inhibit the alarm reporting O O O X
Set the delay time of reporting alarm generation O O O X
Set the stretch time of reporting alarm disappear O O O X
Set the alarm severity O O O X
Set the attribute of alarm bell O O O X
Browse the attributes of all kinds of alarm O O O O
Retrieve and browse a variety of events (including protection switch,
time source switch, equipment type change and QoS alarm) O O O O
Configuration
Modify NE's attributes O O O X
Browse NE's attributes O O O O
Install panel O O O X
Uninstall panel O O O X
Establish the links between NEs O O O X
Delete the links of NE O O O X
Activate the ports (including traffic port and other kinds of ports) O O O X
Deactivate the ports (including traffic port and other kinds of ports) O O O X
Browse the working state of ports O O O O
Set the attributes of power port O O O X
Browse the attributes of power port O O O O
Set the attributes of fan port O O O X
Browse the attributes of fan port O O O O

2-44
F2880_F05
(2of3)
Command List User Level

Browse the attributes of network administration Port (including
RS232 and Ethernet) O O O O
Set the attributes of environment ports O O O X
Browse the attributes of environment ports O O O O
Set the attributes of out environment ports O O O X
Browse the attributes of out environment ports O O O O
Set the orderwire numbers of broadcasting, group and individual O O O X
Browse the orderwire numbers of broadcasting, group and individual O O O O
Set the sending and expecting value of J byte (including J0, J1 and
J2) O O O X
Browse the J value (including J0,J1 and J2 O O O O
Browse the C2/V5 value O O O O
Set terminal and link loopback O O O X
Cancel the loopback O O O X
Install Cross-Module O O O X
Uninstall Cross-Module O O O X
Download firmware O O X X
Upgrade firmware O O X X
Browse the version information and working state of firmware O O O O
Establish Cross-Connect O O O X
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)) O O O X
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) O O O O
Delete Cross-Connect O O O X
Modify Cross-Connect Attribute O O O X
Set SNCP O O O X
Set laser switch, working state, wave length and line code O O O X
Setup MSP O O O X
Browse the MSP Setup O O O O

2-45
F2880_F05
(3of3)
User Level
Command List
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)) O O O X
Browse the attributes of system clock source (including priority,
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)) O O O O
Set the attributes of pass through clock source (including priority,
restore, the forced sending SSM value, the switch of sending forced
SSM value and support of extra command (such as Lockout, Force,
Manual)) O O O X
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)) O O O O
Set the attributes of clock source of outputting 2Mb/2Mh(including
SAN Bit and state) O O O X
Browse the attributes of clock source of outputting 2Mb/2Mh
(including SAN Bit and state) O O O O
Set NE time O O O X
Browse NE time O O O O
Database up/download O O X X
Security
Create user O O* X X
Delete user O O* X X
Change password O O* X X
Modify the user level O O* X X
Set the life of user O O* X X
Browse the user information O O* X X
Browse the log of operation O X X X

2-46
F2880_F05
2.9 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 and EMS memory management:
z Unit reset
z Equipment initialization function
z Loopback control
z Loopback control for each tributary.
z Software upgrade
z Configuration download /upload
The software can be downloaded via online and the current version can be obtained
(updated) smoothly without influence of running traffic.
2.9.1 Loopback
NOTE: In remote login loopback for SDH interface is forbidden, but that for PDH
interface is allowed.
2.9.1.1 Facility loopback
z STM-N optical signal

When Facility loopback is operated AIS signal shall be sent to cross connect side.
STM-1/4 o
MST RST SPI OPT OUT
FAC LPB
SA MST RST SPI OPT IN
MS-AIS
z STM-1e signal
When Facility loopback is operated AIS signal shall be sent to cross connect side.

2-47
F2880_F05
STM-1 e
MST RST SPI OUT
FAC LPB
SA MST RST SPI IN
MS-AIS
z 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.
AIS
PDH PI LPA LPT HPA
INTF PI LPA LPT HPA
2.9.1.2 Terminal loopback
z STM-N signal
The signal sent to opposite end is same as the signal returned to local end (cross
connect)
STM-1/4 o
MST RST SPI OPT OUT
TRM LPB
SA MST RST SPI OPT IN

2-48
F2880_F05
z 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
z PDH signal
The 2M/34M/1.5M/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.
PDH PI LPA LPT HPA
INTF PI LPA LPT HPA

AIS
2.10 LOG
A list of the operation logs and event logs of the NE can be recorded.
z Event Log: max 500 items for each event log
z Command Log: max 500 items

2-49
E
This page is intentionally left blank.
F2880_F05
3. EXTERNAL INTERFACES
3.1 User channel

z Physical interface: V.11, 64kb/s
z Mode: Co- directional/Contra-directional
z Max Cable length: 1KM
z Connector: RJ45
z Interface control: Add/Drop or Bypass
z Accessible OH Byte: F1, E2
3.2 Orderwire
z Level Diagram: Rx: 2 dBm
Tx 0 dBm
z DTMF Tone Level: Rx 10 dBm
Tx: 10 dBm
z Impedance: 600ohm
z Signal Instruction Mode: dual tone multi-frequency mode (DTMF)
z Single Tone:
Frequency: 450Hz
Dialing tone: long continuous tone
Ring back tone: 1 second connecting, 2 seconds disconnecting
Busy tone: 0.4 seconds disconnecting and continuing
Notice mode: buzzer-producing tone
Station addresses: up to 999
z Operation mode: All call/ Group call/Selective call
All call: All NEs whose orderwire channel(s) is (are) opened and
corresponding optical port(s) connected by fibers are called.
Group call: 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.
Selective call: 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.
z Connector: RJ11
External Interfaces
3-1
F2880_F05
z Accessible OH Byte: E1
z Up to 4 overwire branches are available at the same time though up to 10 optical
ports are provided in C-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

z Physical Layer: RS-232C, 10Base-T (Half/10M)
z Connector: D-sub 9-pin (RS-232C)

RJ-45 (10Base-T)
z Connection: UTP Straight cable (via Hub)
3.3.2 NMS
z Physical Layer: 10Base-T (Half/10M)
z Connector: RJ-45
z Connection: UTP Straight cable (via Hub)
z Protocol: TCP/IP
3.4 Physical Specification
3.4.1 C-Node Subrack Dimensions

z Height: 88 mm
z Width: 482.6 mm
z Depth: 306 mm
z Weight: 7.3 Kg(Typical configuration, with an E12 subboard)
NOTE: Above dimension includes any projection of subrack.
External Interfaces
3-2

F05 Work PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

F05 Work PDF

Uploaded by

Copyright:

Available Formats

F2880_F05

TELEX NECTOK J22686 FAX +81-3-3798-1510/9 E-mail:mcj@onw.nec.co.jp

SpectralWave is a registered trademark of NEC Corporation.

Copyright 2002-2004 by NEC Corporation.

1. SDH WORKING PRINCIPLE 1-1

1.3 Layer 2 Switch Function ................................................................ 1-11

1.4 Encapsulation and LCAS Function ............................................... 1-55

2. C-NODE WORKING PRINCIPLE 2-1

2.2 Protection.......................................................................................... 2-3

2.2.2 SNCP ...................................................................................................... 2-5

2.3 Synchronization.............................................................................. 2-10

2.4 Trace/signal label function ............................................................ 2-14

2.7 Fault management .......................................................................... 2-33

2.8 Security management .................................................................... 2-43

2.10 LOG.................................................................................................. 2-49

3.4 Physical Specification...................................................................... 3-2

1. SDH WORKING PRINCIPLE

1.1 Signal Multiplexing Paths

Figure 1-1 shows the functional diagram of signal multiplexing paths:

STM-N AUG AU-4 VC-4 C-4 139264kbit/s

TUG-3 TU-3 VC-3

Location and calibration TU-12 VC-12 C-12 2048kbit/s

Figure 1-1. STM-N Signal Multiplexing Paths

SDH Working Principle

1.2 Basic Parameters

1.2.1 Frame Structure

Figure 1-2. Basic Frame Structure

Table1-1. Frame Structure Parameter of STM-1

1.2.2 Multiplexing Structure and Multiplexing Methods

Multiplexing structure is provided in Figure 1-1. Multiplexing STM-1 to STM-N or

SDH Working Principle

1.2.3 Frame Synchronization and Line Code Type

z STM-4 optical line interface:

z STM-1 optical line interface:

z STM-1 electrical line interface: CMI code

z 45M electrical tributary interface: B3ZS code

z 34M electrical tributary interface: HDB3 code

z 2M electrical tributary interface: HDB3 code

z 1.5M electrical tributary interface: B8ZS code

1.2.4 Overhead Function

C-Node supports section and path OH.

The definition of SOH is shown in Figure 1-3 and Table 1-2.

SDH Working Principle

Bytes reserved for national use

* Unscrambled bytes. Therefore care should be taken

NOTE ? All unmarked bytes are reserved for future international

Figure 1-3. SOH of STM-1 and STM-4

SDH Working Principle

Table 1-2. Summary for RSOH/MSOH of STM-1 and STM-4

Byte Position (STM-1 frame) Position (STM-4 frame)

B2 5 1,2,3 Error Monitor on STM-1

B2 5 1 thru 12 Error Monitor on STM-4

K1 5 4 5 13 APS (Automatic Protection Switching)

M1 9 6 9 15 Multiplex Section REI (Remote Error

S1 9 1 9 1 Synchronization Status Message

12, 9 8, 9 12, 9 29 thru 36 National uses

2, 3 2, 3, 5 2, 3 5 thru 12 Illustrating types of transmission media

SDH Working Principle

z K1, K2 Bytes (b1 thru b5):

z K2 Bytes (b6 thru b8):

z S1 Bytes (b5 thru b8):

SETS: Synchronous Equipment Timing Source

SDH Working Principle