SED&SEE Card Service Configuration Guide (U31) - R1.0 PDF
SED&SEE Card Service Configuration Guide (U31) - R1.0 PDF
Configuration Guide
R1.0
SED&SEE Card Service Configuration Guide Internal Use Only▲
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do
not agree to the following terms, please notice that you are not allowed to use this document.
Copyright © 2012 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited.
and are registered trademarks of ZTE CORPORATION. ZTE’s company name, logo
and product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners. Without the prior written consent of ZTE CORPORATION or the
third party owner thereof, anyone’s access to this document should not be construed as granting, by
implication, estopped or otherwise, any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual, relevant
contract or laws and regulations in relevant country (countries).
This document is provided “as is” and “as available”. Information contained in this document is subject
to continuous update without further notice due to improvement and update of ZTE CORPORATION’s
products and technologies.
ZTE CORPORATION
Address: NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website: http://dms.zte.com.cn (TSM-Technical Support)
Email: [email protected]
Revision History
Author
Proposal: Before reading this document, you had better have the following knowledge and skills.
SEQ Knowledge and skills Reference material
Application principles and service
1 configuration methods of SEC and SFE Card maintenance manual
cards
2
3
Follow-up document: After reading this document, you may need the following information.
SEQ Reference material Information
Introduces other details of the SEE card
1 ZXMP S385 SEE Card Maintenance Manual
except service configuration.
Introduces other details of the SED card
2 ZXMP S330 SED Card Maintenance Manual
except service configuration.
3
ZTE Confidential Proprietary © 2012 ZTE CORPORATION. All rights reserved. III
SED&SEE Card Service Configuration Guide Internal Use Only▲
Summary
Chapter Description
1 Preface Introduces the backgrounds of this manual and its content.
2 Card Overview Introduces the features of SED and SEE card briefly.
3 Access to Main Configurations of Introduces the access to configure basic services on U31
EMS and Basic Concepts EMS of EMS and definitions of the parameters on multiple
configuration interfaces.
4 Introduction to MFDFr Service Introduces the basic principles of various service models and
Model typical networking scenarios.
5 EMS Configuration Introduces how to configure services under different
networking scenarios in engineering.
AppA Reference A Introduces the reference manuals.
TABLE OF CONTENTS
1 Preface ............................................................................................................ 1
FIGURES
Figure 5-11 EVPL Model Scenario 1—【UNINNI Interface Configuration】 Interface ....... 40
Figure 5-12 EVPL Model Scenario 1—【CE-VLANID List Management】 Interface ......... 40
Figure 5-13 EVPL Model Scenario 1—【Ethernet MFDFr Management】 Interface 1 ...... 41
Figure 5-14 EVPL Model Scenario 1—【Ethernet MFDFr Management】 Interface 2 ...... 42
Figure 5-15 EVPL Model Scenario 1—【Ethernet MFDFr Management】 Interface 3 ...... 42
Figure 5-16 EVPL Model Scenario 1—【Ethernet MFDFr Management】 Interface 4 ...... 43
Figure 5-17 EVPL Model Scenario 1—【Ethernet VCG Binding】 Interface ..................... 43
Figure 5-18 EVPL Model Scenario 1—【Cross Connection】 Interface ............................ 44
Figure 5-19 EVPL Model Application Scenario 2—Schematic Diagram of Networking ....... 44
Figure 5-20 EVPL Model Scenario 2—【Ethernet Port Basic Property】 Interface ........... 46
Figure 5-21 EVPL Model Scenario 2—【UNINNI Interface Configuration】 Interface ....... 46
Figure 5-22 EVPL Model Scenario 2—【CE-VLANID List Management】 Interface ......... 47
Figure 5-23 EVPL Model Scenario 2—【MFDFr Service Management】 Interface 1 ........ 48
Figure 5-24 EVPL Model Scenario 2—【MFDFr Service Management】 Interface 2 ........ 48
Figure 5-25 EVPL Model Scenario 2—【MFDFr Service Management】 Interface 3 ........ 49
Figure 5-26 EVPL Model Scenario 2—【MFDFr Service Management】 Interface 4 ........ 49
Figure 5-27 EVPL Model Scenario 2—MFDFr Service Management Interface 5 ................ 50
Figure 5-28 EVPL Model Scenario 2—Ethernet VCG Binding Interface ............................. 50
Figure 5-29 EVPL Model Scenario 3—Cross Connection Interface 1 ................................. 51
Figure 5-30 EVPL Model Scenario 3—Cross Connection Interface 2 ................................. 51
Figure 5-31 EVPL Model Scenario 3—Cross Connection Interface 3 ................................. 52
Figure 5-32 EVPL Model Application Scenario 3—Schematic Diagram of Networking ....... 52
Figure 5-33 EVPL Model Scenario 3—Ethernet Port Basic Property Interface ................... 54
Figure 5-34 EVPL Model Scenario 3—UNINNI Interface Configuration Interface ............... 55
Figure 5-35 EVPL Model Scenario 3—CE-VLANID List Management Interface ................. 55
Figure 5-36 EVPL Model Scenario 3—MFDFr Service Management Interface 1 ................ 56
Figure 5-37 EVPL Model Scenario 3—MFDFr Service Management Interface 2 ................ 57
Figure 5-38 EVPL Model Scenario 3—MFDFr Service Management Interface 3 ................ 58
Figure 5-39 EVPL Model Scenario 3—MFDFr Service Management Interface 4 ................ 58
Figure 5-40 EVPL Model Scenario 3—MFDFr Service Management Interface 5 ................ 59
Figure 5-41 EVPL Model Scenario 3—Ethernet VCG Binding Interface ............................. 59
Figure 5-42 EVPL Model Scenario 2—Cross Connection Interface 1 ................................. 60
Figure 5-43 EVPL Model Scenario 2—Cross Connection Interface 2 ................................. 60
ZTE Confidential Proprietary © 2012 ZTE CORPORATION. All rights reserved. VII
SED&SEE Card Service Configuration Guide Internal Use Only▲
ZTE Confidential Proprietary © 2012 ZTE CORPORATION. All rights reserved. VIII
SED&SEE Card Service Configuration Guide Internal Use Only▲
TABLES
Table 3-1 Correspondence Table of Tag Retransmission and Process of Service Flow ..... 16
1 Preface
The newly developed SED and SEE cards based on the flow domain concept are
members of data cards. Currently, the cards are released for commercial use in various
cities successively to replace the traditional cards (including SFE and SEC). Because
SED and SEE cards differ widely from the traditional cards in configuration methods and
application principles, engineers may have difficulties in understanding and configuring
these two kinds of cards when encountering the cards for the first time. In order to meet
the requirements from live network, ZTE Corporation composes this configuration guide
so as to help those engineers on site if necessary.
The following sections will compare the SED/SEE cards (hereinafter referred to as “new
cards”) with the traditional SFE/SEC cards (hereinafter referred to as “traditional cards”).
This document is intended for SED R1 and SEE R1 versions. If not specified, the
configuration method of SEE card is the same with that of the SED card and the SED
card is taken as an example in the following sections. If the configuration method of SEE
card is different from that of the SED card Otherwise, the differences will be specified.
2 Card Overview
SED card is mainly intended for S330 and S325 devices. SED card, which is generally
referred to as SED main processor, can be used with either electrical interface card
EIFEx6 or optical interface card OIS1x6. SEE main processor provides two FE optical
interfaces (with port No.7 and 8) and two GE opto-electronic interfaces (with port No. 9
and 10) top to bottom on the panel.
When SED card is used with electrical interface card, EMS preset software/hardware
version is 2320 and user side provides 6 FE electrical interfaces, 2 optical interfaces and
2 GE opto-electronic interfaces. When SED card is used with optical interface card, EMS
preset software/hardware version is 1320 and user side provides 8 FE optical interfaces
and 2 GE opto-electronic interfaces. When SEE card is not used with interface card, EMS
preset software/hardware version is 1310 and user side provides 2 FE optical interfaces
and 2 GE opto-electronic interfaces. “Hardware version” and “software version” must be
the same.
SEE card provides 16 VCG (EOS) ports, which support convergence ratio of 16:1, and
maximum 8 AUG system bandwidth.
All service slots (slots 1-6 and slots 11-16) of S330 can be configured. According to
different bandwidths of slot buses in system backplanes, the backplane capacities of
SED in different slots are different. The detailed plug-in slots and port capacities are as
follows:
Note:
1. Because SED card is produced formally with ZXMP S330 V1.4 system, it can be
used with CSB cross-connect card but not the CSA cross-connect card in S330
devices.
2. SED card can also be used in S325 devices on condition that the software
version of SED card is either R1P10 or later versions, and the logic version of
SED card is either R1P04 or later versions.
SEE card is mainly intended for S385 devices and produced formally with V2.5 system.
SEE card, which is generally referred to as SEE main processor, can be used with
electrical interface card ESFEx8, optical interface card OEIFEX8 or alone. SEE main
processor provides two GE opto-electronic interfaces (with port No. 9 and 10) on the
panel.
When SEE card is used with electrical interface card, EMS preset software/hardware
version is 2321 and user side provides 8 FE electrical interfaces, and 2 GE
opto-electronic interfaces. When SEE card is used with optical interface card, EMS
preset software/hardware version is 1321 and user side provides 8 FE optical interfaces
and 2 GE opto-electronic interfaces. When SEE card is not used with interface card, EMS
preset software/hardware version is 1311 and user side provides 2 GE opto-electronic
interfaces.
SEE card provides 48 VCG (EOS) ports, which support convergence ratio of 48:1, and
maximum 8 AUG system bandwidth.
Note:
2. SEE can be used in ZXMP S385 V2.20 and system version. Make sure to
configure proper NCP and CS versions.
Data configuration of the new SED card mainly consists of the following five mandatory
interfaces (as shown in the following red square frames in Figure 3-1) which must be
configured when configuring basic services (of course, other interfaces need to be
configured in special conditions). For other related optical interfaces and meanings of
parameters, please refer to relevant card maintenance manual.
The following sections will briefly introduce and explain relevant mandatory parameters
respectively ( the optical parameters can be set to their default values).
The 【Ethernet Port Basic Property】 interface is similar to traditional card interface.
The Use parameter (mandatory item) is used to enable 10 Ethernet user ports. For the
ports not used, please don’t enable them. For the ports used for temporary
commissioning and testing, please disable the ports after the commissioning and testing
ends. User ports 1 to 8 correspond top to bottom to 8 FE electrical interfaces (or optical
interfaces) successively, and the user ports 9 and 10 correspond to GE optical interfaces.
Modify other parameters such as Rate Selection (including full duplex mode) and Cross
Connection of the enabled ports according to actual situation. The configuration is
similar to traditional card in that the connected equipment must be configured the same.
Min IFG Parameter means minimum frame interval which is used to configure the card's
minimum interval of sending services. The value of Min IFG Parameter, which needs not
to be modified, can be set from 6 to 16.
Tip:
The interface, which is similar to traditional card interface, is used for bundling timeslots
for system ports, setting encapsulation types, enabling LCAS and so on. The card
supports VC12, VC3, and VC4 granularities, GFP encapsulation, Enable and Disable
types of LCAS, and the function of activating and deactivating VCG members.
Note:
Currently, only one VC4 granularity, with which LCAS is of Disable status, can be
configured on SEC card. However, SED and SEE cards are not limited by this.
1. Choose VCG-EOS port (system port) on the 【VCG Bind Information】 window.
2. Choose corresponding channel listed in the Resource tree on the right of the
window (for more channels, press Shift on you keyboard, and choose multiple
continuous channels needed).
4. If you want to discharge the channel of one system port, choose the channels and
click . Then, the channels will be removed to the Resource tree on the right.
Click Add to add either sectional CE-VLAN tags or Untagged tags in batches which can
coexist in a list. For tags in batches, if the sequence number of the first part of the tag is
same with that of the send part, it means only one tag. For example, CE-VLAN 100-100
in Figure 3-4 means tag 100. If the Untagged tag is chosen, services without tags will be
forwarded, and services with tags will be filtered and discarded. CE-VLAN of every row
(one VLAN Table ID corresponds to one row) can be configured with a maximum of 32
segments (that is, the CE-VLAN may contain 31 commas at most); every row contains
either multiple or repeated CE-VLANs (ranging from 1 to 4094); SED card can supports
256 lists at most while SEE card supports 512 lists at most.
Traditional card does not have this interface. Since the new card have imported flow
concept, its port configuration is different from that of the traditional card. The new card
requires that physical ports, specified as either UNI or NNI ports, should be allocated
logically. UNI and NNI ports are not mapped necessarily to user ports and system port
VCG. Choose Add on the lower left corner of the interface to create UNI/NNI port (you
can create multiple ports successively).
UNI port: Only user Ethernet port can be designated as an UNI port. One UNI port may
contain multiple (1, 2, or 4) user Ethernet ports. If the UNI port contains either 2 or 4 ports,
these ports are aggregated into a trunk group which acts as a logic port.
NNI port: Both user Ethernet port and VCG (EOS) port can be designated as NNI ports.
A NNI port may contain of multiple (1, 2, or 4) user Ethernet ports. Two user Ethernet
ports are aggregated into a trunk group to act as a logic port, or four user Ethernet ports
act as a logic port.
Convergence mode: “Static”, “Dynamic”, and “No”, as shown in the following figure.
No mode means that it does not support trunk group convergence while Dynamic and
Static modes both support trunk group convergence. Dynamic mode means that trunk
group convergence supports LACP protocol, and Static mode means that trunk group
convergence does not support LACP protocol.
After the ports are created as shown in Figure 3-5, click Apply and the following interface
is displayed:
Bind Attribute: the Bind Attribute drop-down list box has two items: All to One Bundling
and CE-VLAN Bundling.
All to One Bundling means that the port can be used by only one service flow and is
exclusive. The item is used to configure three kinds of services: EPL, EPLAN, and
EPTREE.
CE-VLAN Bundling means that the port should be used with CE-VLAN. One UNI/NI port
can be used with different CE-VLANs. Multiple service flows can share the same port.
This item is used to three kinds of services: EVPL, EVPLAN, and EVPTREE.
Member Port: Null means that there is no member port now and you need to add it. To
add a new member port, proceed as follows.
2. Choose the port on the Aggregation Port List To Be Set window on the right of the
interface.
Choose UNI/NNI port as shown in Figure 3-7, and then click Advance on the lower right
corner of the interface. The following interface is displayed to set parameters as shown in
Figure 3-8.
NNI Multiple Link Attribute: When the bind attribute of NNI port is set to CE-VLAN
Bundling, you can configure the NNI port to either Not Multiplexing or Multiple
S-VLAN Label (the two items are not available for UNI port).
If the NNI is configured to Multiple S-VLAN Label, it means that the access service
flow, which contains the NNI interface, will first use S-VLAN to check validity through
the interface; the service flow, exported through NNI interface, also contains
S-VLAN.
If the NNI is configured to Not Multiplexing, it means that the access service flow
through NNI needs not to be checked by S-VLAN; the service flow, exported
through NNI interface, does not contain S-VLAN.
Note:
Please note that S-VLAN implementation principle is different from PVID principles
under either traditional card access or TLS mode.
Although there is configuration of PVID value in new card, the value is of non sense.
JUMBO Frame Support: the JUMBO Frame Support can be set to either Support or No
Support.
Support means that it can transmit data consisting of more than or equal to 1518
bytes.
Not Support means that it can only transmit data consisting of less than 1518
bytes. This configuration is invalid for NNI interfaces designated by VCG (EOS)
interface.
The following interface, which is used to create MFDFr service flow model, is the core
interface of new card service configurations. The services of new card are classified into
six types. Click Create to choose the service types on the right of the interface as shown
in Figure 3-9.
Assume that you have chosen to create EVPL service as shown in Figure 3-10.
【Basic Info Window】: On this window, you can configure related information about
service flow.
User Label: an alternative name in order to facilitate user to remember and distinct.
SVLAN Label: Only for EVP type services, the parameter needs to be configured. For EP
services, the parameter should not be configured. The value of SVLAN Label for every
service on one card should be unique (the value is an integer ranging from 1 to 4094).
Note:
1. If the NNI logic port is set to Not Multiplexing, the S-VLAN label configured with
this service is invalid. However, the S-VLAN label is also obliged to be
configured. Or, the service will be unavailable; if the NNI logic port is set to
Multiple S-VLAN Label, the S-VLAN label is valid and marked at the outermost
layer of the service to implement the QinQ function.
2. As far as service flow is concerned, S-VLAN label only exists in EVP service.
Different service flows require different S-VLAN label values.
SVLAN TPID: the parameter can be set to either 0x8100 or 0x88A8. 0x8100 is an
international standard. 0x88A8 is a standard owned by some vendors. When connecting
SED or SEE card to other data card or equipment of other vendors, please choose the
accurate SVLAN TPID. This parameter is valid on condition that NNI port is set to
CE-VLAN Bundling and Multiple S-VLAN Label (the two parameters are both required to
be configured accurately).
Note:
1. If the NNI port is set to Not Multiplexing, the SVLAN TPID is invalid.
2. If the UNI and NNI ports are both set to CE-VLAN Bundling, and the NNI port is
also set to Not Multiplexing, TPIDs of UNI and NNI ports are set to 0x8100 by
default (that is, when there is only one VLAN label; if the NNI port is set to
Multiple S-VLAN Label, that is QinQ mode, TPID, which is the outermost layer
can be set to 0x8100 or 0x88A8.
VLAN Preservation: select the check box of Enable means that VLAN is preserved. If
you do not select the check box, it means that VLAN is not preserved. For EP services,
the parameter need not to be set and the check box is selected by default.
Under VLAN Preservation mode with the check box of Enable selected, VLAN label can
not be added, modified, and deleted in flow domain. VLAN remains unchanged during the
retransmission and processing process on UNI/NNI port. So, the CE-VLAN list
configurations of ports on flow domain must be same. The service connected in UNI/NNI
port may contain TAG or not, but the service must consist with the configuration of
CE-VLAN list so as to be forwarded. Otherwise, the service will be discarded.
Under the VLAN No Preservation mode, that is the check box of Enable not selected,
VLAN label can be added, modified, and deleted in flow domain during the
retransmission and processing process on UNI/NNI port ( untag service supports untag
preservation and vid addition, tag service supports vid preservation, strip, and
modification). So, the configurations of CE VLAN ID list on port in flow domain can be
different. The following sections take the example of direction from A to B to illustrate
processing of tags for messages under the CE VLAN ID No Preservation mode as shown
in Table 3-1.
Table 3-1 Correspondence Table of Tag Retransmission and Process of Service Flow
Direction of
Port A Processing of Port B
service flow Processing of and
CEVLAN and changes in CEVLAN
changes in packet
→ list packet list
Untag ------
Other VID discarded
Other VID ------
Untag ------
Untag discarded
Other VID ------
Table 3-1 clearly illustrates the processing of VLAN tag under No Preservation mode
when the service flow is retransmitted. For traditional card, only those ports with the same
VLAN ID can retransmit services. This is similar to the VLAN Preservation mode of new
card. New card can change VLAN tag under VLAN No Preservation mode. This function
of new card can be used flexibly to implement service configurations under several
scenarios. For detailed information, please refer to the service configuration chapter
below.
The configuration mode of Untagged tag is the same as that of VID. Here takes an
example to illustrate the transmission of simple service through two ports. UNI and NNI
are configured as an EVPL service in flow domain, and the flow direction of the service
from UNI to NNI is shown below:
1. VID is of preservation mode, and NNI port is set to Not Multiplexing. UNI configures
untagged list, and NNI configures untagged list. Under this circumstance, only
services with untag can be forwarded while services with tag will be discarded on
UNI port.
2. VID is of no preservation mode, and NNI port is set to Not Multiplexing. UNI
configures untagged list, and NNI configures tag n list. Under this circumstance,
only services with untag can be forwarded with tag n on NNI export.
3. VID is of preservation mode, and NNI port is set to Multiple S-VLAN Label. UNI
configures untagged list, and NNI configures untagged list. Under this circumstance,
only services with untag can be forwarded with S-VLAN m on NNI export, and the
services with tag will be discarded on UNI port.
4. VID is of no preservation mode, and NNI port is set to Multiple S-VLAN Label. UNI
configures untagged list, and NNI configures tag n list. Under this circumstance,
only services with untag can be forwarded with tag S-VLAN m on outer layer and tag
n on inner layer on NNI export. Besides, the QinQ function can be implemented
under this circumstance.
VLAN window: on the window, you can configure the port in service flow and the VLAN
tag binding.
Port: this parameter is used to add all UNI and NNI ports. Click Add to add a port.
CE-VLAN (or CE-VLAN List): this parameter needs to be configured for EVP services
(do not configure this parameter for EP services). The value of the parameter must be the
same with the value of VLAN Table ID on the CE-VLANID List Management interface.
Set the CE-VLAN parameter correctly according the value of VLAN Table ID.
After the service is created, click OK to finish, and then the following interface is
displayed to show and check the created service information and configurations as
shown in Figure 3-11.
The new card should select accurate service flow model and limit the rate of bandwidth
for every port (except the multiplexing NNI port) in the service flow. For traditional card,
bandwidth rate-limiting is an optical item. If not required, it is recommended not to limit
rate. For new card, the bandwidth rate-limiting is a mandatory item. Please note that
services will be discarded directly and thus not forwarded if you do not configure the item.
In Figure 3-11, choose Band Width tab page on the lower window, click Add on the right
corner, and then the bandwidth rate-limiting interface is displayed in Figure 3-12.
Port: choose the port to limit rate of bandwidth in the drop-down list box.
QoS Property: this parameter is used to configure the QoS property of services under
bandwidth rate-limiting. QoS property is classified into Expedited Forward (EF), Assumed
Forwarding (AF), and Best Effort (BE) corresponding to Assured Bandwidth (AB),
Committed Burst Size (CBS), Excess Information Rate (EIR), and Excess Burst Size
(EBS) respectively.
Information Rate indicates forwarding rate of data packet and its unit is Kbps.
100000, as shown in Figure 3-12, indicates 100Mbps bandwidth.
Burst Size indicates number of tokens. The larger the number is, the more the data
is sent in a flash. In other words, the greater the configuration value of burst size is,
the higher the rate is when the bandwidth rate-limiting is just configured (this relates
to the cache size of peer equipment). After the configuration, the rate will be stable
when the card is running normally.
When the QoS is set to EF, only AB and CBS can be configured. Under this
circumstance, services that can be forwarded are defined as green services.
Services that are discarded because of out of bandwidth are defined as red
services.
When QoS is set to AF, AB, CBS, EIR, and EBS can be configured. Assume that
total bandwidth of the port is 80M with 40M configured to AB, the 40M configured to
EIR.
If the port access rate is 20M, the 20M services are all AB services.
If the access rate is 60M, 40M services are AB services while the other 20M
services are EIR services. That is the services are classified into 40M green
services and 20M yellow services.
Following the same rule, if the port access 100M services, 20M services will be
regarded as red services and discarded.
When the QoS is set to BE, EIR and EBS can be configured. Under this
circumstance, services that can be forwarded are defined as yellow services.
Services that are discarded because of out of bandwidth are defined as red
services.
From the above description, we see that green services have the highest priority, and
yellow services have second highest priority. The services that are discarded because of
out of bandwidth are defined as red services. Colors of services can be researched on
current performance and history performance interfaces.
For the application environment of port +CE-VLAN ID+802.1p, you can choose to limit
rate or not as required. Besides, you can set different bandwidth rate-limiting for services
of different priorities of one port.
After finishing bandwidth limitation, click Apply to close the window, and then check the
bandwidth information on the Bandwidth window, as shown in Figure 3-13.
Note:
The bandwidth rate-limiting of every port in service flows on SED and SEE card must be
configured. Otherwise, the services, which are discarded directly, will be unavailable.
Besides, bandwidth rate-limiting is only configured in entry ports.
4.1 Overview
The new card does not contain transparent transmission, backbone, and access and TLS
modes. However, the new card imported the concept of MFDFr service flow domain, and
the services are configured on the basis of service flow mode.
MFDFr service is classified into three types: E-line, E-LAN and E-TREE services.
According to service models, MFDFr service is classified into six modes: EPL, EVPL,
EPLAN, EVPLAN, EPTREE, and EVPTREE. Wherein, EPL, EPLAN, and EPTREE are
referred to EP services for short, EVPL, EVPLAN, and EVPTREE, which contain letter V,
are referred to as EVP services for short. The detailed category information is shown in
Figure 4-1.
Property: Point-to-point
EPL Service
transparent transmission
E-line
service.
(Linear
Property: virtual linear
Service) EVPL
service, can implement
Point to Point Service
shared bandwidth.
Property: exclusive access
to a port, MAC address
E-LAN EPLAN learning, provides multicast
(Net Service) Service network for point to
Multipoint to multipoint service
MFDFr
Multipoint applications (such as
Service
Property: can implement
IPTV).
EVPLAN shared link bandwidth
Service comparing to EPLAN
service.
Property: assigns root node
EPTREE
and leaf node attributes to
E-TREE Service
port. Leaf node does not
(Tree Service)
communicate with each
Point to
other in flow domain;
Multipoint
Property: can
implements implement
MAC address
EVPTREE shared link bandwidth
learnding.
Service comparing to EVPTREE
service.
EPL has two service access points to implement point-to-point transparent transmission
for MAC frame of user Ethernet. Services of every EPL user are borne by special SDH
channel. Since different users do not need to share SDH bandwidth, EPL users have the
same bandwidth assurance and safety performance with SDH. Besides, because this
mode is point-to-point transmission, L2 switching function and MAC address learning is
not needed.
Features of EPL services: forwarding with exclusive access to port. No matter whether
the Ethernet services on card have VLAN tag or two layers of VLAN, the card does not
process the services which will be forwarded from another port on condition that the
connected port is exclusive to these services. This transparent transmission mode in new
card is equal to that of the old card but with higher transmission efficiency. However,
because of exclusive access to port, the port utilization ratio is low.
ADM7
10GSDH Device of
Vendor B
ADM9
Wavelengt
ADM8
h Division
155M
155M Equipment
1200~3840k
m
ADM1 ADM4
MSTP MSTP
Device 1 Device 2
FE1 Data FE2
FE Analyzer FE
The main differences between EVPL and EPL lie in the fact that different users need to
share link bandwidth. So, this mode requires identifying data from different users through
VLAN ID or other mechanisms. If the mode requires providing services of different
qualities for different users, QoS mechanism should be used. However, because of logic
user isolation, its safety is less than that of EPL. Services of this mode also belong to
point-to-point services.
If forwarded services have VLAN, the user is required to provide specific VLAN
ID value;
Even if you have chosen multiplexing mode (QinQ), the services are also
required to check and process inner layer tags.
ADM7
10GSDH Device of
Vendor B
Wavelengt ADM9
ADM8
h Division
Equipment 155M
155M
1200~3840k
m
ADM1 ADM4
80k 80k
80k 2.5GSDH 80k ZTE 2.5GSDH
m m
m Device of Vendor m Device
A
Analyzer FE4
FE3
ADM7
10GSDH Device of
Vendor B
ADM9
ADM8 Wavelengt
h Division
155M
155M Equipment
From user’s point of view, EVPLAN makes the network of operator look like a LAN. The
main differences between EVPLAN and EPLAN lie in the fact that EVPLAN users need to
share link bandwidth. EVPLAN has specific bandwidth, safety and availability attributes,
MAC address learning and data forwarding abilities.
ADM7
10GSDH Device of
Vendor B
Wavelengt ADM9
ADM8
h Division
Equipment 155M
155M
1200~3840k
m
ADM1 ADM4
80k 80k
80k 2.5GSDH Device 80k ZTE 2.5GSDH
m m
m of Vendor A m Device
Advantages of EPTREE:
Ports are granted with root node and leaf node attributes;
It is easier to expand capacity of the station and add new station afterwards.
Leaf Leaf
Root
Leaf Leaf
Leaf
The main differences between EVPTREE and EPTREE lie in the fact that the
point-to-point connection of EVPTREE is composed of EVPL and thus can share
bandwidth. EVPTREE belongs to point-to-point services.
Leaf
Leaf
Root
Leaf
Leaf
Leaf
5 EMS Configuration
(4) Limit the bandwidth rate for all related ports in the service flow;
(5) Limit the bandwidth rate for all related ports in the service flow;
The following sections will introduce methods of configuring services of different models
under different scenarios. By learning these scenarios, you can understand principles
and configuration methods of these models. Since the EVPLAN model is seldom used in
engineering, it is not mentioned above. The configuration method is almost similar except
light differences to that of EPLAN model. Since EVPLAN contains VLAN, which is not
contained in EPLAN model, please refer to the configuration method of EVPTREE.
Under the following scenarios, versions of MSTP devices used are S330 and S200. S200
is configured with TEE card to implement service transparent transmission. It is regarded
to be transparent and is not described in the manual. U1 indicated 1# user port (that is,
FE 100Mbps interface). S1 indicates 1# system port. Other ports follow this naming rule.
【Application scenario】:
Network description:
End A End B
SED TFE
U1 S1 S1 U1 End A End B
S330 S200
Service Flow
Point-to-point data service is released from End A to End B through MSTP network. The
service occupies the bandwidth of the whole service channel. Assume that the service
bandwidth is 10Mbps (that is, 5* VC12).
1. Enable 1# user port (the system port is enabled by default). Access the 【Ethernet
Port Basic Property】 interface and configure data, as shown in Figure 5-2.
2. Create UNI/NNI ports. Access the 【UNINNI Port Configuration】 interface and add
one UNI port (1# user port USER) and one NNI port (1# system port VCG). The
Binding Attribute parameters of UNI and NNI ports are all set to All to One
Bundling which indicates dedicated channel, as shown in Figure 5-3.
3. Create the MFDFr service model. Access the 【Ethernet Service Management】
interface and click Create to add an EPL service. Create UNI port 1 (UNI: 1) and
NNI port 1 (NNI: 1) on the VLAN window.
4. Set the rate of entry port. Click Band Width on the lower part of the interface, as
shown in Figure 5-5. And then, limit the bandwidth rate for UNI and NNI ports. If users do
not make special claims, you can set the bandwidth of every port to the maximum
pyhsical bandwidth 100Mbps (FE port is taken as an example to set the bandwidth here.
For GE port, the bandwidth shuold be set to 1000Mbps. This will not be mentioned below).
QoS property is set to EF, AB is set to 100000Kbps, and CBS can be set to its default
value, as shown in Figure 5-6.
5. Bundle the VCG port. Access the 【Ethernet VCG Binding】 interface and bundle
VCG EOS system port 1 with 5* VC12 ports, as shown in Figure 5-7.
EVPL models can be applied under various scenarios. The following sections describe
four most commonly used scenarios.
A、Network description
End A End B
Router Router
End B
U1 SED End A
CE-VLANID=10
U1
S330 S1 S1 S330
End C End D
Router U2 U2 Router CE-VLANID=20
End C Service Flow End D
End A needs to communicate with End B while End C needs to communicate with End D.
The two service flows are isolated from each other with a shared middle channel
bandwidth. Assume that the service VLAN in A-B service flow is 10, the service VLAN in
C-D service flow is 20, and the two service bandwidths are both 10Mbps (that is, 5*
VC12).
Mode 1:l
U1, U2, and S1 ports on bilateral cards are all set to backbone modes. Create VLAN ID:
10 (including U1 and S1 ports) and VLAN ID: 20 (including U2 and S1 ports).
Backbone mode requires that user services should contain VLAN and the actual VLAN of
the service should be known.
Mode 2:
U1 and U2 ports on bilateral cards are both set to TLS modes (PVIDs are set to 100 and
200 respectively). S1 port is set to backbone mode.
Create two VLANs (used inside ZTE equipment and have nothing to do with service
VLAN): VLAN 100 (including U1 and S1) and VLAN 200 (including U2 and S1).
This configuration mode need not know the VLAN information of user service and does
nor care about whether user service contains VLAN.
Assume that all ports in S330 traditional cards on the right side are set to backbone
modes (they can also be set to other modes only if the services are assured to be
forwarded transparently to the SED card on the left side). Create 2 ECPL services on the
left SED card. Like the backbone mod of traditional card, the actual VLAN of user service
should be known. Create two CE-VLANID (that is, VID=10, and VID=20) according to
VLAN tag of user service, as shown in Figure 5-9.
1. Enable 1# and 2# user ports (the system ports on new card are enabled by default).
Access the 【Ethernet Port Basic Property】 interface to configure data, as shown in
Figure 5-10.
Figure 5-10 EVPL Model Scenario 1—【Ethernet Port Basic Property】 Interface
3. Create the CE-VLANID List. Access the 【CE-VLAN List Management】 interface to
create 2 CE-VLAN, namely 10 and 20, as shown in Figure 5-12.
4. Create MFDFr service flow. Access 【Ethernet MFDFr Management】 interface and
click Create to create two EVPL services. The VLAN Preservation parameter is set to
Preservation by selecting the check box before Enable. Add the UNI and NNI ports for
the two EVPL service flows on the VLAN window, as shown in Figure 5-13. Choose the
correct VLANID S/N associated with each service flow in CE-VLAN column. The value of
SVLAN Label of every service flow should be unique, as shown in Figure 5-13, Figure
5-14, and Figure 5-15.
5. Set the rate of entry port. Click the Band Width tab page on the lower part in Figure
5-15 to limit the bandwidth for all ports. If users do not make special claims, all UNI and
NNI ports can be configured on the basis of port with the rate-limiting of 100Mbps. The
QoS Property parameter can be set to EF, AB can be set to 100000Kbps, and CBS can
be set to default value, as shown in Figure 5-16.
6. Bundle the VCG port. Access the 【Ethernet VCG Binding】 interface. Since the
system port is shared by two 10M bandwidth services, system port 1 bundles 10*
VC12, as shown in Figure 5-17.
Network description
End B
TFE Switch
End B CE-VLANID=10
S1 S200-1 U1
End A
Router Trunck
Router SED S1 End C
TFE Switch End CCE-VLANID=20
Trunck U1 S2 S1 U1
S330 S200-2
S3
There are many configuration methods of aggregated network. This chapter describes
the EVPL mode of new card and compares that with the backbone mode of traditional
card.
Assume that VLAN of end B is 10, of end C is 20, and of end D is 30;
Assume that the bandwidths of the three access nodes are 10Mbps (that is, 5* VC12).
S330: U1, S1, S2, and S3 ports are all set to backbone modes. Create VLAN ID: 10
(including U1, S1), VLAN ID: 20 (including U1, S2), and VLAN ID: 30 (including U1, S3).
Logically, three point-to-point services are configured.
Like the backbone mode of traditional card, new card is also configured with three
point-to-point services. Besides, the actual service VLAN of user should be known in
advance (EPTREE can be used under this scenario, please refer to the following
sections). Three EVPL services and three CE-VLAN ID (that is, VID=10, VID=20, and
VID=30) are created in SED card. The service flow is shown in Figure 5-19.
1. Enable 1# user port (the system port of new card is enabled by default). Access the
【Ethernet Port Basic Property】 interface to configure data, as shown in Figure
5-20.
Figure 5-20 EVPL Model Scenario 2—【Ethernet Port Basic Property】 Interface
3. Create the CE-VLANID List. Access the 【CE-VLAN List Management】 interface
to create three CE-VLANs, namely 10, 20, and 30, as shown in Figure 5-22.
4. Create MFDFr service flow. Access 【Ethernet MFDFr Management】 interface and
click Create to create three EVPL services. The VLAN Preservation parameter is set to
Preservation by selecting the check box before Enable. Add the UNI and NNI ports for
the three EVPL service flows on the VLAN window, as shown in Figure 5-23. Choose the
correct VLANID S/N associated with each service flow in CE-VLAN column. The value of
SVLAN Label of every service flow should be unique, as shown in Figure 5-23, Figure
5-24, Figure 5-25, and Figure 5-26.
5. Set the rate of entry port. Click the Band Width tab page on the lower part in Figure
5-26 to limit the bandwidth for all ports. If users do not make special claims, the UNI port
can be configured with three services on the basis of port+CEVLAN with rate-limiting of
100Mbps. The three NNI ports can be configured on the basis of port with rate-limiting of
100Mbps. QoS Property parameter can be set to EF, AB can be set to 100000Kbps, and
CBS can be set to default value, as shown in Figure 5-27.
6. Bundle the VCG port. Access the Ethernet VCG Binding interface. The three system
ports bundle 5* VC12, as shown in Figure 5-28.
7. Configure timeslot cross connection. Access the Cross Connection interface to cross
connect the timeslots of three system ports to different optical directions, as shown in
Figure 5-29, Figure 5-30, and Figure 5-31.
A、Network description
End B
TFE
S1 S200-1 U1 CE-VLANID=10 End B
CE-VLANID=20
CE-VLANID=30
End A Router Trunck
Router SED S1 End C
TFE
Trunck U1 S2 S1 End C
S330 S200-2 U1
S3
Service Flow
End D
TFE End D
U1
S1 S200-3
Although the network is like an aggregated network virtually, it differs with the aggregated
network under scenario 2 in service processing. Under scenario 2, ZTE transmission
equipment is transparent to users and the service VLAN is not processed in
Assume that users require marking VLAN tags: B—VLAN 10, C—VLAN 20, D—VLAN
30.
The bandwidths of the three access nodes are 10Mbps (that is, 5* VC12).
S330: S1, S2, and S3 system ports are all configured to access modes (PVIDs 10, 20,
and 30 respectively). U1 user port is configured to backbone mode. Three VLAN ID are
created: VLAN ID: 10 (including U1, and S1), VLAN ID: 20 (including U1, and S2), and
VLAN ID: 30 (including U1, and S3). Three point-to-point services are configured
logically.
The EVPL can also be used to configure parameters under this scenario. With the No
Preservation property of CE-VLANID parameter of new card, CEVLAN of system port
(that is, entry port) for every access node service is set to Untagged (that is, without tag),
and CEVLAN of user port (that is, the port to connect user router) is set to the VLAN tag
actually encapsulated for access nodes service. Three EVPL (with No Preservation
property) services and four CE-VLAN ID (that is, VID=10, VID=20, VID=30,
VID=untagged) are created. The service flow is shown in Figure 5-32. Besides, three
point-to-point services are configured logically.
1. Enable 1# user port (the system port of new card is enabled by default). Access the
Ethernet Port Basic Property interface to configure data, as shown in Figure 5-33.
Figure 5-33 EVPL Model Scenario 3—Ethernet Port Basic Property Interface
2. Create UNI/NNI ports. Access the UNINNI Interface Configuration interface to add
one UNI port (1# user port USER) and three NNI ports (1#, 2#, and 3# system port
VCG). The Bind Attribute parameters of all UNI/NNI ports are set to CE-VLAN
Bundling indicating that the ports share one channel. The NNI Multiple Link
Attribute parameter is set to Not Multiplexing, as shown in Figure 5-34.
3. Create the CE-VLANID List. Access the CE-VLAN List Management interface to
create four CE-VLANs, namely 10, 20, 30, and untagged, as shown in Figure 5-35.
4. Create MFDFr service flow. Access Ethernet MFDFr Management interface and
click Create to create three EVPL services. The VLAN Preservation parameter is
set to No Preservation by not selecting the check box before Enable. Add the UNI
and NNI ports for the three EVPL service flows on the VLAN window, as shown in
Figure 5-36. Choose the correct VLANID S/N associated with each service flow in
CE-VLAN column. The value of SVLAN Label of every service flow should be
unique, as shown in Figure 5-36, Figure 5-37, Figure 5-38, and Figure 5-39.
5. Set the rate of entry port. Click the Band Width tab page on the lower part in Figure
5-39 to limit the bandwidth for all ports. If users do not make special claims, the UNI
port can be configured with three services on the basis of port+CEVLAN with
rate-limiting of 100Mbps. The three NNI ports can be configured on the basis of port
with rate-limiting of 100Mbps. QoS Property parameter can be set to EF, AB can be
set to 100000Kbps, and CBS can be set to default value, as shown in Figure 5-40.
6. Bundle the VCG port. Access the Ethernet VCG Binding interface. The three
system ports bundle 5* VC12, as shown in Figure 5-41.
A、Network description
End A End b
Router Router
This scanario requires ends A and C communicating with remote ends B and D
respectively, that is, end A communicates with end B, end C communicates with end D.
The two services are independent of each other and do not communicate. The
networking is similar to that of scenario 1 but with mior differences. Under scenario 1,
different EVPL services share bandwidth through system ports. The overall bandwidth on
system side is actually configured to sum of the bandwidths of all access services instead
of allocating special channels for these different EVPL services. In other words, different
EVPL services are not completely isolated through system ports and there is no
independent channel logically. Under this scenario, it requires that the bandwidths of
different EVPL services between ports should be exclusive, that is, every EVPL service
should be configured with an independent bandwidth logically in the same physical
channel to isolate different EVPL services logically.
Under this scenario, each of the two EVPL services is implemented with the addition of
one outer-layer VLAN tag (that is, QinQ mode). After being processed by Ethernet card,
A-B and C-D service will not change their VLANs. After being forwarded to the shared
system port, services are added with different S-VLAN. Then, the services are forwarded
to peers. Firstly, the card will identify the services to A-B or C-D service by judging and
striping outer-layer VLANs. Then, A-B or C-D service will enter into respective flow
domain to be forwarded. During the whole process, user VLAN tag is not changed. So,
the two services are isolated from each other logically.
Assume both sides use S330, SED cards, and EVPL models. The NNI ports needs to be
set to Multiplexing, that is, QinQ mode. Assume that service VLAN between ends A and
B is 10, between end C and end D is 20, and the two service bandwidths are both
10Mbps (that is, 5* VC12).
Create two CE-VLANIDs (that is, VID=10 and VID=20) on each SED card on both sides
according to VLAN tag of user service. Assume that S-VLANID of A-B service is 100, and
that of C-D service is 200 (S-VLANID is used for forwarding services inside the
equipment and has nothing to do with VLAN tag of user service). The service flows are
shown in Figure 5-45.
CE-VLAN is set to Preservation mode and the NNI port is set to Multiplexing.
The configuration methods of SED cards on both sides are the same. So, the following
sections just take one card as an example.
1. Enable 1# and 2# user ports (the system port of new card is enabled by default).
Access the 【Ethernet Port Basic Property】 interface to configure data, as shown in
Figure 5-46.
Figure 5-46 EVPL Model Scenario 4—【Ethernet Port Basic Property】 Interface
3. Create the CE-VLANID List. Access the 【CE-VLAN List Management】 interface
to create two CE-VLANs, namely 10, 20, as shown in Figure 5-49.
4. Create MFDFr service flow. Access 【Ethernet MFDFr Management】 interface and
click Create to create two EVPL services. The VLAN Preservation parameter is set
to Preservation by selecting the check box before Enable. Add the UNI and NNI
ports for the two EVPL service flows on the VLAN window, as shown in. Choose the
correct VLANID S/N associated with each service flow in CE-VLAN column. Since
the NNI port is set to Multiplexing, S-VLAN tag will be effective, and one more layer
tag will be marked outside the original service VLAN tag to implement the QinQ
function, as shown in Figure 5-50, Figure 5-51, and Figure 5-52.
5. Set the rate of entry port. Click Band Width tab page on the lower part in Figure
5-52 to limit the bandwidth for all ports. If users do not make special claims, all the
UNI and NNI ports can be configured on the basis of port with rate-limiting of
100Mbps. QoS Property parameter can be set to EF, AB can be set to 100000Kbps,
and CBS can be set to default value, as shown in Figure 5-53.
6. Bundle the VCG port. Access the 【Ethernet VCG Binding】 interface. Since the
system port is shared by two 10M bandwidth services, system port 1 binds 10*
VC12, as shown in Figure 5-54.
Note:
This scenario is seldom used in engineering. Here describes how the S-VLAN
parameter works, and how to configure the parameter when the NNI port is set to
Multiplexing.
【Application scenario】:
A、Network description
End B
TFE Switch End B
S1 S200-1 U1 (Leaf)
End A
End A (Root) End C
Router SED S1 End C
TFE Switch (Leaf)
Trunck U1 S2 S1 U1
S330 S200-2 Service
S3 End D
Flow (Leaf)
TFE Switch
End D Root Leaf Leaf X Leaf
U1
S1 S200-3
The configurations under this scenario are the same with that under scenario 2, that is,
the convergence node S330 device just transparently forwards services without
processing the service VLAN tag. This scenario does not care about whether services
contain tag. Under this scenario, the EPTREE model is easier than EVPL models of
traditional and new cards to be used for configurations.
Assume that the bandwidths of all three access nodes are 10Mbps (that is, 5* VC12).
1. If user service contains tag, S1, S2, S3, and U1 ports should be set to backbone
mode. For detailed information, please refer to scenario 2. Besides, the actual VLAN
tag of user service must be known.
2. If the user service does not contain tag, S1, S2, S3, and U1 ports should be set to
access modes.
PVIDs of S1, S2, S3, and U1 are 10, 20, 30, and 40;
VLAN ID: 10, including U1, and S1 (for uplink services on end B);
VLAN ID: 20, including U1, and S2 (for uplink services on end C);
VLAN ID D: 30, including U1, and S3 (for uplink services on end D);
VLAN ID D: 40, including U1, S1, S2 and S3 (for downlink services on end A);
The EPTREE mode is used to configure parameters and it does not care about whether
the service itself contains VLAN tag.
1. Enable 1# and 2# user ports (the system port of new card is enabled by default).
Access the 【Ethernet Port Basic Property】 interface to configure data, as shown in
Figure 5-57.
4. Set the rate of entry port. Click the Band Width tab page on the lower part in Figure
5-60 to limit the bandwidth for all ports. If users do not make special claims, all UNI
and NNI ports can be configured on the basis of port with rate-limiting of 100Mbps.
QoS Property parameter can be set to EF, AB can be set to 100000Kbps, and CBS
can be set to default value, as shown in Figure 5-61.
5. Bundle the VCG ports. Access the 【Ethernet VCG Binding】 interface. The three
system ports bind 5* VC12, as shown in Figure 5-62.
【Application scenario】:
A、Network description:
End End B1
TFE Switch B1 (Leaf)
S1 S200- U1 EVPTREE-1: CE-VLANID=10
1 End A1 (Root) End C1
End (Leaf)
Router B2
End Tru EndD1
A1 n ck (Leaf)
SED S1 End
U1 TFE Switch
S2 S1 S200- U1 C1
S330
2 End B2
S3 EVPTREE-2: CE-VLANID=20 (Leaf)
n ck U2
Tru End
End A2 (Root)
End C2 End C2
A2 (Leaf)
End
TFE Switch End D2
S200- U1 D1 Service Flow
S1 (Leaf)
3 Lea Lea
Root Leaf X
End f f
D2
This network is also a convergence network. Scenario imitation: there are two different
application servers A1 and A2 which are used to communicate with servers associated
with every access node. The two kinds of convergence service are independent of each
other. In other words, A1 can communicate with B1, C1, and D1 (B1, C1, and D1 can not
communicate with each other), and A2 can communicate with B2, C2, and D2 (B2, C2,
and D2 can not communicate with each other).
Assume that bandwidths of all access nodes are 10Mbps (that is, 5* VC12).
S1, S2, U1, and U2 ports are all set to TLS mode (SEC card) or virtual channel access
mode (S card) (can not care about VLAN tag of user service, an outer layer tag is marked
on the entry):
Create five VLANs (these VLANs are used inside ZTE equipment and have nothing
to do with VLAN tag of user service):
VLAN ID: 10, including U1, U2, and S1 (for uplink services on end B1, and B2);
VLAN ID: 20, including U1, U2, and S2 (for uplink services on end C1, and C2);
VLAN ID: 30, including U1, U2, and S3 (for uplink services on end D1, and D2);
VLAN ID: 40, including U1, S1, S2 and S3 (for downlink services on end A1);
VLAN ID: 50, including U2, S1, S2 and S3 (for downlink services on end A2).
Under this configuration, the uplink services between B1 and B2, C1 and C2, D1 and D2
are forwarded to A1and A2 respectively (the uplink services will be isolated between
every system port). Uplink services are discarded or received being judged by the service
VLANs received on ends A1 and A2. End A1 receives services when they are checked
from ends B1, C1, and D1, and discards other services. End A2 receives services when
they are checked from ends B2, C2 and D2, and discards other services. Similarly,
downlink services on ends A1 and A1 are forwarded respectively to all access nodes
(isolated between end A1 and end A2). Terminals determine whether to receive or
discard the services according to received service VLANs.
Of course, there are other configuration methods which will not be described here.
Logically, this scenario belongs to two EPTREE services. So, two services of EVPTREE
model needs to be created. This mode is easier than that of traditional card, but the
actual service VLAN of user data should be known. The service flows is shown in Figure
5-66.
1. Enable 1# and 2# user ports (the system port of new card is enabled by default).
Access the 【Ethernet Port Basic Property】 interface to configure data, as shown in
Figure 5-67.
3. Create the CE-VLANID List. Access the 【CE-VLAN List Management】 interface
to create two CE-VLANs, namely 10, 20, as shown in Figure 5-69.
4. Create MFDFr service flow. Access 【Ethernet MFDFr Management】 interface and
click Create to create two EVPTREE services. The VLAN Preservation parameter
is set to Preservation by selecting the check box before Enable. Add UNI and NNI
ports for the two EVPTREE service flows on the VLAN window. Set accurate root
and leaf nodes in CE-VLAN column and their corresponding CE-VLAN S/Ns. The
SVLAN Label parameter of every service flow should be unique, as shown in Figure
5-70, Figure 5-71, and Figure 5-72.
5. Set the rate of entry port. Click the Band Width tab page on the lower part in Figure
5-72 to limit the bandwidth for all ports. If users do not make special claims, all UNI and
NNI ports can be configured on the basis of port with rate-limiting of 100Mbps. QoS
Property parameter can be set to EF, AB can be set to 100000Kbps, and CBS can be set
to default value, as shown in Figure 5-73.
6. Bundlt the VSG port. Access 【Ethernet VCG Binging】 interface. Since three
system ports share two 10M services, the three system ports bundle 10* VC12, as
shown in Figure 5-74.
【Application scenario】:
Network description:
Under this scenario, it requires that services can be transmitted between every two nodes
of A, B, C, and D. ZTE equipment acts as a layer 2 switch to broadcast the received
services sent from one port to other ports.
U1, S1, S2, and S3 ports are all set to access mode or TLS mode. PVID of all services
are all set to the same value, for example 10. Create one VLAN ID 10 (VLAN inside
equipment, has nothing to do with VLAN tag of user service) including UA, S1, S2, and
S3 ports.
This scenario can be configured with EPLAN model. The service flows is shown in Figure
5-78.
1. Enable 1# user ports (the system port of new card is enabled by default). Access the
【Ethernet Port Basic Property】 interface to configure data, as shown in Figure
5-79.
3. Create MFDFr service flow. Access 【Ethernet MFDFr Management】 interface and
click Create to add one EPLAN service. The VLAN Preservation parameter is set to
default value, that is, Preservation. The preservation mode can not be changed. Add UNI
and NNI ports for the EPLAN service flow on the VLAN window, as shown in Figure 5-81,
and Figure 5-82.
4. Set the rate of entry port. Click the Band Width tab page on the lower part in Figure
5-82 to limit the bandwidth for all ports. If users do not make special claims, all UNI and
NNI ports can be configured on the basis of port with rate-limiting of 100Mbps. QoS
Property parameter can be set to EF, AB can be set to 100000Kbps, and CBS can be set
to default value, as shown in Figure 5-83.
5. Bundle the VCG port. Access the 【Ethernet VCG Binding】 interface to bundle
three system ports with 5* VC12, as shown in Figure 5-84.
Since traditional cards of some versions have fewer system ports with little convergence
ratio, one single card can not meet actual need in engineering. In order to solve the
problem, you should add one more new card to increase the convergence ratio by
aggregating the two cards.
One kind is in-place level 2 convergence. Under this scenario, the two cards are set in
one node. Services are aggregated to one card, and then aggregated to the other card.
The two cards are concatenated through system ports and connected to user devices
finally, as shown in Figure 5-88.
Convergence Layer
Equipment
(Core Stations)
Router
SEC-1
U1 Notes:
S1 Red lines indicate
system ports.
Blue lines indicate
S3 S2 user ports.
S4 SEC-2
S1 S2 S3
S1 S1 S1 S1 S1
Edge Layer Edge Layer Edge Layer Edge Layer Edge Layer
Equipment Equipment Equipment Equipment Equipment
U1 U1 U1 U1 U1
Another kind is multiple access level 2 convergence. Cards to be aggregated are located
at different stations. The access services are aggregated firstly at the intermediate
stations, and then aggregated at the core stations. Cards at intermediate and core
stations are concatenated through system ports, and then connect to user devices, as
shown in Figure 5-89.
Router SEC/SFE
U1
Convergence Notes:
Layer Equipment Red lines indicate
(Core system ports.
Stations) Blue lines indicate user
ports.
S1 S2
S4 S3 Convergence
Convergence
Layer Equipment
U1 Layer Equipment U1 (Intermediate
(Intermediate
Node B Node B Stations)
Stations)
S1 SEC/SFE SEC/SFE
S2 S3
S1 S2
S1 S1 S1 S1 S1
Edge Layer Edge Layer Edge Layer Edge Layer Edge Layer
Equipment Equipment Equipment Equipment Equipment
U1 U1 U1 U1 U1
Currently, new cards also support level 2 convergence. There are 48 system ports on
SEE card and 16 system ports on SED card. So, level 2 convergence on SED card is
more commonly used in actual engineering. Besides, the level 2 convergence on SED
card is limited. The following sections will take SED card as an example to describe level
2 convergence.
The method of configuring level 2 convergence services on SED card is different from
that on traditional card. The configuration idea is described below. For related
configuration method of service model, please refer to the above sections. Assume that
access services from 20 directions are to be aggregated:
The in-place level 2 convergence should be described under two different scenarios:
transparent convergence network and nontransparent convergence network, as shown
below:
Convergence Layer
Equipment
Router (Core Stations)
U9 SED-1 S15
(NNI)
(UNI) Notes:
...
Red lines indicate
system ports.
S16(NNI) S1 Blue lines indicate
(NNI)
user ports.
S16(NNI)
SED-2
S1 S2 ...
(NNI) (NNI)
S5
(NNI)
S1 S1 S1 S1 S1
U1 U1 U1 U1 U1
... ...
Node B-16 Node B-17 Node B-20 Node B-1 Node B-15
Under this scenario, since VLAN tag of user service does not need to be processed
while user service needs to be transparently forwarded. Besides, the EPTREE model can
be used. The two cards are concatenated through system ports directly, as shown below:
SED-1 Card:
SED-2 Card:
For detailed information about the configuration of EPTREE model, please refer to the
above sections.
Convergence
Layer Equipment
Router (Core Stations)
U9 SED-1 S16
(NNI)
(UNI) Notes:
...
Red lines indicate
system ports.
U1(NNI) S1 Blue lines indicate user
(NNI)
(Physical ports.
Network Cable)
U1(UNI)
SED-2
S1 S2
(NNI) (NNI) ... S4
(NNI)
S1 S1 S1 S1 S1
Edge Layer
Equipment
Edge Layer
Equipment
... Edge Layer
Equipment
Edge Layer
Equipment
... Edge Layer
Equipment
U1 U1 U1 U1 U1
... ...
Node B-17 Node B-18 Node B-20 Node B-1 Node B-16
Under this scenario, you should care about VLAN tag of user service, that is, mark the
user access service without VLAN tag with accurate tag. The EVPL model should be
used instead of EPTREE. There is a limitation for E-line model (including EPL and EVPL)
on SED card (SEE card does not have this limitation): one end of the service flow must
be UNI while the other must be NNI, and the two ends can not both be NNI. Because of
this limitation, the two cards can be concatenated through common system ports. Or,
EVPL service flow will not be created if the ports at both ends of SED-2 card are both NNI.
As a result, the two cards can only be concatenated through physical cables between
user ports. Since the user port can be set to either UNI or NNI, the user port of SED-1
card is set to NNI while that of SED-2 card is set to UNI to create configuration condition
for EVPL service.
Assume that 20 access services themselves do not contain VLAN tags. They will be
marked with CE-VLAN ID ranging from 1 to 20 after being aggregated on SED card.
CE-VLAN ID of Node B-1 is 1, CE-VLAN ID of Node B-2 is 2, and so on, as shown below:
SED-1 card:
Create CE-VLAN ID: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17-20 and untag,
18 altogether;
EVPL-2 (No Preservation): including U9 (UNI), CE-VLAN ID=2; S2 (NNI), CE-VLAN ID=
untag;
……
EVPL-16 (No Preservation): including U9 (UNI), CE-VLAN ID=16; S16 (NNI), CE-VLAN
ID = untag;
SED-2 card:
For detailed configuration procedures of EVPL model, please refer to the above sections.
The multiple access level 2 convergence should be described under two different
scenarios: transparent convergence network and nontransparent convergence network,
as shown below:
Convergence
Router Layer Equipment
(Core Stations)
U9 SED S15
(NNI) Notes:
(UNI)
...
S16(NNI)
Convergence SED
Layer Equipment
(Intermediate
Stations) S1 S2 ...
(NNI) (NNI)
S5
(NNI)
S1 S1 S1 S1 S1
Edge Layer Edge Layer ... Edge Layer Edge Layer ... Edge Layer
Equipment Equipment Equipment Equipment Equipment
U1 U1 U1 U1 U1
... ...
Node B-16 Node B-17 Node B-20 Node B-1 Node B-15
Under this scenario, since VLAN tag of user service does not need to be processed while
user service needs to be transparently forawarded, the EPTREE model can be used. The
two card are concatenated through optical paths between system ports. This
configuration under this scenarios is similar to that under in-place level 2 convergence, as
shown below:
For detailed configuration procedures of EPTREE model, please refer to the above
sections.
Convergence Layer
Router Equipment
(Core Stations)
U9 SED S15
(NNI) Notes:
(UNI)
...
(Physical
Network Cable) S1
U1(UNI) U2
(UNI) 6
(NNI)
Convergence Layer
Equipment SED
(Intermediate Stations) ...
S1 S2 S5(NNI)
(NNI) (NNI)
S1 S1 S1 S1 S1
Edge Layer
Equipment
Edge Layer
Equipment
... Edge Layer
Equipment
Edge Layer
Equipment
... Edge Layer
Equipment
U1 U1 U1 U1 U1
... ...
Node B-16 Node B-17 Node B-20 Node B-1 Node B-15
Under this scenario, you should care about VLAN tag of user service, that is, mark the
user access service without VLAN tag with accurate tag. The EVPL model should be
used instead of EPTREE. There is a limitation for E-line model (including EPL and EVPL)
on SED card (SEE card does not have this limitation): one end of the service flow must
be UNI while the other must be NNI, the two ends can not both be NNI. Because of this
limitation, the two cards can be concatenated through common system ports. So, the
configuration conditions of EVPL services on SED cards at intermediate stations need to
be created. To create the configuration conditions, proceed as follows.
2. Connect this user port (UNI) to another user port (UNI) through physical network
cables.
3. Transparently forward the convergence services to system ports through the user
port in step 2.
4. Forward the services aggregated for the first time to SED card at core stations
through optical paths between system ports.
Assume that the 20 access services do not contain VLAN tags. They will be marked with
CE-VLAN ID ranging from 1 to 20 after being aggregated on SED card. CE-VLAN ID of
Node B-1 is 1, CE-VLAN ID of Node B-2 is 2, and so does others, as shown below:
Create CE-VLAN ID:1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16-20 and untag,
17 altogether;
……
Create CE-VLAN ID: 16, 17, 18, 19, and 20 and untag, 6 altogether;
For detailed configuration procedures of EVPL model, please refer to the above sections.
Note:
SED card of R1 version has this limitation which will be released in later versions.
When the bandwidth capacity of a port is insufficient, multiple ports should be bundled to
add bandwidth. You can use card’s link convergence function to realize the convergence.
When a port needs to be protected, multiple ports can be bundled to implement the
protection between ports. You can use card’s link convergence function to realize the
convergence.
Link convergence function is also called trunk group function. Multiple ports are
aggregated into one logical port. Currently, SED and SEE cards both support this
function.
For traditional card, because one system port can only support the bandwidth with
maximum of 100Mb/s, it not only supports link convergence of system ports but also
supports that of user ports. However, for SED and SEE cards, one of their system ports
can support the maximum bandwidth (8x155Mb/s≈1.25Gb/s normally) of the whole card,.
So, SED and SEE cards support the link convergence of user physical ports (UNI or NNI)
but not that of the system ports (there is no need to support the link convergence of
system ports). Besides, some parameters of EMS are configured to limit the link
convergence of system ports.
Currently, new card can support the trunk group. Two UNI ports form a trunk group, or
four UNI ports form a trunk group. Two NNI ports form a trunk group, or four NNI ports
form a trunk group, as shown in Figure 5-94.
Trunk Group
User SED/SEE
Equipment
User Port
UNI/NNI
User Port
UNI/NNI
The following sections describe how to configure convergence ports. Service types to
configure on the aggregated ports and the method to configure these services are the
same with that of the normal ports. For detailed information, please refer to the above
sections. Assume that you need to aggregate user physical ports 1 and 2. The SED card
is taken as an example to illustrate the configuration procedures (similar to SEE card). To
configure the parameters, proceed as follows.
Note:
ZTE Confidential Proprietary © 2012 ZTE CORPORATION. All rights reserved. 100
SED&SEE Card Service Configuration Guide Internal Use Only▲
traditional data cards but not the SED and SEE cards. The configurations of trunk
group are finished on the 【UNINNI Interface Configuration】 interface.
1. Enable 1# and 2# user ports. Access the 【Ethernet Port Basic Property】 interface
to configure data, as shown in Figure 5-95.
Caution:
Parameters of the ports belonging to the same convergence group should be the
same including rate and duplex mode.
ZTE Confidential Proprietary © 2012 ZTE CORPORATION. All rights reserved. 101
SED&SEE Card Service Configuration Guide Internal Use Only▲
Aggregation Mode: Static and Dynamic. In order to grant the trunk group with port
protection function, the LACP protocol must be enabled. Currently, there is no specific
access on new card to enable LACP protocol. The LACP protocol is enabled by selecting
Dynamitic. If Static is chosen, LACP protocol will not be enabled. Under this mode,
services can be transmitted to devices that do not support and enable LACP protocol.
Besides, Static mode does not support port protection function of the convergence group
which just acts as a normal trunk group. Under normal circumstances, you select
Dynamic to enable LACP protocol.
Select the service flow, and then click Advance on the right of the interface to check and
modify configuration information of the trunk group, as shown in Figure 5-97.
ZTE Confidential Proprietary © 2012 ZTE CORPORATION. All rights reserved. 102
SED&SEE Card Service Configuration Guide Internal Use Only▲
LACP Priority: this parameter is an optical item. If not required, it is recommended not to
confugre the parameter.
LAG ID Lag Method: Auto and Manual. Auto indicates that appropriate LACP SYS and
LACP KEY values will be set by LACP protocol according to information such as MAC
address of the port. Manual indicates that the LACP SYS and LACP KEY values will be
set manually. If not required, it is recommended to set the parameter to Auto.
LACP System ID: system ID of LACP protocol. The parameter needs to be configured
when the LAG ID Lag Method parameter is set to Manual.
LACP KEY: key value of LACP Protocol. This parameter needs to be configured when
the LAG ID Lag Method parameter is set to Manual.
After the above procedures, user port 1 and 2 are aggregated into one logical port. The
aggregated ports can be confugred as a normal port when configuring services. Of
course, the interconnected devices must be configured with trunk group.
ZTE Confidential Proprietary © 2012 ZTE CORPORATION. All rights reserved. 103
SED&SEE Card Service Configuration Guide Internal Use Only▲
1. Rates and duplex nodes of the ports belonging to the same convergence group
must be the same.
3. Two or four neighboring ports can be aggregated. For example: the mixture of two
ports to be aggregated can be: port 1 and 2, or port 3 and port 4, or port 5 and 6, or
port 7 and 8; the mixture of four ports to be aggregated can be: port 1, 2, 3, and port
4, or port 5, 6, 7, and 8.
ZTE Confidential Proprietary © 2012 ZTE CORPORATION. All rights reserved. 104
SED&SEE Card Service Configuration Guide Internal Use Only▲
AppA Reference A
ZXMP S385 SEE Card Maintenance Manual
ZTE Confidential Proprietary © 2012 ZTE CORPORATION. All rights reserved. 105