220 1 Document Optix Metro 1000 Ss42efs

Document code Product name OptiX Metro 1000

Target readers Product version V200R005

Edited by Data Development Dept. Document version

OptiX Metro 1000 SS42EFS Deployment Guide

Drafted by: Qiao Qian and Jin Zhiguo Date: 2004-03-01

Reviewed by: Date:

Reviewed by: Ma Jiantao Date: 2003-04-09

Approved by: Date:

Huawei Technologies Co, Ltd All Rights Reserved

OptiX Metro 1000 SS42EFS Deployment Guide Confidentiality Level:

Internal Use Only

2005-04-13 Huawei Confidential. No disclosure without permission. Page 2 of 54

Revision Records

Date Revised version Description Author


Internal Use Only


Contents

Chapter 1 Overview Introduction.................................................................................................... 8 1.1 Functions .............................................................................................................................. 8

1.1.1 EPL/EVPL Service Function ...................................................................................... 8 1.1.2 EPLAN/EVPLAN Service Function ............................................................................ 8 1.1.3 RSTP.......................................................................................................................... 8 1.1.4 Broadcast Datagram Suppression ............................................................................. 9 1.1.5 LCAS.......................................................................................................................... 9

1.2 Applications........................................................................................................................... 9 1.3 Characteristics of External Interfaces................................................................................... 9

Chapter 2 Board Signal Flow, Alarm and Performance.............................................................. 10 2.1 Signal Flow ......................................................................................................................... 10 2.2 Description of Alarm Reasons ............................................................................................ 10 2.3 Alarms and Reasons .......................................................................................................... 11

2.3.1 Board Alarms............................................................................................................ 11 2.3.2 Ethernet Performance (RMON) Alarm ..................................................................... 16

2.4 Description of Alarm Indicators........................................................................................... 16 2.5 List of Performance Events................................................................................................. 17

2.5.1 SDH Performances .................................................................................................. 17 2.5.2 Ethernet Performances ............................................................................................ 17

Chapter 3 Installation and Usage.................................................................................................. 18 3.1 Hardware Installation .......................................................................................................... 18 3.2 Intra-Board DIP Switch and Jumper Setting....................................................................... 19 3.3 Preparations for Deployment .............................................................................................. 19 3.4 Upgrade Operations ........................................................................................................... 19

Chapter 4 NM Configuration.......................................................................................................... 20 4.1 Board Parameters............................................................................................................... 20 4.2 Configuring Service and Protection Function ..................................................................... 27

4.2.1 Configuring Ethernet Port attributes and Binding Path ............................................ 27 4.2.2 Configuring Ethernet Private Line Service ............................................................... 28 4.2.3 Configuring Ethernet LAN Service ........................................................................... 32

4.3 Configuring Maintenance Function..................................................................................... 34 Chapter 5 Command Lines............................................................................................................ 34

5.1 Command Line Configuration ............................................................................................. 34 5.1.1 Configuration Case .................................................................................................. 34 5.1.2 EPL/EVPL Service Configuration............................................................................. 35 5.1.3 EPLAN/EVPLAN Service Configuration................................................................... 37 5.1.4 MPLS Service Configuration .................................................................................... 41

5.2 Configuration Check ........................................................................................................... 41 5.3 Maintenance Function ........................................................................................................ 41

Chapter 6 Typical Networking, Service and Protection Configuration (Optional)................... 43 6.1 Example 1: Pure Transparent-Transmission Service......................................................... 43

6.1.1 Example and Analysis.............................................................................................. 43 6.1.2 Configuration and Steps........................................................................................... 43 6.1.3 Site Commissioning Method .................................................................................... 44 6.1.4 Troubleshooting........................................................................................................ 45

6.2 Example 2: Transparently Transmitting Convergent Service ............................................. 45 6.2.1 Example and Analysis.............................................................................................. 45 6.2.2 Configuration and Steps........................................................................................... 45


Internal Use Only


6.2.3 Site Commissioning Method .................................................................................... 46 6.2.4 Troubleshooting........................................................................................................ 47

6.3 Example 3: Layer 2 Switching Service ............................................................................... 47 6.3.1 Example and Analysis.............................................................................................. 47 6.3.2 Configuration and Procedures ................................................................................. 47 6.3.3 Site Commissioning Method .................................................................................... 49 6.3.4 Troubleshooting........................................................................................................ 49

Chapter 7 Deployment and Commissioning................................................................................ 50 7.1 Site Commissioning Method ............................................................................................... 50 7.2 Fault Location Method ........................................................................................................ 50

Chapter 8 Acceptance Test ........................................................................................................... 53 8.1 Items, Methods and Indices................................................................................................ 53 8.2 Precautions ......................................................................................................................... 53

Chapter 9 Board Maintenance....................................................................................................... 53 Chapter 10 Appendix...................................................................................................................... 53

10.1 Description of Hardware Version...................................................................................... 53 10.2 List of Board PTP Commands .......................................................................................... 53 10.3 Currently Known Problems ............................................................................................... 53


Internal Use Only


Figure Description

Figure 1 The front panel of the SS42EFS............................................................................... 10

Figure 2 Signal flow of the SS42EFS...................................................................................... 10

Figure 3 The available installation position of the SS42EFS in the Metro 1000..................... 19

Figure 4 Ethernet configuration items of the imanager T2000................................................ 21

Figure 5 T2000 Ethernet service management....................................................................... 21

Figure 6 Ethernet LAN management ...................................................................................... 22

Figure 7 Ethernet test management ....................................................................................... 22

Figure 8 Forwarding filter table management ......................................................................... 23

Figure 9 Spanning tree management...................................................................................... 23

Figure 10 IGMP snooping management ................................................................................. 24

Figure 11 Flow classification management............................................................................. 24

Figure 12 Parameter configuration for local node................................................................... 25

Figure 13 Topology information............................................................................................... 25

Figure 14 Selecting additional functions ................................................................................. 26

Figure 15 CAR management .................................................................................................. 27

Figure 16 LPT management ................................................................................................... 27

Figure 17 Binding VC trunk..................................................................................................... 28

Figure 18 Application of the EPL............................................................................................. 29

Figure 19 Application of EVPL ................................................................................................ 29

Figure 20 Application of Transit............................................................................................... 29

Figure 21 Ethernet LAN service mode.................................................................................... 32

Figure 22 Networking diagram of transparent-transmission services..................................... 43

Figure 23 Transparently transmitting convergent service ....................................................... 45

Figure 24 Transparently transmitting convergent service ....................................................... 47


Internal Use Only


Table of Table Description

Table 1 List of board alarms .................................................................................................... 11

Table 2 Ethernet performance alarms ..................................................................................... 16

Table 3 List of SDH performances .......................................................................................... 17

Table 4 List of Ethernet performances .................................................................................... 17


Internal Use Only


Keyword:

OptiX Metro 1000 SS42EFS Deployment Guide Summary:

OptiX Metro 1000 SS42EFS Deployment Guide Abbreviation list:

None. Reference list:

None.


Internal Use Only


Chapter 1

1.1

1.1.1

1.1.2

Overview Introduction

Functions

EPL/EVPL Service Function

The SS42EFS supports pure transparent transmission and virtual local area network (VLAN) transparent transmission. It fulfills Ethernet private line (EPL)/Ethernet virtual private line (EVPL) service to isolate the data of different users from each other. Besides, the SS42EFS can perform the sharing of a VC trunk through multi-protocol label switch (MPLS) or stack VLAN. That is, if two or more users want to share one VC trunk to transmit Ethernet service data, they can use such labels to isolate these data from each other. (The V1R1 version of the board does not support the MPLS function).

EPLAN/EVPLAN Service Function

The SS42EFS supports EPLAN/EVPLAN services. For the implementation of the EPLAN/EVPLAN services, refer to the relevant standard protocol.

As viewed from the structure, the EPLAN/EVPLAN consists of layer 2 switching and the MPLS. Similar to an ordinary bridge, layer 2 switching consists of several virtual bridges (VBs) corresponding to different users. The data between these VBs are completely isolated from each other. Each VB acts like an independent bridge. The data of different VLANs within one VB are isolated from each other. The major difference between EPLAN and EVPLAN service is that the former does not need the MPLS label to share the VC trunk. That is, the VC trunk of the EPLAN service is occupied by a single VB only. (The V1R1 version of the board does not support the MPLS function).

EFGS单板VB简介.ppt

RSTP

In the network topology with loop, problems may occur like failure to forward the Ethernet data packet, broadcast storm, and multiframes.

To avoid such problems, the SS42EFS uses the rapid spanning tree protocol (RSTP) to detect the network topology. Through the RSTP, the SS42EFS can form a new network logical topology to eliminate loop. In addition, it can detect the changes of the network topology in real time and form a new one.

Compared to the spanning tree protocol (STP), it uses the RSTP function to achieve rapid convergence of the network topology. (The V1R1 version of the board does not support RSTP/STP).

1.1.3


Internal Use Only


1.1.4

1.1.5

1.2

1.3

