A solution design for a real-time problematic scenario while handling traffic in network. Technology : Provider Bridging (802.1ad), LAG, STP

1. EFFICIENT HANDLING OF BRIDGING THE
TRAFFIC BETWEEN CUSTOMER AND
SERVICE VLAN USING PROVIDER BRIDGING
Vivek Gnanavelu
1
17-04-2014

2. OBJECTIVE
 To identify the problems while handling the traffic in
most of the deployment scenario and provide a
solution to handle them better.
 To verify the proposed solution by deploying them
on a real hardware.
2
17-04-2014

3. MOTIVATION FOR PROJECT
 There are three levels of traffic in a network topology.
1. Access 2. Metro 3. Core
 The traffic will be steadily increasing when we are
moving from Access level to the Core level
 The main challenge lies in handling the traffic better,
particularly at the core level.
 This project identifies the problems in handling, by
collecting various deployment scenario and
formulating a generalized scenario.
 This project provides solution for the generalized
problem scenario using various standards like
Provider Bridging.
3
06-06-2015

4. PROVIDER BRIDGING (PB)
06-06-2015
4
Payload
Ethernet Type
Src Address
Dst Address
Payload
Ethernet Type
VID
Src Address
Dst Address
Payload
Ethernet Type
CVID
SVID
Customer
Src Address
Customer
Dst Address
802.1D
802.1Q
802.1ad

5. PROBLEM SCENARIO
06-06-2015
[UNTAGGED]
CB1
CB2
CB3
CB4
CB5
PB1
PB2
PB3 PB4
[20-50]
[20-50]
[30-100]
[30-100]
C2
C1
C3
C4
C5
Access Metro Core
100
100
100
100
100
100
100
100
100
100
100
200
200
200
400 400
[20-50]  120
[UNTAGGED]  150
[20-50]  220
[51-100]  250VLAN Id
loop
loop
Fault
tolerance
congestion
5

6. METHODOLOGY : SOLUTION SCENARIO
06-06-2015
[UNTAGGED
]
CB1
CB2
CB3
CB4
CB5
PB1
PB2
PB3 PB4
[20-50]
[20-50]
[30-100]
[30-100]
C2
C1
C3
C4
C5
Metro Core
100
100
100
100
100
100
100
100
100
100
200
200
200
200 400
400
[20-50]  120
[UNTAGGED]  150
[20-50]  220
[51-100]  250
PB5
PB6
PB7
4+1 HSB
120  1120
150  1150
220  1220
250  1250
400400
400
ERPS
(50ms)
MSTP
RSTP
CVLAN - SVLAN
SVLAN -
SVLAN
7
6

7. RESULTS
7
Captured Packet – Customer Bridge [1-2]
06-06-2015

8. 8
Captured packet of Untagged Traffic [3]
06-06-2015

9. 9
Captured packet – Customer Bridge [4-5]
06-06-2015

10. 10
Captured Packet - Provider Bridge [VLAN 120]
06-06-2015

11. 11
Captured Packet – RSTP
06-06-2015

12. 12
Data Packet
06-06-2015

13. 13
Control Packet - ERPS
06-06-2015

14. CONCLUSION
 The project discusses on various problems in the current
traffic handling mechanisms and proposes solutions using the
standards like Provider Bridging, LAG and STP.
 The results obtained confirms the existence of the above
mentioned standards and technologies.
14
06-06-2015

15. FUTURE WORK
 In future, the project focuses on using “Provider Backbone
Bridging (PBB)”.
 PBB defines a 12 bit B-VID (backbone VLAN ID) and 24 bit I-SID
(Service Instance VLAN ID). The bridges switch the traffic being
completely unaware of the customer MAC addresses. I-SID allows
distinguishing the services within a PBB domain. Thereby, we can
provide the highest-level of security by hiding the customer MAC
addresses at the core level.
15
06-06-2015

16. REFERENCES
 Research on Double VLAN scheme in Ethernet Network, Li XinZhan, Xu
Genchao, IEEE 2009.
 Understanding Ethernet Ring Protection Switching (ERPS) for carrier
networks, Aricent Whitepaper.
 IEEE Standard for Local and metropolitan area networks “Virtual Bridged
Local Area Networks” (IEEE Standard 802.1Q-2005)
 IEEE Standard for Local and metropolitan area networks “Media Access
Control (MAC) Bridges and Virtual Bridge Local Area Networks”(IEEE
Standard 802.1Q-2011)
 IEEE Standard for Local and metropolitan area networks “Media Access
Control (MAC) Bridges and Virtual Bridge Local Area Networks”(IEEE
Standard 802.1Q-2011)
 IEEE Standard for Local and metropolitan area networks “Virtual Bridged
Local Area Networks -Provider Bridges” (IEEE Standard 802.1ad-2005) 16
06-06-2015

17. 06-06-2015
17
Thank You