Using VCTRUNK Port TAG Attributes to Separate Service Flow for Port

Case Title
Shared EPL
Key Word VCTRUNK, TAG Attributes, Port Shared EPL
Software O&M ✘ Data
Installation Configuration

Network Planning/Optimization
Case Type Troubleshootin
Integrated（Expansion included) g
Principle and
knowledge

Product
OptiX Product SDH
Cluster
Course Case Code
Name(4 bit) (8 bit)
Support ✘ On-site engineering
website
Source
Teaching experience

Editor Robin (ID:48588) Edit Date 2008-12-1

Instructor Reference

Preliminary Knowledge

1. Be able to configure EPL Service via T2000

2. Familiar with the concept such as VCTRUNK, PORT, VLAN ID, Ethernet service type

Teaching Methods

1. Instructor describes the project background. 5 minutes

2. Let trainees discuss the solution to reconstruct the network in groups. 10 minutes
3. Let trainees output their final plan in groups. 10 minutes
4. Instructor summarizes trainees’ solutions and presents the best solution. 5 minutes
 Using VCTRUNK Port TAG Attributes to
Separate Service Flow for Port Shared
EPL

1 Case Description

1.1 Scenario Description

There is Ethernet service between OSN and Metro1000. As we can seen below, there are
3 VC Trunks between Metro and OSN. The 3 VC Trunks share the same GE port on the
EGS4 card. Metro 1000 access UMTS equipment which does not configure VLAN ID. OSN
connects NE40 which supports VLAN ID configuration. As we know, if we want to share the
port, we can use VLAN ID to separate the service flow. In this case the client side on the
Metro1000 can not configure VLAN ID which has limited our action. So what is the
solution?

Metro1000
EFT

OSN 3500
EGS4

Metro1000
EFT

Metro1000
EFT
1.2 Alarms

No alarm.

2 Discussion and Analysis

2.1 Discussion

Let trainees discuss to output their solutions.

2.2 Analysis

1. The parameter of the Ethernet card is as below:

EFT (Metro1000) 4 FE 4 VCTRUNK 2 VC4 Internal& External Port TAG

Attributes: Hybrid

EGS4(OSN 3500) 4 GE 64 VCTRUNK 16 VC4 Internal& External Port TAG

Attributes: Customerlized ( TAG
Aware, Access, Hybrid)

2. The function of the TAG attributes of the port is as below:

Packet Port Tag Untag

Tag aware (In) Transmit transparently Discard

Tag aware (Out) Transmit transparently －

Access (In) Discard Attach default VLAN ID

Access (Out) Delete VLAN ID －

Hybrid (In) Transmit transparently Attach default VLAN ID

If VLAN ID is the same, delete the

Hybrid (Out) Tag flag, otherwise transmit －
transparently

3. The Ethernet service configuration steps are as below:

External Port; Internal Port; Bandwidth; Ethernet Service ; SDH Service ;

Remark: Link between external port and internal port; Link between internal port and
another internal port on the other NE
 SDH Network

SDH XC ETH

ETH XC SDH

2.3 Solutions

1. We can configure the TAG attributes of the internal port and set different PVID to
separate the service flow. The card will finish the task as below:

Add PVID=2
Add Remov Pass
No ID=2
PVID=1 e
ID

Hybrid Hybrid Access TAG Aware

EFT EGS4

Remark: The service from the NE40 to UMTS will be sent to different VCTRUNK based
on VLAN ID.

2.4 Suggestion and summary

1. Usually we do not care about the Internal port TAG Attributes. In this case we just take
advantage of the internal port TAG Attributes to separate the service flow. This is
because there is no ID on the Metro 1000 UMTS side. If there was VLAN ID on the
UMTS side, everything will return to normal.