Broadcast Datagram Suppression

The board software counts the current broadcast datagram flow by the statistical information of the port MAC. If the flow is larger than the preset threshold, the board software will inform the microcode to discard some broadcast datagrams. If the flow is smaller, the board software will inform the microcode to stop discarding them.

The broadcast datagram suppression function is able to prevent the broadcast datagram from affecting normal data service and prevent the network from being attacked.

LCAS

Link capacity adjustment scheme (LCAS) is to expand the virtual concatenation (VC) technology (Remarks: It applies to the VC path only). The LCAS can dynamically adjust service bandwidth without affecting service availability.

If invalid physical channels exist in the VC, the LCAS will shield these channels, while other channels transmit services normally. By this means, a single failure channel will not interrupt services. When the invalid physical channel recovers, the LCAS will use the recovered channel again and restore service bandwidth without any damage. (The V1R1 version of the board does not support LCAS).

Applications

The SS42EFS applies to telecommunication fields like Ethernet service access, bandwidth management and Ethernet service layer 2 switching. Most important of all, it solves FE-to-FE and FE-to-GE convergence as well as interworking with the EGS, the Gigabit Ethernet transparent transmission board (EGT), and the fast Ethernet transparent transmission board (EFT).

Specific applications cover:

• Private line;

• Private network;

• Non-management residential communities;

• Scattered-management residential communities;

• Centralized-management residential communities.

Characteristics of External Interfaces

There are two indicators on the front view of the SS42EFS front panel. The green one is the running indicator and the red one is the alarm indicator.

The front panel provides 4-channel FE electrical interfaces.


Internal Use Only


Figure 1

Chapter 2

2.1

The front panel of the SS42EFS

Board Signal Flow, Alarm and Performance

Signal Flow

LXT9785NP3400PL215NP3400

PL215

4 x FERGGI

XCS

Figure 2

2.2

Signal flow of the SS42EFS

One PL215 supports eight VC-4s, divided into Channel A and Channel B. The Metro1000 EFS only supports four VC-4s (the V1R1 version supports Channel A, that is, two VC-4s), the latter two VC-4s of Channel A and Channel B each. The maximum bandwidth is 622M. Any Vc-4 can be configured as VC-3. However, only the last VC-4 in each channel can be configured as VC-12. Therefore, one SS42EFS supports either 12 x VC-3s or 6 x VC-3s plus 126 x VC-12s at most. One VC trunk can bind either Channel A or Channel B.

Description of Alarm Reasons

The SS42EFS has not only ordinary SDH alarms but also the special Ethernet alarms.

ETH_LOS It means the Ethernet port link loss alarm. When the SS42EFS detects that the indication port status of the link register on the PHY chip turns to link down, the ETH_LOS alarm is reported.

RMON The SS42EFS counts the transceived data packet at the Ethernet port in real time. When a statistical value exceeds the configured threshold, the RMON appears.


Internal Use Only


2.3

2.3.1

Table 1

Alarms and Reasons

Board Alarms

List of board alarms

Code Name Alarm description

Sn Alarm reason Severity Alarm processing

ETH_LOS

Ethernet interface connection loss alarm

Detect the connection status of the Ethernet interface.

0xEB (1) Too-large Ethernet cable interference; (2) Ethernet interface failure; (3) Ethernet twisted-pair broken; (4) PHY chip damaged; (5) Work modes at both sides mismatched

Major (1) Report the alarm to the NE. (2) If LPT is configured, enable LPT. (3) If the SPT is configured, enable the SPT topology for reshaping.

T_LOS

Loss of the receive signal from the backplane side

Detect the receive signal for the use of bus switching

0X0002 This alarm appears when the bus sent from the cross-connect board to the line board has no valid signal.

Report it to the NE.

AU_AIS

AU alarm indication

Detect the AIS status of the AU pointer for the use of bus switching

0x0048 Detect the AIS status of the AU pointer for the use of bus switching


TU_AIS_VC3 TU alarm indication

Detect the AIS and LOP status of the TU pointer.

0XF871 It is incurred by unavailable indication of higher-level alarms or signals.

Critical Report it to the NE.

TU_LOP_VC3 TU pointer loss


0XF873 Detect the illegal pointer value.


LP_UNEQ_VC3 No payload indication of the lower order path

Payload type of the low-order path is knowable.

0XF86F The path has no payload or is set to the not-in-use status.

Minor Report it to the NE.

LP_TIM_VC3

Lower order path tracking identification mismatch

The lower order path tracking byte is monitorable.

0XF86D The received J1 byte is different from the J1 to be received. The service configuration might be faulty.


LP_SLM_VC3

Lower order path signal identification mismatch

Payload type of lower-order path is monitorable.

0XF86B The received signal identification does not match the one to be received. The service configuration might be faulty.


LP_RDI_VC3

Lower order path remote defect indication

The local station displays the receive signal failure

0XF867 Detect that the previous station fails to receive signals.



Internal Use Only




generated in the previous station.

LP_REI_VC3

Lower order path remote error indication

The local station displays the bit errors generated in the previous station.

0XF869 Detect that the previous station has bit errors.


B3_EXC_VC3

Excessive B3 errors

The alarm appears according to the detected number of bit errors and preset error threshold.

0XF859 The detected B3 errors exceed the threshold.


B3_SD_VC3

B3 errors degraded


0XF85B The detected B3 errors exceed the preset degraded threshold.


ILL_SQ_VC12

VC sequent number indication mismatched

Report the alarm when the VC multiframe number indication is mismatched.

0xf863 VC sequent number indication mismatched


ILL_SQ_VC3

VC sequent number indication mismatched


0xf864 VC sequent number indication mismatched


ILL_MFI_VC3

VC multiframe number indication mismatched


0xf861 VC multiframe number indication mismatched


ILL_MFI_VC12

VC multiframe number indication mismatched


0xf860 VC multiframe number indication mismatched


TU_AIS_VC12 TU alarm indication signal


0XF870 Incurred by higher-level alarms or indication of signal invalid


TU_LOP_VC12 TU pointer Detect the AIS 0XF872 Detect an illegal pointer Report it to


Internal Use Only




loss and LOP status of the TU pointer.

value. the NE.

LP_UNEQ_VC12

No payload indication of the lower order path

The payload type of the lower-order path is knowable.

0XF86E The path is configured with no service or is set to the non-use status.


LP_TIM_VC12

Lower-order path trace identifier mismatch

The slower-order path tracing identification is monitorable.

0XF86C The received J2 is different from the one to be received. The fault may lie in the incorrect service configuration.


LP_SLM_VC12

Lower-order path signal mismatch

The service type of the lower-order path is monitorable.

0XF86A The received signal label different from the one to be received. The fault may lie in the incorrect service configuration.


LP_RDI_VC12

Lower-order path remote receive failure indication

The local station displays the receive signal failure generated in the previous station.

0XF866 Detect that the previous signal failed.


LP_REI_VC12

Lower order path-remote error indication

The local station displays the bit errors generated in the previous station.

0XF868 Detect that the previous station has bit errors.


LP_RFI

Lower order path remote defect indication

The local station displays the signal failure generated in the previous station.

0X0030 Detect that the previous station fails to receive signals.


BIP_EXC

Excessive BIP errors


0X00B7 The detected BIP2 errors exceed the excessive-error threshold.


BIP_SD

BIP error degraded

BIP error degraded

0X00B6 The alarm appears according to the detected number of bit errors and preset error threshold.


W_R_FAILURE

Failure in writing-reading register

Monitor the writing-reading status of the important register in the board.

0X0063 Register check error Report it to the NE.


Internal Use Only




HARD_BAD

Bad hardware This alarm appears when the power, clock, phase-lock loop, and chips fail.

0X00EC Alarm causes are categorized into: (1) The power module works abnormally. (2) The board is not reliably installed (the board is not reliably connected to the backplane. For example, it is not inserted tightly). (3) The 38M system clock 1 is abnormal. (4) The 38M system clock 2 is abnormal. (5) The 2M clock source is abnormal. (6) The digital phase-lock loop is abnormal. (7) The 38M service clock is lost. (8) The bus is abnormal. (9) The TPS board is abnormal. (10) The main clock crystal oscillator stops oscillating. (11) The frequency deviation of the main crystal oscillator is too large. (12) The standby crystal oscillator stops oscillating. (13) The processor (CPU/DSP/coprocessor) is faulty. (14) The memory device is faulty. (15) The complex programmable logical device (CPLD) is faulty. (16) The SDH device is faulty. (17) The data communication device is faulty. (18) The clock device is faulty. (19) The interface component is faulty. (20) The power device is faulty. (21) Other faults (22) The analog phase-lock loop is abnormal. When para[0] belongs to the power device error,

Major Report it to the NE.


Internal Use Only




