d2s 3.cross connect.pdf

7302-7360 ISAM � R4.6 High Cap. NT/5520 AMS - L2 & PPPoX forwardingNE Operation � ISAM as a L2-CC

2 � 7 � 1COPYRIGHT © ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.

Module 7ISAM as a L2-CC

Section 2NE Operation

7302-7360 ISAM

R4.6 High Cap. NT/5520 AMS - L2 & PPPoX forwarding

TAC42051_V1.1-SG Edition 2.0

TAC42050-HO09 Edition I2.0

Learning experience powered byAlcatel-Lucent University

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.


Section 2 � Module 7 �



Module objectives

Upon completion of this module, you should be able to:

� Describe the different types of cross-connect modes (S-, C-, S/C-)� Unstacked C-VLAN cross-connect

� S-VLAN cross-connect (C-VLAN transparency)

� SC-VLAN cross-connect

� VLAN translation



Section 2 � Module 7 � Page 3



Table of Contents

1 Introduction 7

2 Cross Connect 10

3 Cross Connect types 14

4 Cross Connect (MPLS) 24

Page

1 Introduction 71.1 General overview 81.2 Cross-Connect overview 92 Cross Connect 102.1 Cross connect model 113 Cross Connect types 143.1 Cross connect mode and VLAN stacking 153.2 C-VLAN cross connect 163.3 S-VLAN cross connect (C-VLAN transparency) 173.4 SC-VLAN cross connect 183.5 Protocol aware cross connect (“residential cc”) 193.6 Cross connect with protocol filtering 203.7 Cross connect VLAN translation 213.8 Summary: Cross- Connect mode 223.9 C-VLAN cross connect mode, things to consider 234 Cross Connect (MPLS) 244.1 Unified forwarding model for Access + Aggregation 254.2 MPLS Applications - Virtual Leased Line 26






1 Introduction






1 Introduction

1.1 General overview

Networkside User

side

7302 ISAM

Eth-VLAN

L2Eth - VLAN

Anything

Phys layer

ATM/AAL

Eth – (VLAN)

Anything

Phys layer

Eth – (VLAN)

Anything

layer 2 forwarding

� ethernet layer must be present at both sides

� encapsulation at CPE must include ethernet

Phys layer

GEM

Eth – (VLAN)

Anything

Intelligent Bridge (IB)VLAN Cross-Connect (CC)Enhanced iBridge

L2

Forwarding mode Decision

Forwarding models capable of handling DHCP traffic

Forwarding models capable of handling PPP traffic

CPE




In case the 7302 ISAM performs L2 forwarding, it means that the internal forwarding is

basically done on layer 2 information. The layer 2 is Ethernet, including the concept of VLANs.

In both layer 2 forwarding models (intelligent bridge as well as cross-connect), the ISAM can

accept tagged frames coming from a user. The operator can configure exactly which tag is to be expected

on the bridge port and frames carrying another tag will be discarded (filter).

In case of VLAN translation, the user sends tags that are recognized, but only have a local

meaning and will immediately be translated into a network vlan.

In case of cross-connect, it is possible to have C-VLAN transparency (where only the S-VLAN

is configured in the ISAM). In that case, the user can send no matter what C-VLAN. The ISAM will not filter

based on C-VLAN. See section on cross-connect.



1 Introduction

1.2 Cross-Connect overviewVLAN per subscriber

� One(1) “unique” VLAN per subscriber

Switch

73xx

VLAN per user

Internet

Video

NEW

Voice

Aggregation Network

IP

backboneNetwork

IP Router

Ethernet switch

AccessNetwork

VLAN user 1

VLAN user 2

VLAN user 3

VLAN user 4

VLAN user 5

VLAN user 6

Home NW






2 Cross Connect






2 Cross Connect

2.1 Cross connect model

Transparent bit pipe

� Conceptually very similar to classical ATM PVC cross-connect

One “customer”-VLAN (C-VLAN) contains strictly one user

� User port or user logical port or user on subtended interface

� Two variants: residential & business cross-connect

One user can be cross-connected to multiple VLANs

� in this case user frames need to be tagged




In cross-connect mode, the ISAM does not care about MAC addresses. The model is conceptually identical to

ATM cross-connect.

Each ATM PVC which is configured in a cross-connect mode is mapped on a unique VLAN.

Each Ethernet frame on that ATM PVC is transported transparently to this VLAN, and frames received over the

Ethernet interface with the VLAN-tag are forwarded to the PVC identified by this VLAN-tag.

It is clear that a VLAN in cross-connect mode also has the two basic properties which differentiate Intelligent

Bridging from standard bridging: no user-to-user communication is possible in the ISAM and broadcast storms

are avoided. This is because there is only a single user in case of a VLAN cross-connection.

One bit pipe per subscriber since the subscriber is identified by:

� Network side: Single or stacked (see later) VLAN tag

� User side: PVC for ATM or DSL port for EFM



2 Cross Connect

2.1 Cross connect model [cont.]

Transparent pipe for unicast, multicast and broadcast traffic

� any protocol : IP, PPP, IPX, AppleTalk,...

IP

