F05 Work PDF
F05 Work PDF
F05 Work PDF
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
Printed in China
F2880_F05
FUNCTIONAL DESCRIPTION
CONTENTS
Contents
i
F2880_F5
FUNCTIONAL DESCRIPTION
Contents
ii
E
F2880_F05
FUNCTIONAL DESCRIPTION
C-3 44736kbit/s
34368kbit/s
TUG-2
Pointer processing
multiplexing
VC-11 C-11 1544kbit/s
mapping
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
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
The blanks in the figure and table are reserved to arrange bytes by international, is
a byte related to transmission media, is a reserved byte for the civil use, * is a byte
that are not scrambled.
9 bytes
A1 A1 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
STM-1
STM-4
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.
In it:
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 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).
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.
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
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
These bits of K3 byte are reserved for the future use, and have no defined values.
The receiver is required to ignore their content.
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
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.
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.
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.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
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.
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.3.3.1 Configuration
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.
Figure 1-11
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.3.4.1 Configuration
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.
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
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.
Figure 1-15
1.3.6.1 Configuration
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.
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
Figure 1-16
NOTE: The configuration is valid only when enable both Maximum Bridge Transmit
Delay and Low Queue Delay Bound
Figure 1-17
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:
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
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:
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
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
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
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
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
Figure 1-22
VLAN Setting:
LAN1-a-U, WAN1-a-U
LAN2-b-U, WAN2-b-T
LAN3-c-T, WAN3-c-T
LAN4-d-T, WAN4-d-U
LAN4-e-U
Then there are six VLANs in bridge include default VLAN.
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
Shows in Figure 1-24 on above,
If a untagged frame received from LAN1, this frame will be dropped by ingress
filter on LAN1;
If a untagged frame received from LAN2, this frame will be dropped by ingress
filter on LAN2.
3.1.3 Ingress Filter: Disable All or Forward Match VID on all ports
Figure 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.
3.1.4 Ingress Filter: Enable All or Drop Untagged Frame on all ports
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.
3.1.5 Ingress Filter: Disable All or Forward Match VID on all ports
Figure 1-27
Shows in Figure 1-27 on above, if a untagged frame received from LAN4, this
frame belongs VLANe, so it is added a VID e at ingress direction, and then
dropped on egress direction.
3.1.6 Ingress Filter: Enable All or Drop Untagged Frame on all ports
Figure 1-28
Shows in Figure 1-28 on above, if a untagged frame received from LAN4, this
frame will be dropped by ingress filter on LAN4.
3.2.1 Ingress Filter: Disable All or Drop Untagged Frame or Enable All or
Forward Match VID on all ports
Figure 1-29
Shows in Figure 1-29 on above,
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
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
Shows in Figure 1-31 on above,
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.
3.2.5 Ingress Filter: Disable All or Drop Untagged Frame on all ports
Figure 1-33
Shows in Figure 1-33 on above,
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 LAN2, this
frame will be dropped;
If a tagged frame(Not configured VID:xa,b,c,d,e,1) received from LAN3, 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
Shows in Figure 1-34 on above,
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,
this frame will be dropped by ingress filter on LAN2;
If a tagged frame(Not configured VID in this port:xc,1) received from LAN3,
this frame will be dropped by ingress filter on 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.
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
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
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
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 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.
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.
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.
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:
(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
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
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)
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
To avoid the ring, STP function must be combined with VLAN function. Many
potential rings exist, as shows below:
Figure 1-39
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.
Since networking directly, and any subscriber equipment is not passed, the
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.
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.
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.
1. Bridge Max Age >= 4*Bridge Hello Time + 2*Maximum Bridge Diameter -
2
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:
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.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. 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
should match with each other at local side and remote side.
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
Figure 1-45
The items to be configured and queried:
1. Monitor Mode
Both indicates monitor the data in both input and output direction.
2. Monitoring Port
3. Monitored Port
Configure the port monitored. Ranges from LAN1 to LAN4 or from WAN1 to
WAN4
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
1. Both the monitored port and monitoring port are required to be in the same
VLAN.
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.
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.
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
2. When Security is enabled (No Security enabling function for WAN port):
NOTE:
1) Input and Output directions are based on L2SW (Layer 2 Switch).
Forward Forward the frame only to the port which the MAC address be set in MAC table.
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
The items to be configured and queried:
1. Queue Mode
Configure service queue mode. The choices include FIFO(First In First
Out),SP(Strictly Priority),WRR(Weighted Round Robin). Default is FIFO.
2. WRR High Weight
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
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.
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.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.
NOTE: The difference between LAPS and GFP-F are shown as bellow:
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.
E
This page is intentionally left blank
F2880_F05
FUNCTIONAL DESCRIPTION
A B
z Broadcast
2.1.3.3 Loopback
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
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
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)
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
NOTE: C-Node supports both SNC/N and SNC/I in SNCP ring configuration,
according to the following table.
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 PPS setting. STM-1o(e)D OK OK OK
STM-1o(e)D OK OK OK
STM-N subboard in different slot
Case4: one of primary/backup ports on subboard, the other one on another subboard.
Mainboard does not use.
Aggregate Tributary:2M/1.5M/34M/45M/STM-1o(e)
Mainboard Mainboard
slot1 slot2 slot3 slot4
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
STM-N subboard in different slot
For SNC/I
Item Switching
requirement
AU-LOP SSF (Server Signal Fail)
HOP
AU-AIS SSF (Server Signal Fail)
2.3 Synchronization
1 port: standard
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
In order to avoid timing loop, SSM control should conform below rules.
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.
SSM = SSM =
G.811 G.811
Node1 SSM = Node2 SSM = Node3
G.811 IN OUT G.811
SSM = SSM =
DNU OUT IN G.812L
3) Selected timing source is from extended clock timing source (can not slave to
EXT clock)
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.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.
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.
Traffic management includes the management of transmission, end users and cross
connection.
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
8*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
3*E31(34M) X Y Y Y Y X Y Y Y Y
3*E32(45M) X Y Y Y Y X Y Y Y Y
NOTE:
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
ES Near end errored seconds ITU-T G.826 G.784
SES Near end severely errored seconds ITU-T G.826 G.784
UAS Unavailable seconds 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
ES Near end errored seconds ITU-T G.826 G.784
SES Near end severely errored seconds ITU-T G.826 G.784
UAS Unavailable seconds ITU-T G.826 G.784
HPT 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
LPT 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
UAS Unavailable seconds ITU-T G.826 G.784
(2of2)
MONITOR TYPES DEFINITION SPEC.
LPT 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
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.
Ethernet PM
(1of3)
MONITOR TYPES DEFINITION SPEC.
(2of3)
MONITOR TYPES DEFINITION SPEC.
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.
The total number of packets that RFC1213
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
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
WAN ETH-RxBr Number of good broadcast packets
oadcastPkt received
s
A count of frames received on a RFC1643
ETH-RxFC
particular interface that are an integral
SErrorFra
number of octets in length but do not
mes
pass the FCS check.
(3of3)
MONITOR TYPES DEFINITION SPEC.
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)
Number of packets received that were
ETH-RxPkt
between 128 to 255 octets in length
128to255
(including error packets)
Number of packets received that were
ETH-RxPkt
between 256 to 511 octets in length
256to511
(including error packets)
Number of packets received that were
ETH-RxPkt
between 512 to 1023 octets in length
512to1023
(including error packets)
WAN
Number of packets received that were
ETH-RxPkt
64 octets in length (including bad
64
packets)
Number of packets received that were
ETH-RxPkt
between 65 to 127 octets in length
65to127
(including error packets)
The total number of packets that RFC1213
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.
Encapsulation PM
MONITOR TYPES DEFINITION SPEC.
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
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.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
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.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).
TCA TCA
Threshold
Count period 15min /1 day Count period 15min /1 day CcCount period 15min /1 day
The TCA value of each parameter can be customized. The TCA report can be
disabled as well, by setting the value to 0.
SDH TCA
(1of2)
LAYER PM TYPES 15m TCA THRESHOLD 24h TCA THRESHOLD
(2of2)
LAYER PM TYPES 15m TCA THRESHOLD 24h TCA THRESHOLD
Ethernet TCA
(1of2)
LAYER PM TYPES 15m TCA THRESHOLD 24h TCA THRESHOLD
ETH-RxFCSErrorF
133929000 0-133929000 4294967294 0-4294967294
rames
ETH-RxAlignment
133929000 0-133929000 4294967294 0-4294967294
ErrorFrames
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-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
(2of2)
ETH-RxPkt1024to
10775700 0-10775700 4294967294 0-4294967294
LAN Max
ETH-RxFCSErrorF
133929000 0-133929000 4294967294 0-4294967294
rames
ETH-RxAlignment
133929000 0-133929000 4294967294 0-4294967294
ErrorFrames
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-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
GFP TCA
GFP_RxEXIErrorP
133929000 0-133929000 4294967294 0-4294967294
kts
LAPS TCA
LAPS_RxFCSErro
133929000 0-133929000 4294967294 0-4294967294
rPkts
(2of4)
INDICATION CATEGORY DESCRIPTION FAULT LOCATION DEFAULT CLASS
(3of4)
INDICATION CATEGORY DESCRIPTION FAULT LOCATION DEFAULT CLASS
(4of4)
INDICATION CATEGORY DESCRIPTION FAULT LOCATION DEFAULT CLASS
Ethernet Alarm
(1of2)
FAULT DEFAULT
INDICATION CATEGORY DESCRIPTION
LOCATION CLASS
(2of2)
FAULT DEFAULT
INDICATION CATEGORY DESCRIPTION
LOCATION CLASS
NOTE:
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.
Encapsulation Alarm
FAULT DEFAULT
INDICATION CATEGORY DESCRIPTION
LOCATION CLASS
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
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.
Stretch Time is a specific period for the process to determine if the alarm has been
cleared.
LED on front of rack lights up when alarm is generated/cleared to report the alarm to
the user.
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.
CR (Critical) V V V V V
MJ (Major) V V V V V
MN (Minor) V V V V V
WN (Warning) V
ACO function V
NOTE: V denotes corresponding office alarm in the column will report when
corresponding class alarm in the row occurs.
If you execute ACO (Alarm Cut Off) during alarm occurrence (AB/AL output), the
audible alarm (AB) is silenced; however, AB will be output if another alarm occurs
later.
Usable functions for each user are limited according to user level of each user.
NOTE:
1) O: means the permission of operation
X: means the denial of operation
*: means the user only have the right to operate the lower level user
2) Level 4 System Administrator(Highest)
Level 3 System Maintenance
Level 2 System Operator
Level 1 System Watcher(Lowest)
(1of3)
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
(2of3)
(3of3)
User Level
Command List
Level4 Level3 Level2 Level 1
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,
restorable, lockout threshold, switch holdoff time, delay time of
restore, the forced sending SSM value, receiving SSM value, the
switch state of sending forced SSM value and support of extra
command (such as Lockout, Force, Manual)) O O O O
Set the attributes of pass through clock source (including priority,
restorable, lockout threshold, switch holdoff time, delay time of
restore, the forced sending SSM value, the switch of sending forced
SSM value and support of extra command (such as Lockout, Force,
Manual)) 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
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
FAC LPB
MS-AIS
z STM-1e signal
When Facility loopback is operated AIS signal shall be sent to cross connect side.
STM-1 e
FAC LPB
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
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
TRM LPB
z STM-1e Signal
The signal sent to opposite end is same as the signal returned to local end (cross
connect).
STM-1e
TRM LPB
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.
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
3. EXTERNAL INTERFACES
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
FUNCTIONAL DESCRIPTION
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.2 NMS
z Physical Layer: 10Base-T (Half/10M)
z Connector: RJ-45
z Protocol: TCP/IP
z Width: 482.6 mm
z Depth: 306 mm
External Interfaces
3-2