RAD brocade-mobile-backhaul-solutions-dg.pdf

DEPLOYMENT GUIDE

Brocade Mobile Backhaul Solutions The Brocade-RAD-Symmetricom mobile backhaul solution is a validated end-to-end (E2E) solution delivering a graceful evolution to packet backhaul in support of all mobile generations, including 4G

SERVICE PROVIDER DEPLOYMENT GUIDE

Brocade Mobile Backhaul Solutions Page 2 of 55

CONTENTS Mobile Backhaul .............................................................................................................................................................................................................................. 4

Overview ......................................................................................................................................................................... 4

About Brocade ............................................................................................................................................................... 4

About RAD ...................................................................................................................................................................... 4

About Symmetricom ...................................................................................................................................................... 5

Brocade Router and Switch Configuration ................................................................................................................... 5

RAD Configuration.......................................................................................................................................................... 5

Wholesale Ethernet Backhaul Part 1 ....................................................................................................................................................................................... 5

Reference Architecture .................................................................................................................................................. 6

OAM & Diagnostics Tests Performed ............................................................................................................................ 7

Single Segment IEEE 802.3-2005 ........................................................................................................................ 7

OAM & Diagnostics Detailed Results ............................................................................................................................ 7

Single Segment IEEE 802.3-2005 ........................................................................................................................ 7

OAM & Diagnostics Tests Performed .......................................................................................................................... 10

End-to-end IEEE 802.1ag ITU-T Y.1731 .............................................................................................................. 10

OAM & Diagnostics Detailed Results .......................................................................................................................... 10



End-to-end: Fault monitoring and performance measurement ITU-T Y.1731 ................................................... 12


End-to-end: Fault monitoring and performance measurement ITU-T Y.1731 ................................................... 13

Quality of Service (QoS) Tests Performed ................................................................................................................... 15

General Traffic across network with EIR and CIR ............................................................................................... 15

Quality of Service (QoS) Detailed Results ................................................................................................................... 15

General Traffic across network with EIR ............................................................................................................. 15

General Traffic across network with EIR and CIR ............................................................................................... 16

General Traffic across network with CIR ............................................................................................................. 18

Diagnostic - RFC-2455 Benchmark Testing ............................................................................................................... 19

Unidirectional and Bidirectional Traffic ............................................................................................................... 19

Diagnostic - RFC-2455 Benchmark Detailed Results ................................................................................................ 20

Wholesale Ethernet Backhaul Part 2 ..................................................................................................................................................................................... 24

Reference Architecture ................................................................................................................................................ 24







Brocade Network Advisor ........................................................................................................................................................................................................... 27

Brocade Network Advisor Screen shots .............................................................................................................. 28

Wholesale Ethernet Backhaul with Clocking ....................................................................................................................................................................... 29


Test Suite per ITU-T Timing and synchronization G.8261/Y.1361 ........................................................................... 30

Clocking Test Performed ............................................................................................................................................. 30

Clocking Test Detailed Results .................................................................................................................................... 31

Baseline Testing with Symmetricom and Brocade ............................................................................................. 31

Test Case 12: Models the "Static" Packet load. ................................................................................................ 31

Test Case 13: Models sudden large, and persistent changes in network load. .............................................. 32

Test Case 14: Models the slow change in network load over an extremely long timescale. ........................... 32

Symmetricom TimeMonitor Measure Configuration .................................................................................................. 33

Spirent Network Emulator Configuration .............................................................................................................................................................................. 34

Wholesale 2G/3G/4G Backhaul ............................................................................................................................................................................................. 36


Error Free Data Transfer Tests Performed ................................................................................................................. 36

Error Free Data Transfer Detailed Results ................................................................................................................. 37

Inband Facility Loopback Test Performed .................................................................................................................. 37

Inband Facililty Loopback Detailed Results ............................................................................................................... 37

G.8032 and QoS Tests Performed .............................................................................................................................. 38

G.8032 and QoS Detailed Results .............................................................................................................................. 38


QOS ............................................................................................................................................................................... 40

Appendix A: Mobile Backhaul Configurations ..................................................................................................................................................................... 42

Brocade NetIron MLX Series Configuration ................................................................................................................ 42

Brocade NetIron CER/CES Series Configuration ........................................................................................................ 43

RAD ETX 204 Configuration ........................................................................................................................................ 45

Appendix B: Mobile Backhaul Configurations with Clocking .......................................................................................................................................... 46

Brocade Configuration to Provide QOS for Clocking .................................................................................................. 46

Customer Edge (CE) Router QoS ......................................................................................................................... 46

Provider Edge (PE) Router QOS for VLL traffic .................................................................................................... 46

Appendix C: MLX G.8032 and RAD IPmux Configurations ............................................................................................................................................ 47

Brocade MLX (RPL-Owner) configuration: ........................................................................................................... 47

RAD IPmux Configuration: .................................................................................................................................... 48

Appendix D: Supported Features and Protocols ................................................................................................................................................................. 50



MOBILE BACKHAUL Overview The Brocade-RAD-Symmetricom mobile backhaul solution provides flexible access/aggregation transport options, including native Ethernet/MPLS, and enables the cost effective delivery of new IP-based services requiring high bandwidth and superior Quality of Service (QoS). It meets all the requirements for the deployment of wholesale Ethernet backhaul with clocking and management integration.

Wholesale backhaul is typically the catalyst for service providers offering best-effort Ethernet services to enhance their offering and provide carrier Ethernet services to retail carriers and enterprise customers. While this solution focuses on wholesale mobile backhaul, it can be easily adapted to cover other wholesale and retail service delivery. It includes features such as stringent QoS, powerful OAM, SLA assurance, circuit validation, and diagnostics critical for carrier Ethernet service delivery. The solution also features Time-Division Multiplexing (TDM) pseudowire and precise clock recovery features, which are targeted more at the mobile backhaul market. About Brocade Brocade is a leading provider of high-performance data center, enterprise, and service provider networking solutions and services. Brocade develops extraordinary networking solutions that enable today’s complex, data-intensive businesses to optimize information connectivity and maximize the business value of their data. The Brocade® ServerIron® MLX Series of advanced routers delivers unprecedented scale and performance, high reliability, and cost-saving operational efficiency for the world’s most demanding service provider and enterprise networks. The Brocade NetIron® CES 2000 Series of switches provides IP routing and advanced Carrier Ethernet capabilities in a compact form factor.

For Brocade support:

• Telephone support in the US: 1-800-752-8061

• International support: www.brocade.com/services-support/contacts_international.page

• E-mail support: [email protected]

• Web support: www.brocade.com/services-support

About RAD Established nearly 30 years ago, RAD Data Communications is an award-winning manufacturer of cost-effective access and backhaul solutions for mobile and fixed line carriers, service providers, enterprises, government agencies, transportation systems, and public utilities. RAD is a preferred solutions provider for more than 150 carriers around the world, from Tier 1 mobile operators to fixed line incumbents, wholesale service providers, city carriers, ISPs, and rural service telephone companies.

Beyond its strong ties with telecom providers, RAD maintains extensive relationships with enterprise network professionals in the banking, commercial, educational, energy, financial, government and defense, manufacturing, and transportation sectors.

For RAD support:

• Telephone Support: 1-800-444-7234, option 3

• Technical Assistance: www.radusa.com/3-11318/Technical-Assistance/

• RADcare International: www.rad.com/3-3653/RADcare/

http://www.brocade.com/services-support/contacts_international.page�

mailto:[email protected]�

http://www.brocade.com/services-support�

http://www.radusa.com/3-11318/Technical-Assistance/�

http://www.rad.com/3-3653/RADcare/�



About Symmetricom Symmetricom is the world’s leading source of highly precise timekeeping technologies, instruments, and solutions. We provide timekeeping in GPS satellites, national time references, and national power grids as well as in critical military and civilian networks, including those that enable next-generation data, voice, mobile and video networks, and services. We assist customers in over 90 countries to generate, distribute, and apply time.