Internet

E-MANNetwork

73xx ISAM

CPE

CPE

CPE

CPE

CPE

ISP2

ISP1

BAS




In VLAN cross-connect mode one Customer VLAN (C-VLAN) contains only one user port.

Tagged frames supported for cross-connect mode.



2 Cross Connect

2.1 Cross connect model [cont.]

Customer identified by access port

� 1 VLAN = 1 VP/VC

� or even multiple VLANs per PVC

� MAC-addresses are not used in the forwarding decision

Security

� IP edge device knows the line id

� Edge can limit number of PPP sessions per line (VP/VC)

Separation of broadcast traffic per user

Number of MAC-addresses can be limited

� enable self-learning on the DSL port




No customer segregation

In the case of cross connect mode, user-identification can be easily done on basis of this VLAN, given there is

a VLAN per user or DSL-line (even per ATM PVC). This user-identification feature should then be available in a

device higher up in the network: e.g. in a BAS where these VLANs are “terminated”. So no problem in case of

dual MAC addresses, as they are in a different VLAN anyway.

No user to user communication within ISAM

� Note: this requirement is applicable for IB mode, because ASAM, user or subtending ports may be in the

same VLAN.

� The requirement is fulfilled for cross-connections by construction, as the isolation is achieved by the one

to one port assignment (from a network interface to one user, ASAM or subtending port) of the VLANs.

All responsibilities are moved to the IP edge.



3 Cross Connect types







3.1 Cross connect mode and VLAN stacking Scalability issue:

� VLAN technology �only 4000 VLAN-ids

Scalability issue is solved by VLAN stacking:

� Customer VLAN: C-VLAN

� Service provider VLAN: S-VLAN

Cross connect types:

� C-VLAN cross connect

� S-VLAN cross connect (C-VLAN transparency)

� SC-VLAN cross connect




In the upstream direction, the incoming user port without the MAC DA is sufficient for the 7302 ISAM to

identify the outgoing upstream port and the C-VLAN tag. This C-VLAN is the port-based default VLAN

configured for this user port.

In the downstream direction, only the C-VLAN (without the MAC DA) is sufficient for the 7302 ISAM to identify

the outgoing user port.

A particular VLAN ID can be configured only once:

� on any of the user ports in the 7302 ISAM

� over all 7302 ISAMs in the complete Ethernet network to which the 7302 ISAM is connected

In order to support more VLAN cross connects, VLAN stacking will be supported if VLAN Dual Tagging Mode is

Enabled. VLAN-stacking introduces another VLAN-layer. One “outer” VLAN can bundle a number of “inner”

VLANs, similar to one LAN bundling a number of VLANs. This way, one VLAN, called the Service-VLAN or S-

VLAN, bundles a number of smaller VLANs, called Customer-VLANs or C-VLANs. More details concerning VLAN

stacking modes are discussed later in the presentation.




3.2 C-VLAN cross connect

Stack type: unstacked C-VLANs

� 1 user port per Vlan

� VLAN 333 is sent untagged towards CPE

� Untagged frames are tagged with pvid (e.g. 333)

� VLAN IDs unknown for that port are discarded

Ethernet

VLAN 333

VLAN 444

VLAN 555

#1 #2 #4

#1

#2

#3

#4

CPE

CPE




Unstacked C-VLAN cross-connect can be used for residential users.




3.3 S-VLAN cross connect (C-VLAN transparency)

Stack type: S-VLANs

� 1 or more S-VLANs per bridge port

� User is allowed to send tagged traffic (even S-tags!)

� We ignore the C-VLAN ID:

� untagged means here: no S-tag present (C-tag can be present, though!)

� single-tagged means: S-tag present (and maybe also C-tag)

S-VLAN 400 - pvid

S-VLAN 402

S

C

C

S C S C#1

#1

#2

#3

#2 #3

S-VLAN 401

S S SC C

S S SC C

CPE

CPE




S-VLAN cross-connect (C-VLAN transparency) is interesting for business users. It can offer a VPN-like service.

� e.g. tag 400 used between business sites 1 and 2 and tag 401 used between sites 1 and 3 etc.

S-VLAN cross-connect is considered a single-tag mode, just like unstacked C-VLAN cross-connect.

The following configuration is typically used by business users:

� CPE with multiple LAN interfaces

� LAN interface carries either untagged or single tag traffic

� LAN port traffic is encapsulated into an S-tag before being forwarded to the network

To fulfill with these needs currently ISAM offers (extension of the VLAN CC behaviour in order to support

configurations that are typically used for business subscribers):

�Tunnel mode (since frames are forwarded transparently in the tunnel): S-VLAN CC with N tags @ UNI, N+1tags @ NNI (add 1 tag unconditionally)

�Mapped mode (the outer tag -independently of whether there more than 1 tags present in the packet- is

checked against the list of allowed tag and if allowed, forwarded):

� C-VLAN CC with N tags @ UNI / NNI, Outer tag mapping

� S/C VLAN CC with N tags @ UNI, N+1 tags @ NNI, Outer tag mapping

� S-VLAN CC with N tags @ UNI / NNI, Outer tag mapping (backwards compatibility)