para[1] = 0xff, para[2] = 0xff Further division: 0x0001/5V (main) 0x0002/3.3V (main) 0x0003/2.5V 0x0004/1.8V 0x0005/1.5V 0x0006/-5V 0x0007/3.3V (electrical interface board) 0x0008/5V (standby) 0x0009/3.3V (standby) When para[0] belongs to the clock device error, para[1] = 0xff, para[2] = 0xff Further division: 0x0001/669M 0x0002/622M 0x0003/155M 0x0004/125M 0x0005/104M 0x0006/100M 0x0007/77M 0x0008/50M 0x0009/38M (this board) 0x000a/38MA 0x000b/38MB 0x000c/19M 0x000d/2M When para[0] = 22 and the analog phase-lock loop is abnormal, para[1] = 0xff, para[2] = 0xff. Further division: 0x0001/669M 0x0002/622M 0x0003/155M 0x0004/38M 0x0005/2M

LOOP_ALM

Loop The alarm appears when the board is in the loop status.

0X00F0 The board is set to loop status.


PROTOCOL_MM

Protocol mismatched

This alarm appears when the board finds the protocol mismatched.

0XF855 The board finds the protocol mismatched.


FCS_ERR

FCS check error

This alarm appears in the case of the FCS check error.

0XF857 FCS check error Report it to the NE.

VC_DELAY_TL Too-large VC delay

This alarm appears when the board finds too large VC

0XF832 Too-large concatenation delay



Internal Use Only




delay.

LCAS_BAND_DECREASED

Enable the LCAS bandwidth protection function. The VC-Trunk service bandwidth is reduced.

Enable the LCAS bandwidth protection function. The VC-Trunk service bandwidth is reduced.

0XF876 LCAS bandwidth protection function enabled and VC-Trunk service bandwidth reduced.


2.3.2

Table 2

Ethernet Performance (RMON) Alarm

Ethernet performance alarms

Alarm event identifier Alarm ID Full name of alarm event DropOv 0x129 Lost-packet events over the upper alarm threshold DropUd 0x12a Lost-packet events below the lower alarm threshold RxBadOctOv 0x12b Received bad packet bytes over the upper alarm threshold RxBadOctUd 0x12c Received bad packet bytes below the lower alarm threshold TxBadOctOv 0x12d Transmitted bad packet bytes over the upper alarm threshold TxBadOctUd 0x12e Transmitted bad packet bytes below the lower alarm threshold ColOv 0x12f Detected bursts over the upper alarm threshold ColUd 0x130 Detected bursts below the lower alarm threshold AligErrOv 0x131 Align errors over the upper alarm threshold AligErrUd 0x132 Align errors below the lower alarm threshold FCSErrOv 0x133 Check errors over the upper alarm threshold FCSErrUd 0x134 Check errors below the lower alarm threshold LateColOv 0x135 The number of collisions detected when transmitting the

succeeding timeslot over the upper alarm threshold LateColUd 0x136 The number of collisions detected when transmitting the

succeeding timeslot below the lower alarm threshold ExcColOv 0x137 Amount of frames not transmitted succeeded due to continuous

collisions over the upper alarm threshold ExcColUd 0x138 Amount of frames not transmitted succeeded due to continuous

collisions below the lower alarm threshold DefTxOv 0x139 Frames to be delayed over the upper alarm threshold DefTxUd 0x13a Frames to be delayed below the lower alarm threshold CarErrOv 0x13b Times of detected carrier errors over the upper alarm thresholdCarErrUd 0x13c Times of detected carrier errors below the lower alarm threshold

2.4 Description of Alarm Indicators

Severity level: 3–critical, the red indicator flashing three times every second 2–major, the red indicator flashing twice every second 1–minor, the red indicator flashing once every second 0–warning, the red indicator not flashing


Internal Use Only


2.5

2.5.1

Table 3

List of Performance Events

SDH Performances

List of SDH performances

B3CNT B3 error count The error counter detects the error information. Report the alarm.

0x00c9 Count parity check bit errors

HPFEBE Higher-order path remote error indication count

The path remote error indication count reflects the quantity of B3 errors in the relevant path of the opposite-end board. It is important to monitor the entire segments.

0x00ca Return the remote error indication of the higher-order path through G1 byte.

LPBIP2CNT Lower-order path bit error

Count lower-order path bit errors. 0x00D9 The board detects that the lower-order path has bit errors.

LPFEBE Lower-order path remote background block error

Count lower-order path remote errors.

0x00DA The board detects that the lower-order path has remote bit errors.

XCSTMP Environmental temperature of the board

The board can detect the working environmental temperature of its key chip.

0x00F5 The working environmental temperature of the board detected by the board

2.5.2

Table 4

Ethernet Performances

List of Ethernet performances 1 1 (0x01) Pkts64Octets The total packets received in the length of 64 bytes 1 2 (0x02) Pkts65to127Octets The total packets received in the length of 65 – 127 bytes 1 3 (0x03) Pkts128to255Octets The total packets received in the length of 128 - 255 bytes 1 4 (0x04) Pkts256to511Octets The total packets received in the length of 256 -511 bytes1 5 (0x05) Pkts512to1023Octets The total packets received in the length of 512 -1023 bytes 1 6 (0x06) Pkts1024to1518Octets The total packets received in the length of 1024 -1518 bytes1 39 (0x27) Pkts1519to1522Octets The total packets received in the length of 1519 - 1522 bytes 1 7 (0x07) TranPkts64Octets The total packets transmitted in the length of 64 bytes 1 8 (0x08) TranPkts65to127Octets The total packets transmitted in the length of 65 - 127 bytes1 9 (0x09) TranPkts128to255Octets The total packets transmitted in the length of 128 -255 bytes1 10 (0x0a) TranPkts256to511Octets The total packets transmitted in the length of 256 - 511

bytes 1 11 (0x0b) TranPkts512to1023Octets The total packets transmitted in the length of 512 -1023

bytes 1 12 (0x0c) TranPkts1024to1518Octets The total packets transmitted in the length of 1024 - 1518

bytes 1 40 (0x28) TranPkts1519to1522Octets The total packets transmitted in the length of 1519 -15122

bytes Group 2: transceiver performance event (total: 17 items)

2 13 (0x0d) InUcastPkts The unicast packets received 2 14 (0x0e) InMulticastPkts The multicast packets received 2 15 (0x0f) InBroadcastPkts The broadcast packets received 2 16 (0x10) OutUcastPkts, The unicast packets transmitted 2 17 (0x11) OutMulticastPkts The multicast packets transmitted 2 18 (0x12) OutBroadcastPkts The broadcast packets transmitted 2 19 (0x13) InPauseFrames The Pause flow control frames received 2 20 (0x14) OutPauseFrames The Pause flow control frames transmitted


Internal Use Only


2 21 (0x15) DropEvents The times of packet losses caused by FIFO overflow 2 22 (0x16) UndersizePkts The number of undersized packets 2 23 (0x17) OversizePkts The number of oversized packets 2 24 (0x18) Fragments The number of fragments 2 25 (0x19) Jabbers The number of jabbers 2 26 (0x1a) InOctets The total count of normal packet bytes received 2 27 (0x1b) OutOctets The total number of normal packet bytes transmitted 2 28 (0x1c) BadRecvOcts The number of bad packets received 2 29 (0x1d) badTranOcts The number of bad packets transmitted Group 3 (not supported at present)

3 30 (0x1e) Collisions The number of collisions detected 3 31 (0x1f) AlignmentErrors The number of alignment errors 3 32 (0x20) FCSErrors The number of check errors 3 33 (0x21) SingleCollisionFrames The number of frames correctly transmitted after a single

collision 3 34 (0x22) MultipleCollisionFrames The number of frames correctly transmitted after multiple

collisions 3 35 (0x23) LateCollisions The number of collisions detected within one time slot after

transmission 3 36 (0x24) ExcessiveCollisions The number of frames unsuccessfully transmitted due to

continuous collisions 3 37 (0x25) DeferredTransmissions The number of frames deferred in transmission 3 38 (0x26) CarrierSenseErrors The number of carrier collisions detected 3 41 (0x29) RxTxPkts64Octets The total packets transceived in the length of 64 bytes 3 42 (0x2a) RxTxPkts65to127Octets The total packets transceived in the length of 65-127 bytes 3 43 (0x2b) RxTxPkts128to255Octets The total packets transceived in the length of 128 – 255

bytes 3 44 (0x2c) RxTxPkts256to511Octets The total packets transceived in the length of 256 - 511

bytes 3 45 (0x2d) RxTxPkts512to1023Octets The total packets transceived in the length of 512 -1023

bytes 3 46 (0x2e) RxTxPkts1024to1518Octets The total packets transceived in the length of 1024 – 1518

bytes 3 47 (0x2f) RxTxPkts1519to1522Octets The total packets transceived in the length of 1519 -1522

bytes

Chapter 3

3.1

Installation and Usage

Hardware Installation

The SS42EFS occupies a system bandwidth with the 4 x VC-4 capacity. It can be installed in Slot IU1, IU2, or IU3 slot in the Metro1000. Figure 3 shows the installation position of the SS42EFS in the Metro 1000.

IU 1IU 2IU 3

IU4

SCB

FAN POI