Our product offering—among the industry’s broadest—includes atomic clocks, hydrogen masers, timescale systems, GPS instrumentation, synchronous supply units, standards-based clients and servers, performance measurement and management tools, and embedded subsystems that generate, distribute, and apply precise frequency and time.

For Symmetricom Support:

• Telephone support in the US: 1-888-FOR SYMM (1-888-367-7966)

• Worldwide Main number: 1-408-428-7907

• Online Support: www.symmetricom.com/support/online-support/

Brocade Router and Switch Configuration • Brocade Carrier-Class MLX routers were configured as part of the Carrier Ethernet MPLS (Multiprotocol

Label Switching) core.

• Brocade Aggregation CER/CES switches were configured as the PE (Provider Edge) with MPLS and VLL (Virtual Leased Line) tunnels.

See Appendix A for configuration example. RAD Configuration • The RAD ETX is a Carrier Ethernet Demarcation Device. These devices are owned and operated by the

server provider and installed at the customer premises.

• The ETXs were configured with flow-based services. Different services are assigned to different Ethernet flows and received by the same user port. Ingress user traffic was created on VLANs.

See Appendix A for configuration example.

WHOLESALE ETHERNET BACKHAUL PART 1 This demonstrates RAD ETX to RAD ETX across MPLS Core. End to end testing was performed with RAD ETX 204A to a remote RAD ETX 204A via MPLS through Brocade MLX routers.

Data VLAN was configured to carry customer traffic; Operations, Administration, and Maintenance (OAM); and test data. Management VLAN was configured to manage equipment and retrieve statics.

Operations and Maintenance (OAM) is used to monitor the health of a network and diagnose problems without maintenance truck rolls. OAM is required for connectivity verification, especially for connectionless protocols such as Ethernet (otherwise when there is no traffic, there is no verification of connectivity).

The Ethernet OAM standard IEEE 802.3-2005 (formerly 802.3ah Ethernet in first mile) is important for link monitoring procedures, including auto-discovery, heartbeat, and fault notification messages; link statistics; MIB variable retrieval; and remote loopbacks.

IEEE 802.1ag and ITU-T Y.1731 provide mechanisms for Connectivity Fault Management (CFM) and Performance Management (PM) over any path, whether single link or end-to-end, allowing the service provider to manage each EVC separately regardless of the underlying transport.

http://www.symmetricom.com/support/online-support/�



Quality of Service (QoS) enables better service to certain flows over other. RAD and Brocade validated end-to-end QoS starting with comprehensive traffic management at the demarcation device and continuing across the network.

RFC-2544 benchmark testing is vital to provide performance metrics for the Ethernet network. Key tests include the measurement of throughput, latency and frame loss.

Reference Architecture The solution components are listed below and show in Figure 1:

• 4 x Brocade NetIron MLX (v5.0)

• 1 x Brocade NetIron CER (v5.1)

• 1 x Brocade NetIron CES (v5.1)

• 2 x RAD ETX 204A (v2.2)

• Brocade Network Advisor

• I/O Generator

Figure 1. Mobile backhaul topology



OAM & Diagnostics Tests Performed Single Segment IEEE 802.3-2005

1. Auto Discovery - discovers if next hop supports 802.3ah and what are the peer’s advertized capabilities. 2. Connectivity Check – supports passive mode designed for network termination 3. Remote loop back -remote layer 1 loopback of all traffic (Excludes 802.3ah OAM messages from loopback) 4. Fault propagation

a. Network-to-user fault propagation mechanism on the port and OAM CFM levels – When fault propagation is enabled, the user port shuts itself down or an OAM CFM indication of failure is sent when a link failure is detected at the network port or when an OAM CFM indication of failure is received.

b. User-to-network fault propagation mechanism on the port and OAM CFM levels – When fault propagation is enabled, the network port shuts itself down or an OAM CFM indication of failure is sent when a link failure is detected at the user port or an OAM CFM indication of failure is received.

OAM & Diagnostics Detailed Results Single Segment IEEE 802.3-2005 OAM Loopback Control Remote loopback configured on CES and detected on ETX2 CES output CES#link- remote-loop-back ethernet 1/1 start start loopback CES#sh link-o i d OAM information for Ethernet port: 1/1 +link-oam mode: active +link status: up +oam status: up Local information multiplexer action: forward parse action: discard stable: satisfied state: up loopback state: disabled dying-gasp: false critical-event: false link-fault: false Remote information multiplexer action: discard parse action: loopback stable: satisfied loopback support: enabled dying-gasp: false critical-event: false link-fault: false ETX2 output ETX-204-2>config>port>eth(1)# show oam-efm Administrative Status : Enabled Operetional Status : Operational Loopback Status : Local



OAM EFM Information ----------------------------------------------------------------------------- Local Remote MAC Address : 00-20-D2-50-04-12 74-8E-F8-1E-03-C1 Mode : Passive Active Unidirectional : Not Supported Not Supported Vars Retrieval : Supported Supported Link Events : Supported Supported Loopback : Supported Not Supported PDU Size : 1518 1518 Vendor OUI : 0x0020D2 0x000000 CES outputs CES#link- remote-loop-back ethernet 1/1 stop stop loopback CES#sh link-o i d OAM information for Ethernet port: 1/1 +link-oam mode: active +link status: up +oam status: up Local information multiplexer action: forward parse action: forward stable: satisfied state: up loopback state: disabled dying-gasp: false critical-event: false link-fault: false Remote information multiplexer action: forward parse action: forward stable: satisfied loopback support: enabled dying-gasp: false critical-event: false link-fault: false ETX2 output ETX-204-2>config>port>eth(1)# show oam-efm Administrative Status : Enabled Operetional Status : Operational Loopback Status : Off OAM EFM Information ----------------------------------------------------------------------------- Local Remote MAC Address : 00-20-D2-50-04-12 74-8E-F8-1E-03-C1 Mode : Passive Active Unidirectional : Not Supported Not Supported Vars Retrieval : Supported Supported Link Events : Supported Supported Loopback : Supported Not Supported PDU Size : 1518 1518 Vendor OUI : 0x0020D2 0x000000



OAM Events Dying gasp and Link fault CES output CES(config-link_oam)#sh link-o i d pull cable OAM information for Ethernet port: 1/1 +link-oam mode: active +link status: down +oam status: down Local information multiplexer action: forward parse action: forward stable: unsatisfied state: linkFault loopback state: disabled dying-gasp: false critical-event: false link-fault: true Remote information multiplexer action: forward parse action: forward stable: unsatisfied loopback support: enabled dying-gasp: true critical-event: false link-fault: false CES output CES(config-link_oam)#sh link-o i d plug back cable OAM information for Ethernet port: 1/1 +link-oam mode: active +link status: up +oam status: down Local information multiplexer action: forward parse action: forward stable: satisfied state: sendLocalAndRemoteOk loopback state: disabled dying-gasp: false critical-event: false link-fault: false Remote information multiplexer action: forward parse action: forward stable: unsatisfied loopback support: enabled dying-gasp: false critical-event: false link-fault: false



Active & Passive mode OAM Discovery CES output CES#show link-oam info Ethernet Link Status OAM Status Mode Local Stable Remote Stable 1/1 up up active satisfied satisfied

OAM & Diagnostics Tests Performed End-to-end IEEE 802.1ag ITU-T Y.1731

1. Continuity check (CC) OAM a. messages are sent every 1 second b. Continity check can be defined per EVC c. Loss of Continuity (LOC)

i. Declare LOC – Upon 3.5 seconds without receiving CC OAM frame ii. Recovery – 2 CC OAM frames within a window of 3.5 seconds

d. Upon CC failure i. Update active alarm log ii. Update statistics

