NJEdge.Net

1
NJEdge.Net

• Verizon Business Ethernet Solutions

2
Ethernet Services - Summary
3
Ethernet Product Architecture Comparison
4
Verizon Switched Ethernet Service Types
5
EVPL Metro Switched Ethernet Service
6
EVPL MetroSwitched Ethernet Service

• Customer network
• Customer has three EVPL Premier UNIs and two
  EVCs, as shown below
• EVC-1 single CoS
• EVC-2 multi-CoS 50Mbps

Switch port configured as Premier Access Line,
untagged
Switch port configured as Premier Access Line,
tagged
E-UNI 100M
SES Network
E-UNI 1G
CE
6509
6509
NID
VLAN-ID123
EVC-1
A3
A1
VLAN-ID456
EVC-2
6509
All customer traffic is untagged
All customer traffic is tagged
E-UNI 100M
A2
Note For EVC-2, switch looks at VLAN_ID CoS
(p-bit) of each incoming service frame - frames
must be tagged
7
(No Transcript)
8
Ethernet Services - Summary
9
Marking CoS with SES-EVPL
10
Ethernet Service Frame

• The Layer 2 Protocol Data Unit exchanged between
  the Customer Equipment (CE) and the Metro
  Ethernet Network (MEN) at the UNI
• Standard Ethernet (IEEE 802.3-2005) frame
  structure
• With IEEE 802.1Q VLAN tag (68 to 1522 bytes)
• Without IEEE 802.1Q VLAN tag (64 to 1518 bytes)
• Includes everything but the preamble (PRE) and
  inter frame gap (IFG)
• More than 100 Million devices exist that are
  potential Customer Edge devices

11
IP Precedence and DiffServ Code Points
ID
Offset
TTL
Proto
FCS
IP SA
IP DA
Data
Len
Version Length
ToS Byte
IPv4 Packet
7
6
5
4
3
2
1
0
DiffServ Code Point (DSCP)
IP ECN

• IPv4 Three most significant bits of ToS byte are
  called IP Precedence (IPP) - other bits unused
• DiffServ Six most significant bits of ToS byte
  are called DiffServ Code Point (DSCP) - remaining
  two bits used for flow control
• DSCP is backward-compatible with IP Precedence
• DiffServ Class Selector (DSCS) also uses 3 most
  significant bits

Source Cisco training material
12
EVPL Services

• Domain
• All UNIs in a given domain must be Service
  Multiplexed
• Service Multiplexed UNI
• Offered only for 100M and 1000M UNIs (not 10M)
• Two types Untagged OR Tagged (cant be both
  on same UNI)
• CAC rules apply to UNI...more on this later...
• EVPL EVCs
• Customer gets ability to order an EVC with up to
  three CoS
• Separate speeds for each CoS
• For EVC order requiring 1 CoS ? VLAN ID is used
  to identify the CoS
• For EVC order with 2 or 3 CoS ? 2 options
• EVCCoS (VLAN ID p-bit value)
• EVCDSCP could be used to identify the CoS on
  the EVC (only for EVCs connecting two untagged
  UNIs)
• L2CPs All L2CPs are discarded at the UNI

13
Local Enterprise, EVPL-EVC, Multiple CoS

• Customer network
• Customer has three EVPL Premier UNIs and two
  EVCs, as shown below
• EVC-1 single CoS
• EVC-2 multi-CoS 50Mbps

Service Multiplexed, tagged
Service Multiplexed, untagged
E-UNI 100M
SES Network
E-UNI 1G
CE
6509
6509
NID
VLAN-ID123
EVC-1
A3
A1
VLAN-ID456
EVC-2
6509
All customer traffic is untagged
All customer traffic is tagged
E-UNI 100M
A2
Note For EVC-2, switch looks at VLAN_ID CoS
(p-bit) of each incoming service frame - frames
must be tagged
14
EVPL Considerations

• EVPL is designed for customers using routers to
  access the service...Bridge CEs may not work
  correctly...
• All traffic is policed on these UNIs ? CE cant
  burst to line rate
• CE must police/shape traffic to coordinate with
  the Bandwidth Profile of the service
• Traffic exceeding the BWP is dropped by the
  policer
• More on this later...
• Connection Admission Control (CAC) rules limit
  the number of EVCs and the aggregate bandwidth
  per CoS on a given UNI
• More on this later...

15
CoS Performance SLAs
16
SES EVPL CoS ID, Tagged UNI
Service multiplexed UNI, Premier Access Line,
Tagged
EVC1

• Two CoS ID options per EVC
• EVC a given EVC (VLAN ID) single CoS
• EVC CoS a given CoS (p-bit value) on a given
  EVC multiple CoS
• Note CoS ID options per EVC are independent,
  i.e., both can coexist on same UNI see right