IU1IU2IU3


Internal Use Only


Figure 3

3.2

3.3

3.4

The available installation position of the SS42EFS in the Metro 1000

Intra-Board DIP Switch and Jumper Setting

The jumper inside the board is actually the board reset button.

Preparations for Deployment

Before the deployment, ensure the following configuration relation of software versions:

Board software: 1.20 or later

NE software: 4.02.06.31 T03 or later

BIOS: 201 or later

PL215 version: 100 or later

Control logical version: 100 or later

SCC: SS43SCB or later

NM: iManager T2000 V100R006 or later

Prepare the upgrade software Navigator5.50 or later for the board and the NE software and the computer connected to the NE.

Upgrade Operations

All of board software, expansion BIOS, control logic, and PL215 logic can be upgraded through the Navigator. The Navigator version shall be later than 5.50. The window is shown below (supposing the SS42EFS is inserted in Slot 3).


Internal Use Only


Four files of the board can be uploaded through the Navigator: Board software ss42efs10.dlb; Board software configuration file ne.ini; Board control logic ctl.pga; PL215 mapping logic pl215.pga.

Select “Board” to upload ss42efs10.dlb and ne.ini. Select “Fpga” to upload ctl.pga and PL215.

Note: 1)

2)

3)

Chapter 4

4.1

It will take a long time to upload the large-capacity ss42efs10.dlb and pl215.pga. When the progress bar reaches 99%, the uploading status will become “S_Idle” instead of “OK”. In this case, wait about 0.5m and then reset the board. By now, the two files shall have been uploaded. You need not upload them again. As there is no sequence requirement for uploading files, it is done when they are uploaded completely (we recommend you to upload ne.ini at last). When you upload new board software, you need not delete the old one.

NM Configuration

Board Parameters

The Ethernet configuration covers the following items shown in the figure.


Internal Use Only


Figure 4

1)

Ethernet configuration items of the imanager T2000

Figure 4 provides the menu for setting the data Ethernet board. Select one directory to set the corresponding attribute as follows.

Ethernet interface board management

Figure 5

2)

T2000 Ethernet service management

The above figure lists Ethernet service configurations. The EFS is used to configure transparent-transmission services.

Ethernet LAN management


Internal Use Only


Figure 6

3)

Ethernet LAN management

Ethernet test management

Figure 7

4)

Ethernet test management

Forwarding filter table management


Internal Use Only


Figure 8

5)

Forwarding filter table management

Spanning tree management

Figure 9

6)

Spanning tree management

IGMP snooping management


Internal Use Only


Figure 10

7)

IGMP snooping management

Flow classification management

Figure 11

8)

Flow classification management

Parameter configuration for local node


Internal Use Only


Figure 12

9)

Parameter configuration for local node

Topology information

Figure 13

10)

Topology information

CAR management Select system–>system setting–>Customize Function–>Show Advanced Manu, as follows.


Internal Use Only


Figure 14 Selecting additional functions


Internal Use Only


Figure 15

11)

CAR management

LPT management (The V1R1 of the board does not support LPT)

Figure 16

4.2

4.2.1

LPT management

Configuring Service and Protection Function

Configuring Ethernet Port attributes and Binding Path

(1) In the main menu, select [Configuration/Ethernet Configuration].

(2) Select an operation object (Ethernet board) at the lower left. Click the button and set the relevant attributes on the right side of the window.

(3) To query the selected Ethernet interface board, click <Query>. The desired information returns.

(4) Set the parameters of each interface port like “TAG” and “VLAN ID”.

(5) Click <Apply>.

(6) Select the “Binding path” tab. Click <Query>. The binding path information of the internal port on the selected Ethernet interface board returns.

(7) Click <Configuration>. Enter the “Binding Path Configuration” window.

(8) Select the configurable port, level, direction, VC4 and timeslot of the optional binding path. Click the button.

(9) To delete or modify a binding path, select it and click the button.


Internal Use Only


(10) To configure other binding paths, click <Apply>.

Repeat Steps 8 ~ 10.

After finishing the configurations, click <OK> to close the “Binding Path Configuration” window.

Select “External port”. Click <Query>. The port information of the external port on the selected Ethernet interface board returns. Set the parameters of each external port like “TAG” and “VLAN ID”.

Click <Apply>.

Figure 17

4.2.2

Binding VC trunk

Configuring Ethernet Private Line Service

Introduction

The Ethernet private line service is similar to the Ethernet transparent-transmission service except for their operation object. The Ethernet private line service is used to configure the EFS of all multi-service transmission platform (MSTP).

Ethernet private line services include: EPL; EVPL; Tansit.


Internal Use Only


EPL is a simple service of the private line services. It can fulfill point-to-point and point-to-multipoint connection for service. However, the VC trunk port each service takes up is independent from each other, as shown in Figure 18.

NE 2

A A'

NE 1 NE 3

B

B'

VCTRUNCK B

VCTRUNCK A

Figure 18 Application of the EPL

The difference between the EVPL and the EPL service is whether the EVPL uses a label, as shown in Figure 19. EPL can be regarded as one special application of EVPL.

NE 2

A A'

NE 1 NE 3

B

B'

VCTRUNCK A

Figure 19 Application of EVPL

Transit is used to fulfill MPLS on the MPLS core network. It is applied to the case where the Ethernet service passes through an NE, as shown in Figure 20.

NE 2A A'Tunnel VC

16 25

P P

Tunnel VC30 25

NE 1 NE 3

Figure 20

1) 2) 3) 4)

Application of Transit

Like the configuration of the asynchronous transfer mode (ATM), configuration of Ethernet private line service covers the following two parts:

Configuration of Ethernet service itself; Configuration of SDH service.

Only the latter part is introduced here.

Brief procedures: Complete the configurations at the SDH layer. Set the VC-4 port of the Ethernet board to the SDH NNI. Install the Ethernet interface board. Create the Ethernet private line.

Detailed procedures:


Internal Use Only


1)

2)

3) 4)

Completing the configurations at the SDH layer For more information, refer to imanager T2000V100R006 Operation Manual.

Setting the VC-4 port of the Ethernet board to the SDH NNI For more information, refer to imanager T2000V100R006 Operation Manual.

Installing the Ethernet interface board Creating the Ethernet private line

In the main menu, select [Configuration/Ethernet Configuration/Ethernet Interface Management].

Select an operation object (Ethernet board) at the lower left. Click the button and set the relevant attributes on the right side of the window.

Select “Ethernet Private Line/New” and the relevant window is displayed.


Internal Use Only


Select service type, direction, source/sink port and VLAN ID, Tunnel, and VC.

In “Port Attributes”, set Port Type, Enable Port, encapsulation format, and TAG Flag.

Click <Configuration>. The “Binding Path Configuration” window is displayed.

Select the configurable port, level, direction, VC4, and timeslot of the optional binding path. Click the button.

To delete or modify a binding path, select it and click the button. To configure other binding paths, click <Apply>. Repeat Steps 7 ~ 9. After

finishing the configuration, click <OK> to close the “Binding Path Configuration” window.

To configure other Ethernet private line services, click <Apply>. Repeat Steps 4 ~ 10. After finishing the configuration, click <OK> to close the “Binding Path Configuration” window.

Note: (1) In Step 4, before you select EVPL and Transit, make sure to select “Display Shared

Service”. (2) In Step 4, it is forbidden to set Tunnel and VC Flag for EPL. (3) If you select service type as EPL, you can only select PE after “Port Type”. If you select

Transit, you can only select P after “Port Type”. (4) In Step 5, only when the port attributes is P can you select the encapsulate format. (5) Transit can only swap Tunnel labels.


Internal Use Only


4.2.3 Configuring Ethernet LAN Service

Background

The Ethernet LAN service is similar to the Ethernet layer 2 switching service except for their operation object. The Ethernet LAN service is used to configure the EFS of all MSTPs. In addition to layer 2 switching service, the Ethernet LAN service adds MPLS or Stack VLAN protocol processing to fulfill fast forwarding and VC trunk bandwidth sharing.

Logically, the entire Ethernet LAN can be regarded as a huge switch. A user can access a switch at any place of the LAN. The port of this switch allows layer 2 protocols like STP and IGMP Snooping.

VB

LSP

Physical port

Physical port

Physical portLogical portPhysical port

Physical port

Physical port

Logical port

Logical portLogical port

Logical port

Logical port

Figure 21 Ethernet LAN service mode

Data are sent to the VB through the physical ports and layer 2 switching processed. Through the MAC address table, the data are sent outside the logical ports. Outlet logical ports are connected to the label switch paths (LPSs) that encapsulate the data before sending them out of the physical ports.

Note: Label switched path (LSP) is a path with source and sink ports. It is configured with the label.

It decides the relevant operations and data outlets.

At present, Ethernet LAN service is limited to a single station. The Ethernet service on the entire network is transmitted through private lines.

Like the configuration of the ATM, configuration of Ethernet LAN service covers the following two parts:

Configuration of Ethernet service itself; Configuration of SDH service.