2. Loop back (LB) OAM a. Standard 802.1ag implementation Non intrusive, defined per EVC and applies to OAM

messages only b. Required for performance monitoring

3. Link trace OAM & Diagnostics Detailed Results End-to-end IEEE 802.1ag ITU-T Y.1731 ETX1 OAM config OAM CFM Configuration multicast-addr 01-80-C2-00-00-30 maintenance-domain 1 no proprietary-cc md-level 4 name string "MD1" maintenance-association 1 name string "MA1" ccm-interval 1s Continuity Check interval mep 1 Local MEP classification vlan 100 queue fixed 0 block 0/1 remote-mep 2 Remote MEP dest-addr-type ccm multicast pm unicast ccm-initiate ccm-priority 5 no shutdown



service 1 delay-threshold 30 delay-var-threshold 8 classification priority-bit 5 interval 1s dest-ne 1 remote mep-id 2 pm single-ended-loss pm two-way-delay exit no shutdown exit ETX1 OAM output ETX-204-1>config>oam>cfm>md(1)>ma(1)>mep(1)# show status Port : Ethernet 1 VLAN : 100 Priority : 5 MD Name : MD1 MA Name : MA1 Cross Connect Status : OK Remote MEP Remote MEP Address Operational Status ----------------------------------------------------------------------------- 2 00-20-D2-50-04-12 OK

ETX2 OAM config OAM CFM Configuration multicast-addr 01-80-C2-00-00-30 maintenance-domain 1 no proprietary-cc md-level 4 name string "MD1" maintenance-association 1 name string "MA1" ccm-interval 1s Continuity Check interval mep 2 Local MEP classification vlan 100 queue fixed 0 block 0/1 remote-mep 1 Remote MEP dest-addr-type ccm multicast pm unicast ccm-initiate ccm-priority 5 no shutdown service 1 delay-threshold 30 delay-var-threshold 5 classification priority-bit 5 interval 1s dest-ne 1 remote mep-id 1 pm single-ended-loss pm two-way-delay



exit no shutdown exit ETX2 OAM output ETX-204-2>config>oam>cfm>md(1)>ma(1)>mep(2)# show status Port : Ethernet 1 VLAN : 100 Priority : 5 MD Name : MD1 MA Name : MA1 Cross Connect Status : OK Remote MEP Remote MEP Address Operational Status ----------------------------------------------------------------------------- 1 00-20-D2-50-07-9D OK ETX2 sends LBM (Loopback Message) to remote ETX1 ETX-204-2>config>oam>cfm>md(1)>ma(1)>mep(2)# lbm remote-mep 1 repeat 5 ETX-204-2>config>oam>cfm>md(1)>ma(1)>mep(2)# show lbm-results Remote MEP ID : 1 Destination Address : 00-20-D2-50-07-9D Messages Sent : 5 Replies In Order : 5 Replies Out Of Order : 0 Messages Lost/Timed Out : 0 Messages Lost/Timed Out % : 0 ETX2 sends link trace message to remote ETX1 ETX-204-2>config>oam>cfm>md(1)>ma(1)>mep(2)# linktrace remote-mep 1 ETX-204-2>config>oam>cfm>md(1)>ma(1)>mep(2)# show linktrace-results LTR ----------------------------------------------------------------------------- Hop : 1 Relay Action : Hit Ingress Action : Ingress OK Egress Action : No TLV Ingress Port Sub Type : Interface Alias Ingress Port ID : ETH 1 Ingress MAC Address : 00-20-D2-50-07-9D OAM & Diagnostics Tests Performed End-to-end: Fault monitoring and performance measurement ITU-T Y.1731

1. Performance Monitoring (PM) OAM a. PM per Ethernet Virtual Connection (EVC) up to 64 PM instances

i. Frame Delay ii. Frame Delay Variation iii. Frame Loss iv. Availability

b. Traps can be defined per EVC per parameter with threshold



2. OAM PM Statistics a. 15 minutes intervals b. Record of last 24 hours stored (96 cyclic intervals kept)

3. Additional PM (not OAM related) a. Performance Measurements per port such as dropped frames, oversize frames etc b. Traps with thresholds “Rising” and “Falling” thresholds definition

OAM & Diagnostics Detailed Results End-to-end: Fault monitoring and performance measurement ITU-T Y.1731 Performance measurement was taken over a 24 hour period. ETX output ETX-204-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# show stat all Running ----------------------------------------------------------------------------- Transmitted Frames : 855428 Near End Frames Loss : 0 Near End Frames Loss Ratio : 0 Far End Frames Loss : 0 Far End Frames Loss Ratio : 0 Elapsed Time (Seconds) : 427719 Unavailable Seconds (Seconds) : 20 Unavailable Ratio : 4 exp(-5) Frames Above Delay : 0 Frames Above Delay Variation : 0 Current Delay : 0.4 Current Delay Variation : 0.1 Current ----------------------------------------------------------------------------- Above Delay Threshold : 0 Below Delay Threshold : 203 Above Delay Var Threshold : 0 Below Delay Var Threshold : 205 Transmitted Frames : 410 Near End Frames Loss : 0 Far End Frames Loss : 0 Min Round Trip Delay (msec) : 0.2 Max Round Trip Delay (msec) : 0.5 Avg Round Trip Delay (msec) : 0.3 Max Round Trip Delay Var (msec) : 0.2 Avg Round Trip Delay Var (msec) : 0.0 Elapsed Time (Seconds) : 205 Unavailable Seconds (Seconds) : 0 Interval ----------------------------------------------------------------------------- Interval ----------------------------------------------------------------------------- Interval : 1 first interval (15 minutes)



Above Delay Threshold : 0 Below Delay Threshold : 900 Above Delay Var Threshold : 0 Below Delay Var Threshold : 900 Transmitted Frames : 1800 Near End Frames Loss : 0 Far End Frames Loss : 0 Min Round Trip Delay (msec) : 0.2 Max Round Trip Delay (msec) : 0.5 Avg Round Trip Delay (msec) : 0.3 Max Round Trip Delay Var (msec) : 0.3 Avg Round Trip Delay Var (msec) : 0.0 Unavailable Seconds (Seconds) : 0 Interval ----------------------------------------------------------------------------- Interval : 2 second interval (30 minutes) Above Delay Threshold : 0 Below Delay Threshold : 900 Above Delay Var Threshold : 0 Below Delay Var Threshold : 900 Transmitted Frames : 1800 Near End Frames Loss : 0 Far End Frames Loss : 0 Min Round Trip Delay (msec) : 0.2

Max Round Trip Delay (msec) : 0.6 Avg Round Trip Delay (msec) : 0.3 Max Round Trip Delay Var (msec) : 0.4 Avg Round Trip Delay Var (msec) : 0.0 Unavailable Seconds (Seconds) : 0

****Interval 3-94 not printed in the Test Results**** Interval ----------------------------------------------------------------------------- Interval : 95 95th interval (1425 min or 23.75 hrs) Above Delay Threshold : 0 Below Delay Threshold : 900 Above Delay Var Threshold : 0 Below Delay Var Threshold : 900 Transmitted Frames : 1800 Near End Frames Loss : 0 Far End Frames Loss : 0 Min Round Trip Delay (msec) : 0.2 Max Round Trip Delay (msec) : 0.6 Avg Round Trip Delay (msec) : 0.2 Max Round Trip Delay Var (msec) : 0.4 Avg Round Trip Delay Var (msec) : 0.0 Unavailable Seconds (Seconds) : 0 Interval