3.4 SC-VLAN cross connect

Stack type: stacked C-VLANs

� Create and Associate “Stacking VLAN” (from the AMS or CLI)

� C-VLAN IDs unknown to a bridge port are discarded

� C-VLAN ID is unique within S-VLAN

� Multiple bridge ports can share the same S-VLAN

Ethernet

c#1

c #2

#3

c #4

s c #1

s c #4

S-VLAN

s c #2

S-VLAN

CPE

CPE

CPE




SC-VLAN cross-connect can be interesting for both business and residential users.

SC-VLAN cross-connect is a dual tag mode (you configure the system settings for VLAN on the ISAM to dual tag

and all VLAN associations use dual tags).

With SC-VLAN cross-connect, the same S-tags can be used for different C-tags. Likewise, a C-tag can be

reused in combination with different S-tags.

E.g. the stacking VLAN can identify an ISAM and the C-VLAN is unique on that ISAM (e.g. each user gets a C-

VLAN id that reflects the position of the port in the ISAM � VLAN 101 = LT 1 port 1; VLAN 1648 = LT16 port 48)

� Make sure that those VLAN-ids don’t occur for a residential bridge or layer 2-terminated VLAN on the same

ISAM! In that case it will not be possible to reuse the VLAN-id.



� Protocol aware for 802.1x, DHCP, IGMP, PPPoE

� Support for “residential bridge” alike features:• DHCP option 82

• IGMP control channel (multicast applications with cross VLAN)

• PPPoE Relay tag


3.5 Protocol aware cross connect (“residential cc”)

Ethernet

VLAN 333

VLAN 444

#1 #3

#1 #2

#3

CPE

CPE




In a residential context, it is usually not desired to keep the VLAN CC fully transparent, so in that case the

operator can be make the VLAN CC “protocol aware” (also called a “residential cross connect”).

The protocol-aware VLAN cross-connect mode has the following features:

� xDSL interfaces types:

� ATM:

� Bridged encapsulation carrying both PPPoE and IPoE traffic

� PPPoA with the required interworking to convert the traffic to PPPoE

� IPoA with the required interworking to convert the traffic to IPoE

� Encapsulation auto-detection

� Ethernet: VDSL EFM, VDSL2 EFM

� Subscriber identification:

� A single (C-VLAN) or a stacked (S-VLAN/C-VLAN) VLAN tag towards the network is associated with

either a PVC (in the case of ATM) or a DSL port (in the case of EFM)

� Optional addition of the PPPoE relay tag in the PPPoE control messages

� Optional addition of the DHCP Option 82 in the DHCP messages

� No MAC address or IP address anti-spoofing since the scope of these addresses remain limited within the

protocol-aware cross-connect mode. The IP edge router or the BRAS must keep the freedom of allocating

them as they want. This control will typically be performed centrally.

� Policing per PVC (ATM) or DSL line (EFM)

� Local multicast handling: driven by IGMP. When you configure an IGMP control channel on a bridge port

or on a subscriber VLAN where you have a cross-connect network VLAN associated, the cross-connect

becomes protocol-aware!




3.6 Cross connect with protocol filtering

EthernetVLAN 333

VLAN 444

#1 #2

PPPoE traffic IPoE traffic

#1 PPPoE #2 IPoE

VP/VC : 8/36 CPE

CPE




By adding some protocol awareness in the data plane, the ISAM can provide cross-connect forwarding based

on protocol information within the ethernet frame similar to the iBridge model, i.o.w using protocol filtering.




3.7 Cross connect VLAN translation

EthernetEthernetEthernetEthernet

VLAN 333

VLAN 444

#1 #2

User X

#1

#2

#3

#3

VLAN 555

User Y

User Z

VLAN 111

CPE

CPE

CPE




Why VLAN translation?

� In case a separate VLAN needs to be used to identify a service, emulating the PVC (EFM, VDSL) we can

decouple the subscriber interface from the forwarding interface so that the user side vlan can be the

same for all users even in case of 1:1 forwarders like the Cross-connect model.

This is made possible by defining 2 vlans on a bridge port :

� a network vlan and a subscriber (user) VLAN.