Only the latter part is introduced here.

Brief procedures: 1) 2) 3) 4) 5) 6)

Configure the SDH layer. Set the VC-4 port of the Ethernet board to the SDH NNI (optional). Install the Ethernet interface board (optional). Create the Ethernet LAN service. Create VLAN. Configure the aging time (optional).

Detailed procedures:


Internal Use Only


Complete the configurations at the SDH layer.

For more information, refer to Online Help.

1) Create Ethernet LAN service. a. In the main menu, select [Configuration/Ethernet Configuraiton/Ethernet Service Management].

b. Select an operation object (Ethernet board) at the lower left. Click the button and set the relevant attributes on the right side of the window.

c. In the “Ethernet Private Line Service” optional tab, click <New>. The window for creating Ethernet LAN service is displayed.

d. Set VB ID and VB name.

e. Click <VB Mount Port> and the relevant window is displayed.

f. Select the desired port. Click the button.

g. Click <OK> to close the “VB Mount Port Configuration” window.

h. In “VB Mount Port”, you can set “Mount Port”, “Port Type”, “encapsulation Format”, “Uplink Tunnel”, “Uplink VC”, “Downlink VC”, “Downlink Tunnel’, “Enable Port”.

j. Click <Configuration>. The “Binding Path Configuration” window is displayed.

k. Select a configurable port, level and direction, and time slot. Click the button.

l. To configure the binding path, click <Apply>. Repeat Step k. After finishing the configuration, click <OK> to close the “Binding Path Configuration” window.

m. To configure other Ethernet LAAN services, click <Apply>. Repeat Steps 4 ~ 11. After finishing the configuration, click <OK> to close the “Create Ethernet LAN service” window.


Internal Use Only


n. Click <Apply>. 2)

3)

4.3

Chapter 5

5.1

5.1.1

Create VLAN. For more information, refer to “Forwarding filter table management” in Figure 5.

Configure the aging time (optional).

Configuring Maintenance Function

Command Lines

Command Line Configuration

Configuration Case

:cfg-init<sysall>; //Clear all logical systems.

:cfg-set-nepara:device=sbs155a:nename="NE1" //NE parameters

:cfg-create-board:3,efs:11,oi4:9,x42:15,stg:18,ohp2 //Create a board.

:cfg-create-lgcsys:sys1&sys2 //Create a logical system.


Internal Use Only


5.1.2

I.

:cfg-set-attrib<sys1>:622:2f:bi:nopr:tm:line //Set the attributes of the logical system.

:cfg-set-attrib<sys2>:622:2f:bi:nopr:tm:line

:cfg-set-gutumap<sys1>:gw1&&gw4,11,oi4,0//Set the binding relation between the logical system and the physical board.

:cfg-set-gutumap<sys2>:gw1&&gw4,3,efs,0

:cfg-set-xcmap<sys1&sys2>:xlwork,9,x42

:cfg-init-slot<sysall>

:cfg-create-vc12:sys2,gw2,1&&63,sys1,gw2,1&&63//Set the mapping relation of logical systems.

:cfg-create-vc12:sys1,gw2,1&&63,sys2,gw2,1&&63

:cfg-checkout

EPL/EVPL Service Configuration

Configure the EPL service when a single user takes up the VCTRUNK

The EPL service is the traditional point-to-point pure transparent-transmission service, applied to the case where a user has only two access points on an entire transmission network. Suppose the user service is accessed at port 2, the accessed datagrams are all Tag packets, the access bandwidth is 2M, the peak is 3M, and the released SDH bandwidth is 2M:

:ethn-cfg-add-link:3,1,ip2,0xffff,vctrunk1; //Slot 3, link ID = 1, access to port 2, all VLANs sent to VCTRUNK1

:ethn-cfg-add-link:3,2,vctrunk1,0xffff,ip2; //link ID = 2, access to VCTRUNK1, sent to port 2

:ethn-cfg-add-vctrunkpath:3,vctrunk1,bi,vc12,1,1; //VCTRUNK1 binds a bidirectional VC12 numbered 1

:ethn-cfg-set-tag:3,ip2&vctrunk1,hybrid; //Set port 2 and VCTRUNK1 to hybrid port (defaults to Tag port )

:ethn-cfg-create-car:3,1; //Set CAR ID to 1.

:ethn-cfg-set-carbindvlan:3,ip2,0xffff,1; //Port-based CAR

:ethn-cfg-set-carpara:3,1,2048,0,3072,0; //Set the parameter of No.1 CAR in Slot 3: CIR = 2M, CBS = 0K, PIR = 3M, MBS = 0K

:ethn-cfg-set-caren:3,1,enable; //Enable CAR

:ethn-cfg-set-fcmode:3,ip2,enable; //Enable flow control (optional)

:ethn-cfg-set-portenable:3,ip2,enable; //Enable port.


Internal Use Only


II.

III.

Confiugre the EVPL service when two users with different VLAN IDs share the VCTRUNK

This kind of service applies to users with small traffic and same access stations. By sharing the SDH bandwidth, the users can save the rent for the line. However, the VLAN IDs of their datagrams must vary. Suppose user services are accessed at ports 2 and 3 respectively, access datagrams are Tag packets, the access bandwidth is 1M, and the leased SDH bandwidth is 2M:

:ethn-cfg-add-link:3,1,ip2,2,vctrunk1; //Uplink: slot 3, link ID = 1, access to port 2, VLAN2, sent to VCTRUNK1

:ethn-cfg-add-link:3,2,vctrunk1,2,ip2; //Downlink: link ID = 2, access to VCTRUNK1, sent to port 2

:ethn-cfg-add-link:3,3,ip3,3,vctrunk1; //Uplink: slot 3, link ID = 3, access to port 3, VLAN3, sent to VCTRUNK1

:ethn-cfg-add-link:3,4,vctrunk1,3,ip3; //Downlink: link ID = 4, access to VCTRUNK1, sent to port 3

:ethn-cfg-add-vctrunkpath:3,vctrunk1,bi,vc12,1,1; //VCTRUNK1 binds a bidirectional VC12 numbered 1.

:ethn-cfg-set-tag:3,ip2&ip3&vctrunk1,tag; //Set ports 2, 3 and VCTRUNK1 to Tag port.

:ethn-cfg-create-car:3,1&2; //Set CAR ID to 1 and 2.

:ethn-cfg-set-carbindvlan:3,ip2,2,1; //CAR based on port + VLAN

:ethn-cfg-set-carpara:3,1,1024,0,1024,0; //Set the parameters of No.1 CAR in Slot 3: CIR = 1M, CBS = 0K, PIR = 1M, MBS = 0K



:ethn-cfg-set-caren:3,1&2,enable; //Enable CAR

:ethn-cfg-set-portenable:3,ip2&ip3,enable; //Enable port

Configure the EVPL service when two users with the same VLAN ID share the VCTRUN

This kind of service applies to users with small traffic and same access stations. By sharing the SDH bandwidth, the users can save the rent for the line. No requirements are needed for user data. Suppose user services are accessed at ports 2 and 3 respectively, access datagrams are Tag packets, the access bandwidth is 1M, and the leased SDH bandwidth is 2M:

:ethn-cfg-set-porttype:3,ip2&ip3,pe; //Set ports 2 and 3 to PE type.

:ethn-cfg-set-porttype:3,vctrunk1,p; //Set VCTRUNK1 to P type.

:ethn-cfg-add-ingresslsp:3,1,ip2,0xffff,55,23,vctrunk1; //Uplink: slot 3, lsp ID = 1, access to port 2, VLAN not distinguished, Tunnel label = 55, VC label = 23, sent to VCTRUNK1


Internal Use Only


5.1.3

I.

:ethn-cfg-add-egresslsp:3,2,vctrunk1,55,23,ip2; //Downlink: lsp ID = 2, access to VCTRUNK1, Tunnel label = 55, VC label = 23, sent to port 2

:ethn-cfg-add-ingresslsp:3,3,ip3,0xffff,56,24,vctrunk1; //Uplink: slot 3, lsp ID = 3, access to port 3, VLAN not distinguished, Tunnel label = 56, VC label = 24, sent to VCTRUNK1

:ethn-cfg-add-egresslsp:3,4,vctrunk1,56,24,ip3; //Downlink: lsp ID = 4, access to VCTRUNK1, Tunnel label = 56, VC label = 24, sent to port 4

:ethn-cfg-add-vctrunkpath:3,vctrunk1,bi,vc12,1,1; //VCTRUNK1 binds a bidirectional VC12 numbered 1.

:ethn-cfg-set-tag:3,ip2&ip3,hybrid; //Set ports 2 and 3 to hybrid port.

:ethn-cfg-set-vlan:3,ip2,2,7; //Set the default VLAN ID of port 2 to 2 at the priority level of 7.

:ethn-cfg-set-vlan:3,ip3,3,7; //Set the default VLAN ID of port 3 to 3 at the priority level of 7.

:ethn-cfg-create-car:3,1&2; //Set CAR ID to 1 and 2.