----------------------------------------------------------------------------- Interval : 96 96th interval (1440 min or 24 hrs) Above Delay Threshold : 0 Below Delay Threshold : 900 Above Delay Var Threshold : 0 Below Delay Var Threshold : 900 Transmitted Frames : 1800 Near End Frames Loss : 0 Far End Frames Loss : 0 Min Round Trip Delay (msec) : 0.2 Max Round Trip Delay (msec) : 0.4 Avg Round Trip Delay (msec) : 0.3 Max Round Trip Delay Var (msec) : 0.3 Avg Round Trip Delay Var (msec) : 0.0 Unavailable Seconds (Seconds) : 0 Quality of Service (QoS) Tests Performed General Traffic across network with EIR and CIR

1. All user traffic configured for Excess Information Rate (EIR) EIR=1G CIR=0 User Traffic = VLAN 50 (C-Vlan) Stacking S-Tag=100 Approximately 1 minute testing

2. User traffic configured for 50% Excess Information Rate (EIR ) and 50% Committed Information Rate (CIR)

EIR=500M CIR=500M User Traffic = VLAN 50 (C-Vlan)

Stacking S-Tag=100 Approximately 1 minute testing

3. All user traffic configured for Committed Information Rate (CIR) EIR=0 CIR=1G

User Traffic = VLAN 50 (C-Vlan) Stacking S-Tag=100 Approximately 1 minute testing

Quality of Service (QoS) Detailed Results General Traffic across network with EIR ETX 1 – Flow Service 100 statistics: ETX-204-1>config>flows>flow(service100)# show stat run Rate Sampling Window ----------------------------------------------------------------------------- Window Size [Min.] : 15 Window Remain Time [Min.] : 3 Rx Statistics ----------------------------------------------------------------------------- Total Packets : 2936207 Bytes : 4404310500



Drop Statistics ----------------------------------------------------------------------------- Total Green Yellow/Red Packets : 0 0 0 Rate [pps] : 0 0 0 Bytes : 0 0 0 Rate [bps] : 0 0 0 Tx Statistics ----------------------------------------------------------------------------- Total Green Yellow EIR Packets : 2936207 0 2936207 Rate [pps] : 4182 0 4182 Bytes : 4404310500 0 4404310500 Rate [bps] : 50191568 0 50191568 Pick Measurement ----------------------------------------------------------------------------- Min. Max. Tx Bit Rate [bps] : 0 493516360 Drop Bit Rate [bps] : 0 0 ETX 2 – Flow Service 100 statistics: ETX-204-2>config>flows>flow(service100)# show stat run Rate Sampling Window ----------------------------------------------------------------------------- Window Size [Min.] : 15 Window Remain Time [Min.] : 12 Rx Statistics ----------------------------------------------------------------------------- Total Packets : 2937767 Bytes : 4406650500 Drop Statistics ----------------------------------------------------------------------------- Total Green Yellow/Red Packets : 0 0 0 Rate [pps] : 0 0 0 Bytes : 0 0 0 Rate [bps] : 0 0 0 Tx Statistics ----------------------------------------------------------------------------- Total Green Yellow EIR Packets : 2937767 0 2937767 Rate [pps] : 13626 0 13626 Bytes : 4406650500 0 4406650500 Rate [bps] : 163519168 0 163519168 Pick Measurement ----------------------------------------------------------------------------- Min. Max. Tx Bit Rate [bps] : 0 493516360 Drop Bit Rate [bps] : 0 0 General Traffic across network with EIR and CIR



ETX 1 – Flow Service100 statistics: ETX-204-1>config>flows>flow(service100)# show stat run Rate Sampling Window ----------------------------------------------------------------------------- Window Size [Min.] : 15 Window Remain Time [Min.] : 5 Rx Statistics ----------------------------------------------------------------------------- Total Packets : 4538578 Bytes : 6807867000 Drop Statistics ----------------------------------------------------------------------------- Total Green Yellow/Red Packets : 0 0 0 Rate [pps] : 0 0 0 Bytes : 0 0 0 Rate [bps] : 0 0 0 Tx Statistics ----------------------------------------------------------------------------- Total Green CIR Yellow EIR Packets : 4538578 2416650 2121928 Rate [pps] : 7602 4047 3554 Bytes : 6807867000 3624975000 3182892000 Rate [bps] : 91227696 48575872 42651816 Pick Measurement ----------------------------------------------------------------------------- Min. Max. Tx Bit Rate [bps] : 0 937701816 Drop Bit Rate [bps] : 0 0 ETX 2 – Flow Service1_egress statistics: ETX-204-2>config>flows>flow(service1_egress)# show stat run Rate Sampling Window ----------------------------------------------------------------------------- Window Size [Min.] : 15 Window Remain Time [Min.] : 14 Rx Statistics ----------------------------------------------------------------------------- Total Packets : 4538578 Bytes : 6826021312 Drop Statistics ----------------------------------------------------------------------------- Total Green Yellow/Red Packets : 0 0 0 Rate [pps] : 0 0 0 Bytes : 0 0 0 Rate [bps] : 0 0 0 Tx Statistics ----------------------------------------------------------------------------- Total Green CIR Yellow EIR Packets : 4538578 2410211 2128367



Rate [pps] : 0 0 0 Bytes : 6826021312 3624957344 3201063968 Rate [bps] : 0 0 0 Pick Measurement ----------------------------------------------------------------------------- Min. Max. Tx Bit Rate [bps] : 0 0 Drop Bit Rate [bps] : 0 0 General Traffic across network with CIR ETX1 – Flow Service100 statistics: ETX-204-1>config>flows>flow(service100)# show stat run Rate Sampling Window ----------------------------------------------------------------------------- Window Size [Min.] : 15 Window Remain Time [Min.] : 6 Rx Statistics ----------------------------------------------------------------------------- Total Packets : 5358871 Bytes : 8038306500 Drop Statistics ----------------------------------------------------------------------------- Total Green Yellow/Red Packets : 0 0 0 Rate [pps] : 0 0 0 Bytes : 0 0 0 Rate [bps] : 0 0 0 Tx Statistics ----------------------------------------------------------------------------- Total Green CIR Yellow Packets : 5358871 5358871 0 Rate [pps] : 11026 11026 0 Bytes : 8038306500 8038306500 0 Rate [bps] : 132317800 132317800 0 Pick Measurement ----------------------------------------------------------------------------- Min. Max. Tx Bit Rate [bps] : 0 937832720 Drop Bit Rate [bps] : 0 0 ETX2 – Flow Service1_egress statistics: ETX-204-2>config>flows>flow(service1_egress)# show stat run Rate Sampling Window ----------------------------------------------------------------------------- Window Size [Min.] : 15 Window Remain Time [Min.] : 1 Rx Statistics



----------------------------------------------------------------------------- Total Packets : 5358871 Bytes : 8059741984 Drop Statistics ----------------------------------------------------------------------------- Total Green Yellow/Red Packets : 0 0 0 Rate [pps] : 0 0 0 Bytes : 0 0 0 Rate [bps] : 0 0 0 Tx Statistics ----------------------------------------------------------------------------- Total Green CIR Yellow Packets : 5358871 5358871 0 Rate [pps] : 6472 6472 0 Bytes : 8059741984 8059741984 0 Rate [bps] : 77871896 77871896 0 Pick Measurement ----------------------------------------------------------------------------- Min. Max. Tx Bit Rate [bps] : 0 940618000 Drop Bit Rate [bps] : 0 0

Diagnostic - RFC-2455 Benchmark Testing Unidirectional and Bidirectional Traffic RFC -2544 Throughput

a) Unidirectional

i) Local ETX generates TST messages towards the far end ii) Far end device verifies messages and calculates unidirectional throughput iii) The convergence algorithm is based a binary search using LMM and LMR messages iv) Latency v) Frame Loss vi) Back to back

(1) Frame testing involves sending a burst of frame with minimum inter-frame gaps to the DUT and count the number of frames forwarded by the DUT.

(2) If the count of transmitted frames is equal to the number of frames forwarded, the length of the burst is increased and the test is rerun.

vii) If the number of forwarded frames is less than the number transmitted, the length of the burst is reduced and the test is rerun.