� Note: it even goes further � also in case of higher layer forwarding models (routing… there can be a

subscriber vlan! In that case there is no network vlan associated to the subscriber vlan (see in another

module)

If both are different this means that VLAN translation (substitution) will take place.




3.8 Summary: Cross- Connect mode

CC: 1-1

CC: 1-1

CC: 1-1

CC: 1-1

CC: 1-1

NetVlan 11

NetVlan 21

NetVlan 31,12

NetVlan 31, 23

NetVlan 51

11 …

11…

12…

11

1231 …

21 …

…

…

…

11 …

…2331 …

51

ISAM

Ethernet

1

2

3

4

5……




All the upstream frames can be untagged, single tag or with several tags (for example, business services). If

the frame has several tag, the ISAM only analyzes the outer tag to forward it.

there are 5 different combinations in the cross-connect forwarding mode:

1. Not Adding Vlan Tag in upstream. User Vlan Specific and not translated

2. Not Adding Vlan Tag in upstream. User Vlan Specific and translated

3. Adding Vlan Tag in upstream. User Vlan Specific and not translated

4. Adding Vlan Tag in upstream. User Vlan Specific and translated

5. Adding Vlan Tag in upstream. Any User Vlan and not translated




3.9 C-VLAN cross connect mode, things to considerScalability issue:

� VLAN technology �only 4000 VLAN-ids (solved using vlan-stacking)

� Switches learn all MAC-addresses of all end-users

� IP edge learns all MAC-address<->IP-address of all end-users in ARP table

ISAM-1

ISAM-2

CPEBridge

IP1MAC1

IP2MAC2

IP3MAC3

IP101MAC101

IP102MAC102

IP103MAC103

CPEBridge

CPEBridge

IP201MAC201

IP202MAC202

IP203MAC203

BRIP edge

ARP

IP1IP2IP3IP101…

HSIA

VoIP

BTV

VoDMAC

MAC1MAC2MAC3MAC101…

CC

CC

VLAN 100

VLAN 101

VLAN 103

VLAN 102

…

VLAN 100

VLAN 101

VLAN 103

VLAN 102

…VLAN 1000

VLAN 1001

VLAN 1002

VLAN 1003

…




7302-7360 ISAM � R4.6 High Cap. NT/5520 AMS - L2 & PPPoX forwardingNE Operation � Cross Connect IACM


Module 8Cross Connect IACM

Section 2NE Operation

7302-7360 ISAM

R4.6 High Cap. NT/5520 AMS - L2 & PPPoX forwarding

TAC42051_V1.1-SG Edition 2.0


Learning experience powered byAlcatel-Lucent University






Module objectives

Upon completion of this module, you should be able to:

� Retrieve VLAN information on the system

� Associate a VLAN in cross-connect mode to a port on the IACM

� Unstacked C-VLAN cross-connect

� S-VLAN cross-connect (C-VLAN transparency)

� SC-VLAN cross-connect

� VLAN translation






Table of Contents

1 Cross Connect 7

2 Cross Connect – Vlan Association (AMS) 10

3 Cross Connect – Vlan Association (CLI) 38

4 Hands on 45

5 Annex A: Basic GPON QoS configs 59

Page

1 Cross Connect 71.1 The ISAM as a two stage box 81.2 Cross connect mode in 7302 ISAM 92 Cross Connect – Vlan Association (AMS) 102.1 CC VLAN set-up 112.2 Creation of C-VLAN 122.3 Creation of C-VLAN 132.4 Creation of C-VLAN 142.5 Show VLANs 152.6 Create VLAN association on bridge port 162.7 Define PVID on bridge port 172.8 Creation S-VLAN CC 182.9 Creation S-VLAN CC 192.10 Show VLANs 202.11 Create VLAN association on bridge port 212.12 Define PVID on bridge port 222.13 Create VLAN association on bridge port 232.14 Create VLAN association on bridge port 242.15 Define PVID on bridge port 252.16 Define PVID on bridge port 262.17 Creation SC-VLAN CC on NE. 1- “create S-Tag” 272.17 Creation SC-VLAN CC on NE. 2- “create SC-tag” 292.18 Show VLANs 322.19 SC-Type XC “VLAN association on bridge port” 332.20 Define PVID on bridge port 342.21 CC VLAN association with VLAN translation 352.22 CC VLAN association with VLAN translation 362.23 Configuration of FDB aging timer 37




2.23 Configuration of FDB aging timer 373 Cross Connect – Vlan Association (CLI) 383.1 C-VLAN cross connect via CLI 393.2 S-VLAN cross connect via CLI 403.3 Stacked VLAN cross connect via CLI 413.4 Cross-connect with vlan-translation 423.5 VLAN related show commands 433.6 Delete a VLAN 444 Hands on 454.1 Retrieval exercises 464.2 CC Vlan set up 545 Annex A: Basic GPON QoS configs 595.1 Ingress QoS profile 605.2 Bandwidth profile 61



Table of Contents [cont.]

Page






1 Cross Connect






1 Cross Connect

1.1 The ISAM as a two stage box

… will do ethernet switching

� on the NT – xHUB

� on the LT - IWF

ethernet switch = forwarding engine

� interworking = ATM �� ethernet

LT

IWF FW

Engin

e

NT

xDSL

GPON

P2P-eth

ethernet ethernet

ethernet (encapsulated)

xHUB FW

Engin

e

atm gem …

CPE






LT

External

ethernet

linksASAM

link

1 Cross Connect

1.2 Cross connect mode in 7302 ISAM

LT Cross connect mode configurable

� C-VLAN cross connect

� S-VLAN cross connect

� SC-VLAN cross connectVP/VC VLAN

8/35 100

8/37 200

Ph. Port

8/37

Ph portEFM

VLAN

x 30

FW

Engin

eFW

Engin

e

8/35

xHUB

1-16

100

200

100

200 30

30…




Remember, MAC-addresses are not used in the forwarding decision.

In the upstream direction, the incoming user port (without the MAC DA) is sufficient for the 7302 ISAM to identify the outgoing upstream port and the C-VLAN tag. This C-VLAN is the port-based default VLAN configured for this user port.

In the downstream direction, only the C-VLAN (without the MAC DA) is sufficient for the 7302 ISAM to identify the outgoing user port.

A particular VLAN ID can be configured only once:

� on any of the user ports in the 7302 ISAM

� over all 7302 ISAMs in the complete Ethernet network to which the 7302 ISAM is connected

In Cross-connect mode different models exist:

� C-VLAN cross-connect: Straightforward VLAN cross-connect model where one or more VLANs at the EMAN side are associated with a given PVC at the user side

� CC on IACM : only one end-user port (PVC or bridge port EFM) associated to a specific C-VLAN

� CC on shub: since there’s only one user associated to a specific C-VLAN on the xHUB, one ASAM-link and one or more network ports are associated to the VLAN

� S-VLAN at the EMAN side is associated with a PVC at the user side, the C-VLANs carried within the S-VLAN are then passed transparently to the end user.

� CC on IACM: only one end-user port (PVC or bridge port EFM) associated to a specific S-VLAN

� CC on SHUB: since there’s only one user associated to a specific S-VLAN on the xHUB one ASAM-link and one or more network ports are associated to the S-VLAN

� S-VLAN/C-VLAN cross-connect mode: PVC – C-VLAN mapping, where the S-VLAN tag can be used by the EMAN as route-identifier towards the ISAM

� CC on IACM : Different end-user ports (PVC or bridge port EFM) can be associated to a specific S-VLAN. The C-VLAN identifies the user-port

� CC on SHUB: since there’s can be many users associated to a specific S-VLAN on the xHUB all ASAM-link and one or more network ports are associated to the VLAN



2 Cross Connect – Vlan Association (AMS)







2.1 CC VLAN set-up

VLAN set-up:

� � create VLAN

� creation of cross connectVLAN on IACM

� � Add port to VLAN

� on LTs

Via AMS

� Different versions of one VLAN possible

� Create VLAN for

service to be deployed

� Add ports to VLAN

For GON, there is alreadysome QoS stuff

to explain and configure:

see Annex A




Here you’ll learn how to:

� Distinguish different forwarding models and choose the right VLAN mode for a certain forwarding model

� Create a VLAN on IACM using 5520AMS

� Add ports to a VLAN




2.2 Creation of C-VLAN

Network

Select NE

Infrastructure

Layer2

Create VLAN

VLAN

See next slide

C-VLAN = 700




5520AMS doesn’t use templates for VLANs. The only way to configure VLANs is on the NE itself.

For a Cross Connect C-VLAN, the S-TAG = 0.

C-VLAN:

Ethernet

VLAN 333

VLAN 444

VLAN 555

#1 #2 #4

#1

#2

#3

#4

CPE

CPE





Mode = CC




Not all parameters can be configured here already. You can configure e.g. static MAC addresses afterwards.

L2CP frames transparency

� Enabled per VLAN CC: all L2CP frames (XSTP, LACP, EFM OAM, 802.1x, GXRP,..) transparently forwarded

through the VLAN CC





protocol filter (PPPoE / IPoE)

broadcast control

PPPoE relay tag

DHCP option 82




If the PPPoE relay tag or DHCP option 82 are available, this vlan is “protocol aware”.

If the PPPoE or IPoE are selected it will be a cross-connect with protocol filtering.

Protocol aware for (802.1x, DHCP, IGMP, PPPoE):

Protocol filtering:

Ethernet

VLAN 333

VLAN 444

#1 #3

#1 #2

#3

CPE

CPE

PPPoE traffic IPoE traffic

EthernetVLAN 333

VLAN 444

#1 #2

#1 PPPoE #2 IPoE

VP/VC : 8/36CPE

CPE




2.5 Show VLANs







2.6 Create VLAN association on bridge port

Network

Select configured bridge port

Create

VLAN Association




There are 3 possible Cross Connect VLANs:

� C-VLAN CC � S_VLAN Id = 0

� S-VLAN CC � C_VLAN Id = 0

� SC-VLAN CC � S_VLAN Id and C_VLAN id = 0




2.7 Define PVID on bridge port







2.8 Creation S-VLAN CC

Network

Select NE

Infrastructure

Layer2

Create VLAN

VLAN See next slide

S-VLAN = 600




As you already know, S-VLAN CC modes offers the capability to transfer subscriber traffic in “pipes”. Two S-VLAN

CC mode variants are supported in the ISAM: the S-VLAN Tunnel CC and the S-VLAN Mapped CC.

-In Tunnel Mode, the ISAM systematically adds a VLAN-tag to frames originating from the subscriber. This mode is

enabled by configuring an S-VLAN Port as PVID.

-In Mapped Mode, the ISAM considers subscriber traffic as if already inside a tunnel originated at subscriber side. In

Mapped mode, the ISAM just extends the subscriber tunnel further to the EMAN without adding any extra VLAN-tag.

5520AMS doesn’t use templates for VLANs. The only way to configure VLANs is on the NE itself.

For a Cross Connect S-VLAN, the C-TAG = 0.

S-VLAN:

-S_VLAN: 400 (Tunnel Mode)

-S_VLAN: 401 (Mapped Mode)

S-VLAN 400 - pvid

S-VLAN 402

S

C

C

S C S C#1

#1

#2

#3

#2 #3

S-VLAN 401

S S SC C

S S SC C

CPE

CPE




2.9 Creation S-VLAN CC

mode: CC







2.10 Show VLANs








Network


Create

VLAN Association











The Vlan id is the same as the default Vlan therefore this S-Vlan is configured as a tunnel mode. I.e. ISAM adds an

extra-tag to all the frames received from the subscriber.





Network


Create

VLAN Association




There are 3 possible Cross Connect VLANs:

� C-VLAN CC � S_VLAN Id = 0

� S-VLAN CC � C_VLAN Id = 0

� SC-VLAN CC � S_VLAN Id and C_VLAN id = 0




2.17 Creation SC-VLAN CC on NE. 1- “create S-Tag”

Network

Select NE

Infrastructure

Layer2

Create VLAN

VLAN

See next slide

S-VLAN = 800

C-VLAN = 0




For a Cross Connect C-VLAN, the S-TAG = 0.

For a Cross Connect S-VLAN, the C-TAG = 0.

Eth

ern

et

c#1

c #2

#3

c #4

s c #1

s c #4

S-VLAN

s c #2

S-VLAN

CPE

CPE

CPE




2.16 Creation SC-VLAN CC on NE. 1- “create S-Tag” [cont.]

mode: L2 Terminated







2.17 Creation SC-VLAN CC on NE. 2- “create SC-tag”

Network

Select NE

Infrastructure

Layer2

Create VLAN

VLAN

See next slide

S-VLAN = 800

C-VLAN = 2000







2.17 Creation SC-VLAN CC on NE. 2- “create SC-tag” [cont.]

mode: CC







2.17 Creation SC-VLAN CC on NE. 2- “create SC-tag” [cont.]

protocol filter (PPPoE / IPoE)

broadcast control

PPPoE relay tag

DHCP option 82







2.18 Show VLANs







2.19 SC-Type XC “VLAN association on bridge port”







2.20 Define PVID on bridge port Modify VLAN association � Object details view




PortVID = Default VLAN




2.21 CC VLAN association with VLAN translation




E.g. you configure a CC VLAN association with VLAN translation on a VDSL EFM bridge port. The modem is

configured in such a way that it generates tagged traffic, e.g. local subscriber VLAN 750. This subscriber VLAN is

translated into the network C-VLAN CC 300.

� All frames returned to the subscriber should again have VLAN tag 750.

Configure that the frames returned to the subscriber should be single-tagged.

In this slide, the vlans are created.

Ethernet

VLAN 333

VLAN 444

#1 #2

User X

#1

#2

#3

#3

VLAN 555

User Y

User Z

VLAN 111

CPE

CPE

CPE




2.22 CC VLAN association with VLAN translation

Network


Create

VLAN Associationselect network VLAN

local subscriber VLAN




Vlans association (with translation) to the bridge port.

E.g. you configure a CC VLAN association with VLAN translation on a VDSL EFM bridge port. The modem is

configured in such a way that it generates tagged traffic, e.g. local subscriber VLAN 750. This subscriber VLAN is

translated into the network C-VLAN CC 300.

� All frames returned to the subscriber should again have VLAN tag 750.

Configure that the frames returned to the subscriber should be single-tagged.

VLAN Forwarding Mode:

VLAN Without Translation: if Subscriber VLAN and Network VLAN have the same value (Subscriber

part is then greyed out)

VLAN With Translation: if Subscriber VLAN and Network VLAN have a different value or when

configuring a SC-VLAN Cross Connect

NO VLAN Forwarding

Tagging Parameters:

Untagged to remove the VLAN Id on egress to the customer

Single Tagged to have the C-tag added to the customer (CPE is configured to use tagged frames)

¨Priority Tagged: VLAN value set to zero, p-bit filled in

The QoS part will be discussed in the corresponding chapter.




2.23 Configuration of FDB aging timer

LT default timer

VLAN timer (if this services needs a different timer to the LT default timer)




From R3.5 � VLAN specific aging time can be set. If set, this value will override the IACM Layer2 - Ethernet System

Parameters – Forwarding Database Aging Time. If on the other hand the default value –1 is left, the IACM system

parameter is used.

To avoid problems the LT default timer must be matched up the SHUB aging timer.

Remember, MAC-addresses are not used in the forwarding decision.



3 Cross Connect – Vlan Association (CLI)







3.1 C-VLAN cross connect via CLI

Create vlan on IACM :

� configure vlan id <VID> mode cross-connect name <name>

C-VLAN CC-association on bridge port:

� configure bridge port 1/1/./….. vlan-id <C-VID>

� pvid <C-VID>




ASAM-core:

� configure vlan id <C-VID> mode cross-connect

� configure bridge port <R/S/Slot/…> vlan-id <vlan id>

� Optional parameters:

� [no] vlan-scope: local (used for vlan translation where related vid is subscriber vlan)

default = network (no vlan translation)

� [no] pvid: default vlan id for untagged frames default = stacked:0:4097 (= no pvid)

� [no] default-priority: priority to be set in upstream frames default = 0

� [no] mac-learn-off: disable self learning of mac address

� [no] max-unicast-mac : max unicast mac addresses default = 1

� [no] accept-frame-type: accept frame types default = untagged

� …




3.2 S-VLAN cross connect via CLI

Create vlan on IACM :

� configure vlan id stacked:<S-VID>:0 mode cross-connect name <name>


� configure bridge port 1/1/./….. vlan-id stacked:<S-VID>:0

� pvid stacked:<S-VID>:0




S-vlan cross-connect is also known as C-vlan transparency. You can ignore the C-vlan entirely and simply add

an S-tag. Traffic with only a C-tag is regarded as untagged.




3.3 Stacked VLAN cross connect via CLI

Create stacking vlan on ASAM-core

� configure vlan id stacked:<S-VID>:0 mode layer2-terminated

Create cross-connect vlan on ASAM-core :

� configure vlan id stacked:<S-VID>:<C-VID> mode cross-connect name <name>


for all releases:

� configure bridge port <1/1/./…..> vlan-id stacked:<S-VID>:<C-VID>� pvid stacked:<S-VID>:<C-VID>

or – from R3.3 only:

� configure bridge port <R/S/Slot/…> vlan-id <subscriber C-VID> vlan-scopelocal network-vlan stacked:<S-VID>:<network C-VID>� pvid < subscriber C-VID>




For VLAN translation (note that the stacked C-vlan cross-connect is already an example of vlan translation!) �

see further

The stacking VLAN is a shared VLAN. Therefore, all LT-ports (ASAM-links) will have the VLAN association.




3.4 Cross-connect with vlan-translation

Besides creation of vlan(s) (cfr network-vlan) as described in former slides, the vlan-association is as follows:

for C-VLAN CC:

� configure bridge port <R/S/Slot/…> vlan-id <subscr-C-VID> vlan-scope local

� network-vlan <network-S-VID>

� pvid <subscr-S-VID>

for S-VLAN CC:


� network-vlan <network-S-VID>

� pvid <subscr-S-VID>

for S/C VLAN CC:


� network-vlan stacked:<S-VID>:<C-VID>

� pvid <subscr-C-VID>




The subscriber vlan is the one used by the subscriber to tag frames.

For C-VLAN cross-connect:

� Configure bridge port X vlan-id <subscr-C-VID> vlan-scope local

� Configure bridge port X vlan-id <subscr-C-VID> network-vlan <network-C-VID>

� Configure bridge port X pvid <subscr-C-VID>

For S-VLAN cross-connect:

� Configure bridge port X vlan-id <subscr-S-VID> vlan-scope local

� Configure bridge port X vlan-id <subscr-S-VID> network-vlan <network-S-VID>

� Configure bridge port X pvid <subscr-S-VID>

For S/C-VLAN cross-connect (stacked VLAN cross-connect):

� Configure bridge port X vlan-id <subscr-C-VID> vlan-scope local

� Configure bridge port X vlan-id <subscr-C-VID> network-vlan stacked:<S-VID>:<C-VID>

� Configure bridge port X pvid <subscr-C-VID>




3.5 VLAN related show commands

Selection of multiple show vlan commands

� on IACM:

� all bridge ports connected to C- vlan:

� show vlan cross-connect <VLAN ID>

� all MAC-addresses learned or configured on that port:

� show vlan bridge-port-fdb

� show vlan bridge-port-fdb <bridge port id>

� all MAC -adresses learned on all ports of that vlan:

� show vlan fdb-board fdbid <VLAN ID>







3.6 Delete a VLAN

you can’t delete a VLAN that has ports attached it

� and you can’t delete the VLAN-association with VLAN-id = PVID

� configure bridge port <R/S/slot/...> no pvid (if vlan id=pvid)

� configure bridge port <R/S/slot/...> no vlan-id <vlan id>

delete VLAN on ASAM-CORE

� configure vlan no id <VID>




Before you can delete a VLAN, you need to be certain that there are no member ports to this VLAN anymore:

� Example for logical user port:

� configure bridge port 1/1/4/1:8:35 no vlan-id 150

You can’t delete the VLAN if the VLAN-id = PVID. You have to delete the pvid first.

� E.g. configure bridge port 1/1/4/1:8:35 no pvid



4 Hands on






4 Hands on

4.1 Retrieval exercises

1. What is the forwarding mode of VLAN 333 (cross-connect, bridged, …)? Check with AMS and CLI

2. What are the ports assigned to VLAN 333 on the ASAM-CORE and on the xhub. Explain what you see

3. Is there a service defined on the AMS for any of the cross-connect modes? Explain for which cross-connect mode this is useful and why






4 Hands on

4.1 Retrieval exercises [cont.]

4. Explain the configuration on port TRAINING -c on VP/VC 8/35 with AMS and CLI. In the upstream? In the downstream?

5. What happens when the end-user sends a frame with VLAN tag 333?







4 Hands on



8. What happens when the end-user sends an untagged frame?

9. What happens when a frame with VLAN tag 333 is send towards the end user?

10.What happens when a frame with VLAN tag 444 is send towards the end user?







4 Hands on


12.What is the forwarding mode of VLAN 400 (cross-connect, bridged, …)? Check with AMS and CLI

13.What are the ports assigned to VLAN 400 on the ASAM-CORE and on the xhub. Explain what you see

14.Explain the configuration on port TRAINING –c on VP/VC 8/36 with AMS and CLI. What happens in the upstream? What happens in the downstream?






4 Hands on

4.1 Retrieval exercises [cont.]15.What happens when the end-user sends a frame with VLAN tag 400?

16.What happens when the end-user sends a frame with VLAN tag 500?

17.What happens when the end-user sends an untagged frame?

18.What happens when a frame with S-VLAN tag 400 and C-VLAN tag 444 is send towards the end user?








4 Hands on


21.What is the forwarding mode of VLAN 500 (cross-connect, bridged, …)? Check with AMS and CLI

22. What are the ports assigned to VLAN 500 on the ASAM-CORE and on the xhub. Explain what you see

23.Explain the configuration on port TRAINING –c on VP/VC 8/37 with AMS and CLI. In the upstream ? In the downstream?






4 Hands on





27.What happens when the end-user sends an untagged frame ?








4 Hands on




32.What happens when an untagged frame is send towards the end user?






4 Hands on

4.2 CC Vlan set up

1. Go to the port that you configured before and where the modem is connected. Delete all previous configured VLAN associations from the different logical ports.

2. Use the AMS to cross-connect PVC 8/37 with VLAN id 20x as default VLAN. Frames coming from the end user are untagged. BRAS is available on the other side. Do all what is necessary to be able to configure this setup. Verify if you receive an IP address.

Setup






4 Hands on

4.2 CC Vlan set up [cont.]

3. Use the CLI to cross-connect PVC 8/36 with VLAN id 15x as default VLAN 15X to PVC 8/36. Frames coming from the end user are untagged. DHCP server is available on the other side. Verify if you receive an IP address.

Setup






4 Hands on

4.2 CC Vlan set up [cont.]4. Delete all previous configured VLAN associations from the different

logical ports.

5. A business user has different sites, connected to different ISAMs. In there respective LAN, they use VLAN-tags. We want to connect the different sites with VLAN-id 15x in the EMAN. How do you proceed? Do all what is necessary to be able to configure this setup. Proceed with AMS and check your configuration with CLI. Verify if you have IP connectivity to end user(s) on the other sitessetup






4 Hands on


6. Delete all previous configured VLAN associations from the different logical ports.

7. Multiple end-users are connected towards the IPedge with VLAN 15x. End-users send their frames untagged. We use a VLAN tag to identify the end-user within the ISAM.Associate port 8/36 with the service going towards this IP-edge.Do all what is necessary to be able to configure this setup. Proceed with AMS and check your configuration with CLI.

Setup

8. Delete the VLAN association on bridge port linked to ATM termination 8/36. Replace it with an S-VLAN cross-connect with VLAN id 16x. Check if you get an IP-address from the DHCP server.






4 Hands on


9. VLAN translation:Delete the VLAN association on bridge port linked to ATM PVC 8/37. Replace it by a similar one (VLAN20x), but with VLAN translation. The subscriber VLAN id = 10 If the modem doesn’t generate tags, you’ll have to define PVID = 10 (which is of course not very realistic! Typically, you would do VLAN translation only if the modem sends tagged traffic. So this is simply a workaround to be able to set up a scenario with VLAN translation!)

10.Same question for S-VLAN cross-connect. Remove the S-VLAN cross-connect association on port 8/36 and replace it by a similar one with VLAN translation.Subscriber VLAN: S-VID = 20; network S-VLAN = 16x.

11.Create a (dummy – because it can be tested!) stacked cross-connect:subscriber VLAN = 30; network VLAN id = stacked:900:10x.






5 Annex A: Basic GPON QoS configs







5.1 Ingress QoS profile

configure qos profiles

ingress-qos all-in-one

dot1-p0-tc 0dot1-p1-tc 0… dot1-p7-tc 0

configure vlan id 150 mode residential-bridge

(secure-forwarding)

in-qos-prof-name name: all-in-one

all p-bits are mapped to the same TC

hence all traffic enters one single queue

the p-bit mappings are actually/also needed on the ONT

they are downloaded to the ONT when provisioning the bridge port!




The ingress qos profile corresponds more or less to the PQ-profile from the 7342!




5.2 Bandwidth profile

configure qos profiles

bandwidth CBR1000

committed-info-rate 1000

assured-info-rate 1000

excessive-info rate 1000

delay-tolerance 80

configure qos interface 1/1/5/1/33/1/1

upstream-queue 0 bandwidth-profile name:CBR1000

by default, one T-CONT will be assigned per queue,

unless bandwidth sharing is enabled!






Cross Connect IACMEnd of module




d2s 3.cross connect.pdf

Documents