:ethn-cfg-set-caren:3,1&2,enable; //Enable CAR

:ethn-cfg-set-portenable:3,ip2&ip3,enable; //Enable port.

EPLAN/EVPLAN Service Configuration

Configure the EPLAN service when a single user takes up the VCTRUNK.

This service supports local layer 2 switching of user data packet. Suppose use data are accessed at ports 2 and 3 respectively and sent uplink to VCTRUNK1:

:ethn-cfg-create-vb:3,1,"vb1"; //Create VB.

:ethn-cfg-add-ingressvblink:3,1,ip2,1,lp1; //Uplink: Link ID = 1, from port 2 to logical port 1 of No.1 VB

:ethn-cfg-add-egressvblink:3,2,1,lp1,ip2; //Downlink: Link ID = 2, from logical port 1 of No.1 VB to port 2

:ethn-cfg-add-ingressvblink:3,3,ip3,1,lp2; //Uplink: Link ID = 3, from port 3 to logical port 2 of VB 1

:ethn-cfg-add-egressvblink:3,4,1,lp2,ip3; //Downlink: Link ID = 4, from logical port 2 of VB 1 to port 3

:ethn-cfg-add-ingressvblink:3,5,vctrunk1,1,lp3; //Uplink: Link ID = 5, from VCTRUNK1 to logical port 3 of VB 1


Internal Use Only


II.

:ethn-cfg-add-egressvblink:3,6,1,lp3,vctrunk1; //Downlink: Link ID = 6, from logical port 3 of VB 1 to VCTRUNK1

:ethn-cfg-add-vlanporttab:3,1,2,3,lp1&&lp3; //Configure the VLAN filter table: Three logical ports of No.1 VB belong to VLAN2.

:ethn-cfg-add-vctrunkpath:3,vctrunk1,bi,vc12,2,1&2; //VCTRUNK1 binds two bidirectional VC12s numbered 1 and 2.

:ethn-cfg-create-car:3,1&2; //Configure CAR ID as 1 and 2.

:ethn-cfg-set-carbindvlan:3,ip2,2,1; //CAR based on port +VLAN

:ethn-cfg-set-carpara:3,1,2048,0,2048,0; //Set the parameters of No.1 CAR in Slot 3: CIR = 2M, CBS = 0K, PIR = 2M, MBS = 0K.

:ethn-cfg-set-carbindvlan:3,ip3,2,2; //CAR based on port +VLAN


:ethn-cfg-set-caren:3,1&2,enable; //Enable CAR.

:ethn-cfg-set-portenable:3,ip2&ip3,enable; //Enable port.

Confiugre the EVPLAN service when two users with different VLAN IDs share the VCTRUNK

Suppose data of User 1 access to ports 2 and 3, data of User 2 access to ports 4 and 1, using different VLANs, both sent uplink to VCTRUNK1:






:ethn-cfg-add-ingressvblsp:2,1,1,lp3,16,17,vctrunk1; //Uplink: lsp ID = 5, from logical port 3 of VB 1 to VCTRUNK1 with 16 and 17 labeled

:ethn-cfg-add-egressvblsp:2,2,vctrunk1,16,17,1,lp3; //Downlink: Link ID = 2, from VCTRUNK1 to logical port 3 of VB 2, with 16 and 17 labeled

:ethn-cfg-add-vlanporttab:3,1,2,3,lp1&&lp3; //Configure the VLAN filter table: Three logical ports of VB 1 belong to VLAN2.





Internal Use Only


III.



:ethn-cfg-add-ingressvblsp:2,3,2,lp3,18,19,vctrunk1; //Uplink: lsp ID = 3, from logical port 3 of VB 2 ti VCTRUNK1, with 18 and 19 labeled

:ethn-cfg-add-egressvblsp:2,4,vctrunk1,18,19,2,lp3; //Downlink: Link ID = 4, from VCTRUNK1 to logical port 3 of VB 2, with 18 and 19 labeled

:ethn-cfg-add-vlanporttab:3,2,3,3,lp1&&lp3; //Configure the VLAN filter table: The three logical ports of VB 2 belong to VLAN3.

:ethn-cfg-add-vctrunkpath:3,vctrunk1,bi,vc3,1,1; //VCTRUNK1 binds one bidirectional VC3, numbered 1.

:ethn-cfg-create-car:3,1&&4; //Configure CAR ID as 1, 2, 3, and 4.




:ethn-cfg-set-carpara:3,2,5120,0,5120,0; //Set the parameters of No.2 CAR in Slot 3: CIR = 5M, CBS = 0K, PIR = 5M, MBS = 0K..




:ethn-cfg-set-carpara:3,4, 15360,0, 15360,0; //Set the parameters of No.4 CAR in Slot 3: CIR = 15M, CBS = 0K, PIR = 15M, MBS = 0K.

:ethn-cfg-set-caren:3,1&&4,enable; //Enable CAR

:ethn-cfg-set-portenable:3,ip1&&ip4,enable; //Enable port.

Configure the EVPLAN service when two users with the same VLAN ID share the VCTRUNK

Suppose data of user 1 access to ports 2 and 3, data of user 2 access to ports 4 and 1, using the same VLAN, both sent uplink to VCTRUNK1:




:ethn-cfg-add-ingressvblink:3,3,ip3,1,lp2; //Uplink: Link ID = 3, from port 3 to logical port 2 pf VB 1



Internal Use Only


:ethn-cfg-set-porttype:3,vctrunk1,p; //Set VCTRUNK1 to P.

:ethn-cfg-add-ingressvblsp:3,1,1,lp4,55,23,vctrunk1; //Uplink: lsp ID = 1, Tunnel label = 55, VC label = 23, from logical port 4 of VB 1 to VCTRUNK1

:ethn-cfg-add-egressvblsp:3,2,vctrunk1,55,23,1,lp4; //Downlink: lsp ID = 2, Tunnel label = 55, VC label = 23, from VCTRUNK1 to logical port 4 of VB 1

:ethn-cfg-add-vlanporttab:3,1,3,3,lp1&lp2&lp4; //Configure the VLAN filter table: Three logical ports of VB 1 belong to VLAN3.






:ethn-cfg-add-ingressvblsp:3,3,2,lp4,56,24,vctrunk1; //Uplink: lsp ID = 3, Tunnel label = 55, VC = 23, from logical port 4 of VB 2 to VCTRUNK1

:ethn-cfg-add-egressvblsp:3,4,vctrunk1,56,24,2,lp4; //Downlink: lsp ID = 4, Tunnel label = 55, VC label = 23, from VCTRUNK1 to logical port 4 of VB 2

:ethn-cfg-add-vlanporttab:3,2,3,3,lp1&lp2&lp4; //Configure the VLAN filter table: The three logical ports of VB 2 belong to VLAN3.

:ethn-cfg-add-vctrunkpath:3,vctrunk1,bi,vc3,1,1; //VCTRUNK1 binds one bidirectional VC3, numbered 1.

:ethn-cfg-create-car:3,1&&4; //Configure CAR ID as 1, 2, 3, and 4.


:ethn-cfg-set-carpara:3,1,10240,0,10240,0; //Set the parameters of CAR 1 in Slot 3: CIR=10M, CBS=0K, PIR=10M, MBS=0K.

:ethn-cfg-set-carbindvlan:3,ip3,0xfff,2; //Port-based CAR

:ethn-cfg-set-carpara:3,2,5120,0,5120,0; //Set the parameters of CAR 2 in Slot 3: CIR=5M, CBS=0K, PIR=5M, MBS=0K

:ethn-cfg-set-carbindvlan:3,ip4,0xfff,3; //Port-based CAR

:ethn-cfg-set-carpara:3,3,15360,0,15360,0; //Set the parameters of CAR 3 in Slot 3: CIR=15M, CBS=0K, PIR=15M, MBS=0K.


:ethn-cfg-set-carpara:3,4, 15360,0, 15360,0; //Set the parameters of CAR 4 in Slot 3: CIR=15M, CBS=0K, PIR=15M, MBS=0K.

:ethn-cfg-set-caren:3,1&&4,enable; //Enable CAR.

:ethn-cfg-set-portenable:3,ip1&&ip4,enable; //Enable port.


Internal Use Only


5.1.4

5.2

5.3

MPLS Service Configuration

The SS42EFS supports MPLS to forward the accessed MPLS or send the datagram with MPLS through the port at the user’s need by setting the relevant port to the P port. No example will be given here. The V1R1 version of the board does not support MPLS.

For the practical complex configuration, refer to the Command Line Configuration Manual of the EFS.

Configuration Check

Compared with the board configurations commands (set and add), the board software and NE software provide relevant query command (get). When finishing a certain configuration, you can query whether the configuration issue is correct or not by the query command.

For detailed query command and return parameter description, refer to the relevant command line configuration manual.

Maintenance Function

To effectively locate the board fault, the SS42EFS board software provides the relevant maintenance function fulfilled by setting loop for all major chips. Below are the related configuration commands and descriptions of loop points.