viii) The back-to-back value is the number of frames in the longest burst that the DUT will handle without the loss of any frames.

b) Bidirectional i) Local ETX generates LBM + data TLV messages towards the far end ii) Far end devices responds with LBR messages



Diagnostic - RFC-2455 Benchmark Detailed Results

RFC – 2544 Unidirectional Throughput

RFC -2544 Unidirectional Latency



RFC – 2544 Unidirectional Frame loss

RFC – 2544 Unidirectional Back to Back



RFC – 2544 Bidirectional Throughput

RFC -2544 Bidirectional Latency



RFC – 2544 Bidirectional Frame Loss

RFC – 2544 Bidirectional Back to Back



WHOLESALE ETHERNET BACKHAUL PART 2 This demonstrates RAD ETX to Brocade CES RAD ETX across MPLS Core. End to end testing were repeated with RAD ETX 204A to a remote CES via MPLS through Brocade MLX routers. Since many of the results performed for part 2 were identical or very similar to part 1, they were not included in the Deployment Guide. Only those tests with different result outputs or different configuration are included in the Deployment Guide. Reference Architecture The solution components are listed below and show in Figure 2:

• 4 x Brocade NetIron MLX (v5.0) • 1 x Brocade NetIron CER (v5.1) • 1 x Brocade NetIron CES (v5.1) • 1 x RAD ETX 204A (v2.2) • Brocade Network Advisor • I/O Generator

Figure 2. Mobile Backhaul Topology

OAM & Diagnostics Tests Performed End-to-end IEEE 802.1ag ITU-T Y.1731

1. Continuity check (CC) OAM a. messages are sent every 1 second b. Continity check can be defined per EVC



c. Loss of Continuity (LOC) i. Declare LOC – Upon 3.5 seconds without receiving CC OAM frame ii. Recovery – 2 CC OAM frames within a window of 3.5 seconds

d. Upon CC failure i. Update active alarm log ii. Update statistics

2. Loop back (LB) OAM a. Standard 802.1ag implementation Non intrusive, defined per EVC and applies to OAM

messages only b. Required for performance monitoring

3. Link trace OAM & Diagnostics Detailed Results End-to-end IEEE 802.1ag ITU-T Y.1731 CES CFM Config cfm-enable domain-name MD1 id 1 level 4 ma-name MA1 id 1 vlan-id 100 priority 5 mep 3 down port ethe 1/2 Local MEP remote-mep 1 to 1 Remote MEP

ETX1 CFM config OAM CFM Configuration multicast-addr 01-80-C2-00-00-30 maintenance-domain 1 no proprietary-cc md-level 4 name string "MD1" maintenance-association 1 name string "MA1" ccm-interval 1s Continuity Check interval mep 1 Local MEP classification vlan 100 queue fixed 0 block 0/1 remote-mep 2 remote-mep 3 Remote MEP dest-addr-type ccm multicast pm unicast ccm-initiate ccm-priority 5 no shutdown service 1 delay-threshold 30 delay-var-threshold 8 classification priority-bit 5 interval 1s dest-ne 1 remote mep-id 2 pm single-ended-loss pm two-way-delay exit no shutdown



exit

CES Outputs CES#show cfm Domain: MD1 Index: 1 Level: 4 Maintenance association: MA1 Ma Index: 1 CCM interval: 10000 ms VLAN ID: 100 Priority: 5 MEP Direction MAC PORT ==== ========= ========= ==== 3 DOWN 748e.f81e.03c2 ethe 1/2 MIP VLAN/VC Port Level MAC ==== ======== ===== ===== ========== 100 1/1 4 748e.f81e.03c1 ETX Outputs ETX-204-1>config>oam>cfm>md(1)>ma(1)>mep(1)# show status Port : Ethernet 1 VLAN : 100 Priority : 5 MD Name : MD1 MA Name : MA1 Cross Connect Status : OK Remote MEP Remote MEP Address Operational Status ----------------------------------------------------------------------------- 2 00-20-D2-50-04-12 Fail 3 74-8E-F8-1E-03-C2 OK ETX1 sends LBM (Loopback Message) to remote CES ETX-204-1>config>oam>cfm>md(1)>ma(1)>mep(1)# lbm remote-mep 3 repeat 10 ETX-204-1>config>oam>cfm>md(1)>ma(1)>mep(1)# show lbm-results Remote MEP ID : 3 Destination Address : 74-8E-F8-1E-03-C2 Messages Sent : 10 Replies In Order : 10 Replies Out Of Order : 0 Messages Lost/Timed Out : 0 Messages Lost/Timed Out % : 0 ETX-204-1>config>oam>cfm>md(1)>ma(1)>mep(1)# show lbm-results Remote MEP ID : 3 Destination Address : 74-8E-F8-1E-03-C2 Messages Sent : 10 Replies In Order : 10 Replies Out Of Order : 0 Messages Lost/Timed Out : 0 Messages Lost/Timed Out % : 0



ETX1 sends LBM (Loopback Message) to remote CES ETX-204-1>config>oam>cfm>md(1)>ma(1)>mep(1)# lbm remote-mep 3 repeat 5 ETX-204-1>config>oam>cfm>md(1)>ma(1)>mep(1)# show lbm-results Remote MEP ID : 3 Destination Address : 74-8E-F8-1E-03-C2 Messages Sent : 5 Replies In Order : 5 Replies Out Of Order : 0 Messages Lost/Timed Out : 0 Messages Lost/Timed Out % : 0 ETX1 sends link trace message to remote CES ETX-204-1>config>oam>cfm>md(1)>ma(1)>mep(1)# show linktrace-results LTR ----------------------------------------------------------------------------- Hop : 1 Relay Action : Hit Ingress Action : Ingress OK Egress Action : No TLV Ingress Port Sub Type : Interface Name Ingress Port ID : 1/2 Ingress MAC Address : 74-8E-F8-1E-03-C2 CES output showing LBM received CER2#show cfm statistics Receive stats: Transmit stats: LBM : 15 LBM : 100 LBR : 100 LBR : 15 LTM : 1 LTM : 0 LTR : 0 LTR : 1 DMM : 0 DMM : 0 DMR : 0 DMR : 0 Othe CFM stats: XCON : 0 MA_SYN : 0 ERR_CCM : 0 MEP_SYN : 0 RMEP_AGE_OUT : 0 PORT_SYN : 0 NEW_RMEP : 0 RMEP_SYN : 0

BROCADE NETWORK ADVISOR Brocade Network Advisor is the industry’s first unified network management solution. Brocade Network Advisor provides time-saving tools that help automate repetitive tasks by using intuitive wizards. As a result, organizations can automatically discover and manage Brocade IP switches and MPLS routers. In addition, they can easily configure and deploy group policies—significantly reducing administration overhead and simplifying management. For this solution, the Brocade Network Advisor discovered and managed third-party devices and performed the following tasks • Role-based administration • Topology management



• Perform CLI commands for third-party devices in telnet session launched from the Brocade Network Advisor GUI • Launch third-party element managers • SNMP monitoring • Trap forwarding • Dynamically react to traps • Report generation Brocade Network Advisor Screen shots This screen shots displays the IP Products, subnets, network topology, minimap and event logs for each of the devices in the network.

This screen shots displays the IP Products, subnets, network topology, minimap and traps for each of the devices in the network.



WHOLESALE ETHERNET BACKHAUL WITH CLOCKING End-to-end testing with RAD ETX connected via MPLS through MLX routers to remote CER/MLX with clocking.

Reference Architecture The solution components are listed below and show in Figure 3:

• 4 x Brocade NetIron MLX (v5.0) • 2 x Brocade NetIron CER (v5.1) • 1 x Brocade NetIron CES (v5.1) • 1 x RAD ETX 204A (v2.2) • 1 x Symmetricom TimeProvider 5000 Grand Master Clock • 1 x Symmetricom TimeProvider 500 Translator • Brocade Network Advisor • I/O Generator • Network Emulator • Agilent Counter