CE-VLAN CoS 5,6
EVPL-RT or EVPL-PD or EVPL-B
CE-VLAN CoS 2
UNI
EVPL-RT
EVC2
CE-VLAN CoS 0
EVPL-PD
EVPL-B
17
CoS Speeds Summary
Allowable CoS Speeds per EVC, by Service Type

• EVPL CoS Speeds
• Low speed 1 to 9 Mbps, in 1M steps
• Medium speed 10 to 90 Mbps, in 10M steps
• High speed 100-1000 Mbps, in 100M steps

18
UNI Connection Admission Control (CAC) Rules

• UNI CAC rules are built into Provisioning System
• Service Multiplexed UNI - see table below

19
High-level Data Flow
Ingress UNI
Police
Classify
Forward
Switch
RX

• Apply Bandwidth Profile
• Meter each ingress CoS flow
• Mark frames (G, Y or R)
• Discard red frames

• Classify ingress traffic
• Examine each service frame and determine to which
  CoS it belongs, based on CoS ID

• Forward to egress port
• Determine egress port based on MAC forwarding
  table per EVC (VLAN)

Classify
Queuing Scheduling
TX
Egress Port

• Classify egress traffic
• Examine each frame and determine which egress
  queue it belongs in

• Priority queue treatment
• Schedule frames onto egress port based on SP and
  DWRR algorithms
• Discard frames inside individual DWRR queues
  based on W-RED

20
EVPL CoS ID Values
21
Ingress Bandwidth Profile

• A set of parameters that define the allowed rate
  of service frame flow for a given Class of
  Service
• Four bandwidth parameters used
• Committed Information Rate (CIR) in Megabits per
  second (Mbps). CIR ? 0.
• Committed Burst Size (CBS) in Kilobytes (KB). CBS
  ? MTU.
• Excess Information Rate (EIR) in Mbps. EIR ? 0
• Excess Burst Size (EBS) in KB. EBS ? 0.

22
Token Bucket Algorithm
CommittedInformationRate
ExcessInformationRate
GreenTokens
YellowTokens
Overflow
Overflow
CommittedBurst Size
ExcessBurst Size
C-Bucket
E-Bucket

• If (Service Frame length less than C-Bucket
  tokens)declare green and remove tokens from
  C-Bucket
• Else if (Service Frame length less than E-Bucket
  tokens)declare yellow and remove tokens from
  E-Bucket
• Else declare red

23
CoS Bandwidth Profiles

• Values
• X is the CoS speed ordered, Y is the CBS size
  for a given CIR rate and Z is the EBS size for
  EVPL-B
• see next slide for details on burst sizes
• Key points about bandwidth profiles
• Service frames conformant to CIR, CBS ? Green
  (SLAs apply)
• Service frames not conformant to CIR, CBS, but
  conformant to EIR, EBS ? Yellow (SLAs do not
  apply)
• Service frames not green or yellow ? Red
  (discard)
• Customer must shape traffic into the network
  according to BWP

24
CoS Burst Sizes - EVPL-RT
25
CoS Burst Sizes EVPL-PD
26
CoS Burst Sizes EVPL-B
27
Egress Queue Scheduling - UNI
Service Multiplexed UNI
SES Switch
Egress Queues
Egress port X
p-bit values
p5
p2,1
A
Q
S
p0
All-to-One Bundled UNI, Real-time
Egress port Y
p4
A
Q
S
p0

• Notes
• D-WRR scheduler (S) gives weighted access to
  Arbitrator (A) for EVPL-PD and EVPL-B frames
• Arbitrator gives strict priority to EVPL-RT
  traffic RT traffic can starve PD, BE classes
• UNI CAC rules ensure performance is met for
  guaranteed CoS, while starvation is avoided for
  Basic CoS

28
Egress Queue Scheduling - Trunk
SES Switch
Egress Queues
Egress port X
GigE Trunk
p-bit values
p5
p2,1
A
Q
p4
S
E-LAN-RT
p0

• Notes
• W-DRR scheduler (S) gives weighted access to
  Arbitrator (A) for EVPL-PD, E-LAN-RT,
  E-LAN-B and EVPL-B frames
• Arbitrator gives strict priority to EVPL-RT
  traffic RT traffic can starve PD, BE classes
• Trunk CAC rules limit EVPL-RT and EVPL-PD
  aggregate bandwidths to a age of trunk link
  capacity

29
Cisco 6509 Switch Architecture

• 9-Slot Chassis
• CatOS 8.4
• Fully Redundant Common Equipment
• Dual Supervisor Engines
• Active/Standby
• Stateful Switchover, 1-2 sec.
• Dual 720G Switch Fabric
• Dual Power Supplies
• Load Sharing
• Fans (9 per fan tray)
• Line Cards
• 48-port module for 10/100
• 24-/48-port module for GigE
• 4-port module for 10 GigE