1. Set the RGGI port of NP to outloop:

:ethn-debug-enable:enable;

:ethn-debug:bid,”diags control 0x1904”;

Return: control 0x1904 = 0xXXXX.XXXX.XXXX.XXX3;

:ethn-debug:bid,”diags control 0x1904 0xXXXX 0xXXXX 0xXXXX 0xXXXf”;

Cancel the outloop of the RGGI port of NP:

:ethn-debug:bid,”diags control 0x1904 0xXXXX 0xXXXX 0xXXXX 0xXXX3”;

Note: Before using the ethn-debug command, make sure to enable the debug command, that is, execute the :ethn-debug-enable:enable; command first. Same as below.

2. Set the RGGI port of PL215 to outloop:

:ethn-debug:bid,”pl215 1 rggiloop enable”; //1” is the constant, same as below.

Cancel the outloop of the RGGI port of the PL215:

:ethn-debug:bid,”pl215 1 rggiloop disable”;

3. Set the data processing module of PL215 to outloop towards the NP side.

:ethn-debug:bid,”pl215 1 dploop path enable”; //The value of “path” is A or B, representing the first or second channel of pl215 respectively. Presently, only the first channel is in use.

Cancel the outloop of the data processing module of PL215:


Internal Use Only


:ethn-debug:bid,”pl215 1 dploop path disable”;

4. Set the system-side outloop of PL215 towards the NP side.

:ethn-debug:bid,”pl215 sysoutloop slot enable”; //”slot” refers to VC3 time slot in the 1 to 24 range.

Cancel the system-side outloop of PL215.

:ethn-debug:bid,”pl215 sysoutloop slot disable”;

5. Set the system-side inloop of the PL215 towards the cross-connect board.

:ethn-debug:bid,”pl215 sysinloop slot enable”;

6. Cancel the system-side inloop of the PL215:

:ethn-debug:bid,”pl215 sysinloop slot disable”;

Note: The system-side inloop of PL215 only supports VC3 time slot instead of VC4 or VC12 time slot.

7. Transmit frame function

The SS42EFS can transceive test packets to any Ethernet port or VC trunk port. You can set the contents, lengths, transmitting numbers of the test packets on your demand.

For the specific command lines, refer to the command line configuration manual of this board.

8. Test frames

The SS42EFS can transceive test frames. By setting command lines, it can transmit test frames to the SDH side. For the specific command lines, refer to the command line configuration manual of this board.

After configuring services, test whether the SDH-side service gets through by using the following test frame command:

:ethn-cfg-set-testen:bid,vctrunk1,1,0,1;


Return format:

BOARD-ID PORT-ID COUNT-2 COUNT-3 COUNT-1 END-FLAG

11 vctrunk1 0 0 1 1

count-1, the number of test frames transmitted

count-2, the number of answer frames received

count-3, the number of test frames received

If the opposite end receives the transmitted test frame, it will return an answer frame to the local end, which will then report it to the NE.

If both count-2 and count-3 are 0, service is blocked. Check the SDH-side service configuration.

If the NE does not receive any answer frame, service is blocked.


Internal Use Only


Chapter 6

6.1

6.1.1

Typical Networking, Service and Protection Configuration (Optional)

Example 1: Pure Transparent-Transmission Service

Example and Analysis

Private line networking

Company A

Company A

Company B Company B

Node 1 Node 2

Node 3

Figure 22

6.1.2

Networking diagram of transparent-transmission services

In Figure 22, a service is configured from Node 1 to Nodes 2 and 3. Node 1 accesses services of two ports, that is, Ethernet ports 1 and 2. These services reach Nodes 2 and 3 through VCTRUNK1 and VCTRUNK2 respectively and then they are sent outside through Ethernet port 1.

This kind of service belongs to end-to-end service in the port transparent-transmission mode.

Configuration and Steps

Node 1:

Configure the SDH-side service. Create cross connection of VC3.

:Configure the port enabled.

:ethn-cfg-set-portenable:bid,ip3&ip3,enable

:Configure the work mode of the port.

:ethn-cfg-set-workmode:bid,ip2&ip3,100mfull;

:Configure the tag attribute of the port.

:ethn-cfg-set-tag:bid,ip2&ip3&vctrunk1&vctrunk2,hybrid;

Configure the default VLAN of the port to 2 at the priority level 1.

:ethn-cfg-set-vlan:bid,ip2&ip3&vctrunk1&vctrunk2,2,1;


Internal Use Only


6.1.3

Configure VCTRUNK time slot. Configure three VC3s for each VCTRUNK.

:ethn-cfg-add-vctrunkpath:bid, vctrunk1,bi,vc3,3,1&&3;


Configure service link.

:ethn-cfg-add-link:bid,1,ip2,0xffff,vctrunk1;

:ethn-cfg-add-link:bid,2,vctrunk1,0xffff,ip2;



Nodes 2 and 3


:Configure the port enabled.

:ethn-cfg-set-portenable:bid,ip2,enable;

:Configure the work mode of the port.

:ethn-cfg-set-workmode:bid,ip2,100mfull;


:ethn-cfg-set-tag:bid,ip2&vctrunk1,hybrid;

Configure the default VLAN of the port to 2 at the priority level 1.

:ethn-cfg-set-vlan:bid,ip2&vctrunk1,2,1;

:Configure VCTRUNK time slot. Configure three VC3s for each VCTRUNK.





Site Commissioning Method

After configuring the service, test whether the SDH-side service gets through by using the following test frame commands:



Return format:


11 vctrunk1 0 0 1 1




Internal Use Only






6.1.4

6.2

6.2.1

Troubleshooting

See Section 7.2.

Example 2: Transparently Transmitting Convergent Service


Headquarters

Branch 1

Node 2

Node 3

Node 4

Branch 2

Branch 1

Branch 3

Vlan1 Vlan2

Vlan3

Figure 23

6.2.2

Transparently transmitting convergent service

As shown in Figure 23, services at Nodes 1, 2, and 3 are converged to one Ethernet port of Node 4. Services of these nodes are isolated from each other through VLANs.

Configuration and Steps

Nodes 1, 2, and 3


:Configure port enabled.

:ethn-cfg-set-portenable:bid,ip2,enable

:Set the working mode of the port.



Internal Use Only


6.2.3


:ethn-cfg-set-tag:bid,ip2&vctrunk1,tag;




:ethn-cfg-add-link:bid,1,ip2,vlanid,vctrunk1;

:ethn-cfg-add-link:bid,2,vctrunk1,vlanid,ip2;

Change the VLAN ID of each node according to the setting.

Node 4:




:Configure the working mode of the port. Use the FE port as convergent node.









:ethn-cfg-add-link:bid,1,ip1,vlanid1,vctrunk1;

:ethn-cfg-add-link:bid,2,vctrunk1,vlanid1,ip1;





Change the VLANID of each node according to the setting.


After finishing the configuration of service, test whether the SDH-side service is connected by using the following test frame command:




Internal Use Only


After sending the command, the NE will receive a report of the event. Otherwise, the service is blocked. Check whether the cross-connect service configuration is correct and the VCTRUNK binding is normal.

If necessary, test it by means of loopback.

6.2.4

6.3

6.3.1

Troubleshooting

See Section 7.2.

Example 3: Layer 2 Switching Service


SDH Ring

Headquarters

Node 1

Node 2Node 3

Node 4

Branch 2

Branch 1 Branch 3

Figure 24

6.3.2

Transparently transmitting convergent service

Nodes 1, 2, 3, and 4 want to communicate with each other. On the SDH ring, all the nodes share the same SDH time slot. If Node 1 wants to communicate with Node 4, data between the two nodes must be forwarded by Nodes 2 and 3.

Configuration and Procedures

Nodes 1 and 4




:Configure the working mode of the port.






Internal Use Only



:Create VB.

:ethn-cfg-create-VB:bid,1,”node1”; //Node 1


:Mount the logical port of VB of the physical port.

:ethn-cfg-add-ingressvblink:bid,1,ip2,1,lp1;

:ethn-cfg-add-egressvblink:bid,2,1,lp1,ip2;

:ethn-cfg-add-ingressvblink:bid,3,vctrunk1,1,lp2;

:ethn-cfg-add-egressvblink:bid,4,1,lp2,vctrunk1;

:Create the VLAN filter table.

Nodes 1 and 4

:ethn-cfg-add-vlanporttab:bid,1,2,2,lp1&lp2; //vlan filter table, vlanid = 2, including two ports, lp1 and lp2

Nodes 2 and 3 Configure SDH-side service and create cross connection of VC3.



:Configure the working mode of the port.



:ethn-cfg-set-tag:bid,ip2&vctrunk1&vctrunk2,tag;




:Create VB



:Mount the logical port of VB of the physical port.

:ethn-cfg-add-ingressvblink:bid,1,ip2,1,lp1;

:ethn-cfg-add-egressvblink:bid,2,1,lp1,ip2;






Internal Use Only


6.3.3

6.3.4

:Create the VLAN filter table.