MLX 1

MLX 4

MLX 2

MLX 3

CER CES

ETX 204A-1

I/O generatorCER2

Network Emulator

Agilent CounterSymmetricom

TP 5000Symmetricom

TP 500

MPLS

MPLS

Figure 3: Mobile Backhaul with clocking Test Suite per ITU-T Timing and synchronization G.8261/Y.1361 ITU-T G.8261/Y.1361 defines synchronization aspects in packet networks. It specifies the maximum network limits of jitter and wander that shall not be exceeded. It specifies the minimum equipment tolerance to jitter and wander that shall be provided at the boundary of these packet networks at TDM and synchronization interfaces. Tests cases provide useful guidance on the performance of Ethernet-based circuit emulation techniques. Test cases 1-8 are only relevant for PWE (pseudowire) applications and not 1588. Test cases 9-11 are only for Differential Clock recovery. For this solution only test cases 12-14 were performed. Clocking Test Performed Test Case 12: Models the "Static" Packet load. This test models network disturbance load with 80% for the forward direction (Server to Client) and 20% in the reverse direction (Client to Server) for 1 hour. The test measurements should start after the clock recovery is in a stable condition. Test Case 13: Models sudden large and persistent changes in network load. This test models sudden large and persistent changes in network load. It demonstrates stability on sudden large changes in network conditions, and wanders performance in the presence of low frequency PDV (packet delay variation).



Test Case 14: Models the slow change in network load over an extremely long timescale. This test models the slow change in network load over an extremely long timescale. It demonstrates stability with very slow changes in network conditions and wanders performance in the presence of extremely low frequency PDV (packet delay variation). Reading the Graphs: The G.823T 15PP, G.8261.1.E1 and G.8261.1.DS are the three standard MTIE masks as per the Circuit Emulation Applications governing standard for ITU-T Rec. G.8261, they are plotted on all graphs for the reference. The region above these three standard MTIE masks is the unacceptable region, if the MTIE line crosses or passes above the standard MTIE masks then the results are bad. The region below these standard MTIE masks is the acceptable region and if the MTIE line is plotted within this region then the results are proven to be good. During all of our G.8261 testing with RAD and Symmetricom, the MTIE line was always in the acceptable region below the standard MTIE masks and the results were proven good.

Clocking Test Detailed Results

Baseline Testing with Symmetricom and Brocade

Test Case 12: Models the "Static" Packet load. 1st Graph- MTIE calculation excluding the first 4 hrs( stabilization period)



Test Case 13: Models sudden large, and persistent changes in network load. 1st Graph- MTIE calculation excluding the first 4 hrs( stabilization period)

Test Case 14: Models the slow change in network load over an extremely long timescale. 1st Graph- MTIE calculation excluding the first 4 hrs( stabilization period)



Symmetricom TimeMonitor Measure Configuration Set up the individual measurement on the Agilent counter (used to measure MTIE)

Setup Channel1 and Channel 2 on the Agilent Counter



Spirent Network Emulator Configuration Enable Profile 1 on Blade 1 and Blade 2 of the emulator. Once the data traffic is generated from a Spirent Tester center, this traffic load will be noticed on the upper right hand corner of the GUI interface. In this testing traffic load was 90% with frame size 1500 bytes.

Click on Network Playback to play the pre defined data file, this data file contains all the parameters like network delay, jitter, etc. which a customer will set based on their requirements. Once the data file has been added, upload the same data file and then click on the Play button to start the playback. Note: For this testing, Symmetricom provided us with standard profiles for TC 13 and TC 14 which they use to perform testing in their labs.





WHOLESALE 2G/3G/4G Backhaul This is the continuation of Mobile Backhaul testing. This phase 2 Testing is of Wholesale 2G/3G/4G Backhaul with pseudowire.

This solutions tests G.8032 10GbE Ethernet Ring. G.8032 is a mechanism to protect Ethernet rings from link and node failures.

G.8032 has two versions, Version 1 and Version 2. Brocade supports both Version 1 and Version 2 G.8032. RAD supports Version 1 G.8032. The pseudowire circuit emulation tests were performed with Brocade Version 2 G.8032, while the G.8032 convergence tests with two single rings RAD and Brocade were performed using Version 1 G.8032.

Reference Architecture

Figure 4: IPmux to Gmux across G8032 version 2 Ring

Error Free Data Transfer Tests Performed

1. Test BERT/ES/Pattern Loss without any network impairments. The test can be repeated with different values of Jitter buffer and TDM bytes in frame.

2. Clocking Configurations: a. T1 Tester’s – Loopback b. IPmux – 24 Central –Adaptive clock c. GMux– 24 Remote – Internal clock



Error Free Data Transfer Detailed Results

• T1 tester – Loopback • T1 patterns – 2047/QRSS/3 in 24 • IPmux – Adaptive clock • GMux – Internal Clock

The result shows that TDM traffic traversed through the G.8032 network, hits the OC3 loopback and returns back to the IPmux error free. The same test was done using three different patterns as mentioned above, all results were error free. Inband Facility Loopback Test Performed

1. Test internal IPmux loop-back mechanism ability to guarantee reliable TDMoIP transmission under bursts of ETH user traffic.

2. Overload the IPMux-24 ETH user port using a Network Generator. Verify TDMoIP performance under these conditions is not affected. Tests.

Inband Facililty Loopback Detailed Results Below is the configuration used for the above test:

• Spirent TestCenter – Packet size 1500 bytes, Port load 100% • T1 tester – Loopback • T1 patterns – 2047/QRSS/3 in 24 • IPmux – Adaptive clock • GMux – Internal Clock

The result shows that TDM traffic trasversed through the G.8032 network, hits the OC3 loopback and returns back to the IPmux error free. The same test was done using three different patterns as mentioned above, all results were error free. The transmit rate on both the ports of Spirent tester is 1G, the Ethernet traffic is set to priority 0 and TDM traffic is set to priority 7. The traffic is QOS’d with TDM traffic set to priority 7 and then the receive is 4Mbps less then transmit. The 4Mbps is TDM traffic with overhead.



G.8032 and QoS Tests Performed

1. Verify that G.8032 converges to a new path during a link failure 2. Test internal IPmux QoS mechanism ability to guarantee reliable TDMoIP transmission under bursts of ETH

user traffic. 3. Overload the IPMux-24 ETH user port using a Network Generator. Verify TDMoIP performance under these

conditions is not affected. Tests 1to 3 may be repeated under these conditions. 4. Test network QoS mechanisms ability to guarantee reliable TDMoIP transmission under bursts of ETH user

traffic. G.8032 and QoS Detailed Results *During the tests below, there was no change in the T1 pattern during the path convergence and the packet loss was very minimal in both the below scenarios. For the above tests, the configuration is below: RAD IPMux’s: G.8032 Version 1, G.8032 name ERP 1, RPL owner for the ring MLX 2 Brocade MLX’s: G.8032 Version 1, G.8032 name ERP 2, RPL owner for the ring MLX 2

Reference Architecture

Figure 5: G8032 version 2 Rings

ERP 1 link failure results

RAD IPmux 1 – MLX 2 (Owner) – RAD IPmux 2

ERP state before link failure:



ERP state after link failure:

The port 3/4 is the RPL-node, after a link failure this port is now changed to forwarding and port 3/3 is blocking.

ERP 2 link failure results

Brocade G.8032

ERP state before link failure:



ERP state after link failure:

Port 2/2 is the RPL-node, after a link failure this port is now changed to forwarding and port 2/1 is blocking

QOS The transmit rate on both the ports of Spirent tester is 1G, the Ethernet traffic is set to priority 0 and TDM traffic is set to priority 7. The traffic is QOS’d with TDM traffic set to priority 7 and then the receive is 4Mbps less then transmit. The 4Mbps is TDM traffic with overhead.



The TDM traffic did not give any errors during convergence.



APPENDIX A: MOBILE BACKHAUL CONFIGURATIONS Brocade NetIron MLX Series Configuration Each of the NetIron MLXs were configured as part of the Carrier Ethernet MPLS (Multiprotocol Label Switching) core. An example of MLX1 is listed below. MLX1 # The MLX routers were configured with OSPF routing. They served as the Backbone area and Area Border Router. router ospf area 11 area 0 auto-cost reference-bandwidth 1000 redistribute connected interface loopback 1 ip address 10.2.2.2/32 interface ethernet 3/4 enable ip ospf area 0 ip address 10.10.10.1/30 interface ethernet 3/5 enable ip ospf area 0 ip address 10.10.10.5/30 interface ethernet 3/6 enable ip ospf area 0 ip address 10.10.10.9/30 interface ethernet 3/7 enable ip ospf area 11 ip address 10.10.10.29/30 # The MLX routers were configured with MPLS on the each of the physical interconnected interfaces. LDP (Label Distribution Protocol) was enabled on each of the interfaces. LDP is used to establish MPLS service LSP (Label Switch Paths) router mpls mpls-interface e3/4 ldp-enable mpls-interface e3/5 ldp-enable mpls-interface e3/6 ldp-enable mpls-interface e3/7 ldp-enable



Brocade NetIron CER/CES Series Configuration The NetIron CER/CES routers were configured as the PE (Provider Edge) with MPLS and VLL (Virtual Leased Line) tunnels.

CER no spanning-tree vlan 1 name DEFAULT-VLAN no untagged ethe 1/1 vlan 5 vlan 100 route-only # The CER router was configured with OSPF routing. router ospf area 11 redistribute connected interface loopback 1 ip address 10.1.1.1/32 # Link-OAM was enabled globally link-oam enable interface management 1 ip address 192.168.10.5/24 enable interface ethernet 1/3 enable ip ospf area 11 ip address 10.10.10.30/30 interface ethernet 1/4 enable ip ospf area 11 ip address 10.10.10.26/30

# The CER router was configured with MPLS on the each of the physical interfaces connected to the MLX core. LDP (Label Distribution Protocol) was enabled on each of the interfaces. LDP is used to establish MPLS service LSP (Label Switch Paths) router mpls mpls-interface e1/3 ldp-enable mpls-interface e1/4 ldp-enable # LSP (Label Switch Path) tunnel is created to communicate with the remote CES peer lsp tunnelPE1 to 10.6.6.6 enable



# VLL (Virtual Leased Line) created for data VLAN and management VLAN to communicate with the remote CES peer vll PE1 50 vll-peer 10.6.6.6 vlan 100 tagged e 1/1 vll PE11 100 vll-peer 10.6.6.6 vlan 5 tagged e 1/1

CES no spanning-tree vlan 1 name DEFAULT-VLAN no untagged ethe 1/3 ethe 1/5 vlan 5 vlan 100 tagged ethe 1/5 to 1/6 route-only router ospf area 12 redistribute connected interface loopback 1 ip address 10.6.6.6/32 link-oam enable ethernet 1/3 active interface management 1 ip address 192.168.10.5/24 enable interface ethernet 1/1 enable ip ospf area 12 ip address 10.10.10.33/30 interface ethernet 1/2 enable ip ospf area 12 ip address 10.10.10.37/30 interface ethernet 1/3 enable



router mpls mpls-interface e1/1 ldp-enable mpls-interface e1/2 ldp-enable lsp tunnelPE2 to 10.1.1.1 enable vll PE2 50 vll-peer 10.1.1.1 vlan 100 tagged e 1/3 vll PE22 100 vll-peer 10.1.1.1 vlan 5 tagged e 1/3

RAD ETX 204 Configuration EXT Flow config: # define a classifier profile and provide a name applied to a flow classifier-profile "service100" match-any match all exit # define a classifier profile and provide a name applied to a flow that forward frames from VLAN 100 classifier-profile "service100_egress" match-any match vlan 100 exit # define a classifier profile and provide a name applied to a flow to remove VLAN ID. Also define the ingress and egress ports of the flow flow "service1_egress" classifier "service100_egress" vlan-tag pop vlan ingress-port ethernet 1 egress-port ethernet 4 queue 1 block 0/1 no shutdown exit # define a classifier profile and provide a name applied to a flow to push VLAN 100 with p-bit 0 set and define the ingress and egress ports of the flow flow "service100" classifier "service100" vlan-tag push vlan 100 p-bit fixed 0 ingress-port ethernet 4 egress-port ethernet 1 queue 1 block 0/1 no shutdown exit



APPENDIX B: MOBILE BACKHAUL CONFIGURATIONS WITH CLOCKING Brocade Configuration to Provide QOS for Clocking Configure QOS on Customer edge router and Provider edge router to provide high precedence to clock signal over data traffic. Ideally QOS is configured at the Demarcation Device, for a Customer CE is the demarcation point and for a Service Provider PE is the demarcation point. Customer Edge (CE) Router QoS Below is the QOS configuration at the Customer Demarcation device CER2 CER2(config)#sh run

ver V5.1.0T183

no spanning-tree

vlan 1 name DEFAULT-VLAN

#Configure Vlan 5 with untagged port 1/10 for data traffic, assign Vlan 5 a priority value of 0 vlan 5

untagged ethe 1/10

tagged ethe 1/2

priority 0

#Configure Vlan 27 with untagged port 1/1 for clock signal, assign Vlan 27 a priority value of 7. Vlan 27 with priority value 7 will take high precedence over data traffic vlan 27

untagged ethe 1/1 ethe 1/24

tagged ethe 1/2

priority 7

router-interface ve 5

Provider Edge (PE) Router QOS for VLL Traffic Below is the QOS configuration at the Service Provider’s Demarcation device CER and CES #Configure VLL tunnel (named as clock_signal here) with Vlan 27 for clock signal, assign COS value of 7 to this VLL. With COS value as 7, anything going through VLL clock_signal will take a higher precedence over any other VLL tunnels vll clock_signal 100 cos 7

vll-peer 10.6.6.6

vlan 27

tagged e 1/1

#Configure VLL tunnel (data_traffic here) with Vlan 5 for data traffic, assign COS value of 0 to this VLL vll data_traffic 102 cos 0

vll-peer 10.6.6.6

vlan 5

tagged e 1/1



APPENDIX C: MLX G.8032 AND RAD IPMUX CONFIGURATIONS Brocade MLX (RPL-Owner) configuration: # It is mandatory to configure CFM along with standard G.8032 for convergence. MLX2#sh run Current configuration: ! ver V5.1.0bT163 module 2 ni-mlx-4-port-10g module 3 ni-mlx-20-port-1g-copper no spanning-tree

vlan 1 name DEFAULT-VLAN

no untagged ethe 2/1 to 2/2 ethe 3/3 to 3/4

vlan 2

tagged ethe 2/1 to 2/2 ethe 3/1 ethe 3/3 to 3/4

vlan 10

tagged ethe 2/1 to 2/2 ethe 3/1 ethe 3/3 to 3/4

# ERP 1 is the G.8032 Version 1 with RAD IPmux – Brocade MLX (RPL-Owner) – RAD IPmux

erp 1

left-interface vlan 10 ethe 3/4

right-interface vlan 10 ethe 3/3

rpl-owner

version 1

raps-default-mac

fast-wtr-time

rpl vlan 10 ethe 3/4

enable

# ERP 2 is the G.8032 Version 1 with 4 Brocade MLX’s ring

erp 2

left-interface vlan 10 ethe 2/1

right-interface vlan 10 ethe 2/2

rpl-owner

raps-default-mac