:ethn-cfg-add-vlanporttab:bid,1,2,3,lp1&&lp3; //vlan filter table, vlanid = 2, including two ports, lp1, lp2, and lp3


Before configuring such services, configure a chain or ring type and enable the spanning tree (not recommended).

After configuring the services, test whether the SDH-side service gets through by using the following test frame command:



After sending the service, the NE will receive the event report. If the NE does not receive any answering frame, the service is blocked.

Troubleshooting

See Section 7.2.


Internal Use Only


Chapter 7

7.1

7.2

Deployment and Commissioning


Before the deployment, create a VCTRUNK between two nodes. Configure test frames for the two SS42EFSs. Send one test frame to each other. Query whether both sides have received the test frame so as to judge the line status by using the command to query the test frame counter (ethn-cfg-get-testcount) and the command to clear the test frame counter (ethn-cfg-clr-testcount).

Fault Location Method

The most possible fault of a board that may appear on the practical network application is service blocked. You can find out whether the board is wrong by following these steps:

Use test frames to locate whether the fault lies in the hardware:

Perform system-side outloop of the PL215.

Send a test frame to a binding VCTRUNK.

View whether the test frame is looped back. If it is looped back, the hardware is normal. Otherwise, the hardware might be faulty.

If the hardware is normal, check the software.

1. EVPL service

Perform RGGI port loopback for NP. Use the ping function of the SmartBits or the PC to send the packet to the configuration port. If the service is looped back, the configuration at the Ethernet side is correct; otherwise, the configuration at the Ethernet side is faulty. Check and confirm the configuration information.

Perform system-side outloop for the PL215. Use the ping function of the SmartBits or the PC to send the packet to the configuration port. If the service is looped back, the configuration of the PL125 is correct; otherwise, the configuration of the PL125 is faulty. Check whether the relevant configuration commands of the PL125 like time slot binding is correct. Note that the PL215 has only VC3-level loopback instead of VC12-level loopback.

2. EVPLAN service

As the problem of source port filter exists, you cannot locate the fault by performing NP RGGI loopback or PL125 loopback for the EVPLAN service. However, you can use the debug command to query whether the microcode has discarded datagrams.

:ethn-debug-enable:enable; :ethn-debug:bid,”diags ppeext 0x380300”; Return value: ppeext 0x380300 0xaaaa.bbbb.cccc.dddd;

Where,


Internal Use Only


aaaa.bbbb means the status that the microcode discards datagrams; cccc means the number of the port that discards datagrams; VCTRUNK port number between 0000 ~ maximum VCTRUNK number; Ethernet port number: 0040 ~ 0040 + maximum Ethernet port number; dddd means the reason for discarding packets.

For more information of the meanings, refer to the following document.

msg_types.h

During locating the fault, the software consecutively reads data. If the data of aaaa.bbbb vary at a time, the microcode is discarding packets.

Clear microcode count: :ethn-debug:bid,”diags ppeext 0x380300 0 0 0 0”;

You can use the debug command to read transceiver packet and packet loss count of the PL215. Refer to the following document.

Counter.txt Note: You can use the above method to locate all problems related to service disconnected.

Common Location Debug Command

1. Set the RGGI port of the NP to outloop towards the NP side.

:ethn-debug-enable:enable;

:ethn-debug:bid,”diags control 0x1904”;

Return: control 0x1904 = 0xXXXX.XXXX.XXXX.XXX3;

:ethn-debug:bid,”diags control 0x1904 0xXXXX 0xXXXX 0xXXXX 0xXXXf”;

Cancel the outloop of the RGGI port:

:ethn-debug:bid,”diags control 0x1904 0xXXXX 0xXXXX 0xXXXX 0xXXX3”;

Note: Before using the ethn-debug command, make sure to enable the debug command, that is, execute the :ethn-debug-enable:enable; command first. Same as below.

2. Set the RGGI port of the PL215 to outloop towards the NP side.

:ethn-debug:bid,”pl215 1 rggiloop enable”; //”1” is the constant, same as below.

Cancel the outloop of the RGGI port of the PL215.

:ethn-debug:bid,”pl215 1 rggiloop disable”;

3. Set the data processing module of the PL215 to outloop towards the NP side.

:ethn-debug:bid,”pl215 1 dploop path enable”; //The values of “path” is A or B, representing the first or second channel of the PL215 respectively. Presently, only the first channel is in use.


Internal Use Only


Cancel the outloop of the data processing module of the PL215:

:ethn-debug:bid,”pl215 1 dploop path disable”;

4. Set the system-side outloop of the PL215 towards the NP side.

:ethn-debug:bid,”pl215 sysoutloop slot enable”; //”slot” refers to VC3 time slot in the 1 to 24 range.

Cancel the system-side outloop of the PL215:

:ethn-debug:bid,”pl215 sysoutloop slot disable”;

5. Set the system-side inloop of the PL215 towards the cross-connect board:

:ethn-debug:bid,”pl215 sysinloop slot enable”;

6. Cancel the system-side inloop of PL215.

:ethn-debug:bid,”pl215 sysinloop slot disable”;

Note: The system-side inloop of PL215 only supports VC3 time slot instead of VC4 or VC12 time slot.

7. Transmit test packets

The SS42EFS can transmit test packets to any Ethernet port or VCTRUNK port. You can configure randomly the contents, lengths, types, and transmission quantities of test packets. For the specific command line settings, refer to the command line configuration manual of the board.

8. Test frames

The SS53EFS can transceive test frames. By setting command lines, it can transmit test frames to the SDH side. For the specific command lines, refer to the command line configuration manual of this board.

After configuring the service, test whether the SDH-side service gets through by using the following test frame commands:



Return format:


11 vctrunk1 0 0 1 1








Internal Use Only


EFGS .zip单板单单单单单

Chapter 8

8.1

8.2

Chapter 9

Chapter 10

10.1

10.2

10.3 1)

Acceptance Test

Items, Methods and Indices

As all indices of the SS42EFS have been tested before delivery, you only need to test whether the board service is normal during the deployment by using two PCs to ping each other. If successful, the service is normal.

Precautions

During the acceptance test, please note the forwarding efficiency which is related to the packet length due to the performance of the EFS network processor. In general, the smaller the packet length is, the lower the forwarding efficiency becomes. As a result, try to use long packets for the test.

Board Maintenance

Precautions for routine maintenance

Null

Appendix

Description of Hardware Version

The SS42EFS applies to the Metro 1000.

List of Board PTP Commands

Refer to the interface documents of the board and NE software.

Currently Known Problems It will cost lots of CPU resources to configure board VCTRUNK binding. Do not delete or bind VC trunk frequently in a short time. Otherwise, it will incur board watchdog reset.


Internal Use Only


2)

3)

4) 5)

6)

7)

8)

9)

10)

11)

12)

13)

14) 15) 16) 17)

18)

19)

Due to the complex MPLS configuration, try to avoid using the MPLS configuration. Because of the low forwarding efficiency, note that the GE port shall not be added with full service. No.12 VCTRUNK is unavailable. Multiplex flows are bound into one CAR. Long-packet flows are suppressed by short-packet flows and so they fail to get the bandwidth. We recommend you not to bind multiplex flows into one CAR but bind one flow into one CAR. In configuring the interface board, report the interface board event before sending the working mode configuration. Otherwise, the chip will be set to the auto-negotiation mode. You can also send the working mode configuration or send the configuration interface following init-all. The port will be set to the auto-negotiation mode. However, it displays normal when you query the working mode. In this case, query the actual working mode of the board port. If it is in the semi-duplex mode or auto-negotiation mode, you have found the problem. After clearing phy loopback at the FE interface, the working mode will recover to the configuration when loopback is set. If no loopback is set, the working mode will be set to the auto-negotiation mode after sending the command to clear loopback. In this case, you need to send the setting of the working mode again. The RMON of the FE port does not count the lengths and bytes of error packets that will be contained in the total packets and special error packets (FCS and Alignment). After you pull out or insert the cross-connect board, service will be interrupted. Reset the board to recover it. When service is transmitted between Ethernet ports, Quality of service (QoS) is unavailable. When AIS occurs to a certain VCTRUNK, the VCDELAY alarm jitter might appear. After you change the interface board configurations, the port enable status of the NE board is inconsistent with the one before. Send the relevant port configurations again. Broadcast datagram suppression is precise for 64-byte broadcast datagrams only. The datagrams longer than 64 bytes are considered as 64-byte ones during flow statistics. CAR is invalid for IP datagram. The board does not provide the alarm for software loss. The datagrams shorter than 64 bytes are considered as bad packets. When the alarm for clock loss occurs to the board and even the alarm disappears, the service will fail to recover. The outgoing port is the access port which receives 64-byte datagrams and transmits 60-byte datagrams (with the 4-byte VLAN removed). The opposite end will discard the 60-byte datagrams at their arrival. Note that the length of the datagrams is equal to or longer than 68 bytes. The EFS does not support software reset.

Documents

220 1 Document Optix Metro 1000 Ss42efs