fast-wtr-time

rpl vlan 10 ethe 2/2



dot1ag-compliance domain-name d1 mep 1 ma-name 1

enable

# It is mandatory to configure CFM for G.8032 convergence

cfm-enable

domain-name d1 id 1 level 1

ma-name 1 id 1 vlan-id 10 priority 1

mep 2 down port ethe 2/1

no route-only

hw-aging dis

telnet server

ip route 10.0.0.0/8 10.17.80.1

interface management 1

ip address 10.17.95.124/20

enable

topology-group 1

master-vlan 10

member-vlan 2

RAD IPmux Configuration: The ERP ring number is 1 and the p-bit priority value is set to 7 as shown in below screenshots.





APPENDIX D: SUPPORTED FEATURES AND PROTOCOLS

Features Description Brocade DS-1 Private Line Service DS-1 Service operates at 1.544 Mbps. DS-1

service has the equivalent capacity of 24 Voice Grade Services or 24 DS0 Channels.

Availability of all Service > or = 99.999% measured annually X Error Free Seconds > or = 99.99% measured over any twenty-

four-hour (24) period.

X

Bit Erro Rate (BER) <1X10 -9 X Interface Requirements Interface specifications for DS-3's and STS-1’s

is BNC cables, for DS-1’s is USOC RJ-48X connectors, and for OC-type interconnect is SC connectors.

Ethernet Service Ethernet is flexible and scalable (10Mbps to GigE) transport system that utilizes a variety of established transport protocols.

X

Demarcation At Service Provider: GigE/10GigE fiber into each two L3 devices. At Cell site, most probable data rate: 2G/3G Cell: 10, 20, 30 Mbps

X

Site Scaling Abilility to support from 1 to multiple wireless switches at Service Provider location. Ability to support 10 to 500+ cell sites for each wireless switch.

X

Bandwidth Scaling Abilility to scale bandwidth from a single pair of GigE links to 10GigE link pairs or more at Service Provider location. Abilility to scale bandwidth from 10Mbps to 300Mbps+ per cell site.

X

Primary Power Support -48VDC power input. X



Features Description Brocade NEBs NEBS level 3 Certified

X

CIR - Committed Information Rate

At Service Provider: Line rate GigE with option to implement 10GigE.At Cell site: Near-term rate of 10, 20, 30, 50, 100Mbps X

EIR - Excess Information Rate

Bandwidth above the CIR but available only if capacity on the Transport provider network is available.

X

Latency - NID to NID one way latency

Maximum 5ms X

Jitter - variation of packet arrival

"+/-" 1 ms (Total variation of 2ms) X

BER - Bit Error Rate Better than 1E10-9 (one errored bit in 10E9 bits) X

FER - Frame Rate or Frame Loss

Better than 1E10-6 (one errored frame in one million) X

QoS - Quality of Service Prioritize traffic based on L2 802.1p markings. Voice and video traffic to receive appropriate priority. X

Availability - The objective is zero down time

Five 9's - 99.999 X

Redundancy - If the primary connectivity fails, the secondary becomes active

At Service Provider: Dual homing to two Central Office or L1 Ring design. At Cell Site: If a tail circuit into the cell site is a long run, consider a L1 ring.

X

Fail-Over – Fail-over Time Worse case fail-over times from interruption of traffic to restoral of traffic. L1: 50ms L2: 1 second L3: 1 second

X



Features Description Brocade TTR - Time to Repair Dependant on case but can be less than 4

hours X

Reporting Real - time full circuit performance monitoring. Off-line performance reporting. X

Alerting Real - time alerting of out of specification parameters or of circuit degradation X

Tracking Trouble ticket tracking system X

Non Intrusive Loopback Ability to troubleshoot while the circuit is in use. Selectively loopback cell site data sub-streams to allow non intrusive, real-time testing.

Circuit Modifications Real - time ability to modify and upgrade circuit parameters.

Layer Standard Protocol Description Brocade

L2 802.1 D STP Spanning Tree Protocol X

L2 802.1 p CoS Class of Service Prioritization X

L2 802.1 Q .1q Q in Q VLAN Encapsulation 802.1q in 802.1q tagging

X

L2 802.1 s mSTP Merged into 802.1Q Multiple instances of STP X

L2 802.1 v VLAN Class Merged into 802.1Q VLAN classification by Protocol or port

X

L2 802.1 w RSTP Merged into 802.1D Rapid Spanning Tree Protocol X

L2 802.1 x Auth Port based network access ctl X

L2 802.1 ae MAC Sec MAC Security X




L2 802.1 ag Fit Mgmt Connectivity Fault Mgmt X

L2 802.1 u FE Fast Ethernet, 100BaseTX (copper).

X

L2 802.1 u FE

Fast Ethernet, 100Base FX (MM fiber) 1000BaseSX (MM) 1000BaseTX (copper)

X

L2 802.3 u+ GigE Note that GigE requirements are listed under 802.3z X

L2 802.3 x MAC Pause Flow Control X

L2 802.3 z GigE 1000BaseSX (MM) X

L2 802.3 ab GigE 1000BaseTX (copper) X

L2 802.3 ac VLAN Tag Max frame size extended from 1518 to 1522 Bytes to allow for VLAN tags X

L2 802.3 ad LACP Link Aggregation Ctl Protocol X

L2 802.3 ae 10GigE 10 Gbps over SM fiber X




L2 802.3 af PoE Power over Ethernet X

L2 802.3 ah EFM Ethernet in the first mile (PROVIDED BY RAD)

L2 802.3 aq 10G MM 10Gbps over MM fiber X

RFC 2544 Testing Details on Testing of Ethernet service X

Y1731 OAM Details on end-to-end OAM X

L2 Auto

Negotiation Auto negotiation, but the ability to force speed and duplex settings

X

L2 Shaping Traffic Shaping X

L2 Hardware

Redundancy Hardware Redundancy X

L2 Failover Max 50ms device failover X

L2 VLANs Support for 4096 VLANs X

L2 Security MAC Filtering X

L2

Baby Giant Frames

Ethernet frames less than 1518 up to 1600 Bytes

X

L2 Jumbo Frames Ethernet frames up to 9216B X

L2 L2 TR Layer 2 Traceroute X L2 L2F Layer 2 Forwarding Protocol Tunneling of

PPP over IP, virtual extension of dial-up link X

L2

L2TP Layer 2 Tunneling Protocol Encapsulating one Ethernet packet in another (1500+18+50=1568 Bytes)

X

L2 PPTP Point to point Tunneling Protocol X

L3 ACL Access Control List X

L3 DHCP DHCP Auto configuration X

L3 ICMP Internet Control Message Protocol X




L3 IGMP Internet Group Multicast Protocol X

L3 IP Routing Support for IP routing protocols X

L3 IPV6 IP Version 6 support X

L3 Mgmt-IB IP Manageability – In-Band X

L3 Mgmt-OOB IP Manageability – Out of Band X

L3 NTP Ntwk Time Protocol client X

L3 RMON Remote Monitoring X

L3

Security Support for TACACS and Radius Authentication X

L3 SNMP Device mgmt via SNMP traps X

L3 SSHv2 Secure Shell access to device X

L3

TFTP Software upgrade via TFTP or similar protocol X

L3 BFD Bi-Directional Forwarding Detection X

© 2011 Brocade Communications Systems, Inc. All Rights Reserved. 01/11

Brocade, the B-wing symbol, BigIron, DCFM, DCX, Fabric OS, FastIron, IronView, NetIron, SAN Health, ServerIron, TurboIron, and Wingspan are registered trademarks, and Brocade Assurance, Brocade NET Health, Brocade One, Extraordinary Networks, MyBrocade, VCS, and VDX are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned are or may be trademarks or service marks of their respective owners.

Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government.

Documents

RAD brocade-mobile-backhaul-solutions-dg.pdf