Interoperability Testing In Heterogeneous Networks … · Interoperability Testing In Heterogeneous...
21
Interoperability Testing In Heterogeneous Networks Carsten Rossenhoevel, Managing Director European Advanced Networking Test Center
Transcript of Interoperability Testing In Heterogeneous Networks … · Interoperability Testing In Heterogeneous...
Interoperability Testing In Heterogeneous Networks
Carsten Rossenhoevel, Managing Director European Advanced Networking Test Center
About the European Advanced Networking Test Center
Business Areas
Test and certification of network components for manufacturers
Network design consultancy and proof of concept testing for service providers
Request for Proposal (RfP) support, acceptance testing and network audits for large enterprises and government organizations
Vendor neutral technology seminars
Vendor independent network quality assurance since 1991
Unique technical expertise of network design and testing in latest technology areas
20-year testing experience matches highest quality standards
Setting the Scene for Interoperability Testing …
Multiple (potentially many) device types
• Different feature sets and commands
Multiple manufacturers
• Different configuration and management interfaces
Multiple layers of test scenarios
• Different protocols and interdependencies
Growing Complexity
EANTC Multi-Vendor Interoperability Test Events
EANTC periodically invites vendors to join our test events
Two weeks of in-depth testing
Four months of test plan/configuration guide preparation
40+ engineers from participating vendors and EANTC
15-20 Test scenarios in 3-5 groups
Participating Vendors 2012 Sp
rin
g A
utu
mn
iPASOLINK 400
Symmetricom
SSU 2000e
PackeTime PTP
LINK 400 IDU
SpirentParagon-X
IxiaIxNetwork
Omnitron GM4
SpirentTestCenter
SIAE
ALCplus2e
SIAE
ALFOplus80
IxiaIxNetwork
Ericsson MINI-LINK
Omnitron GM4
Ericsson
MINI-LINK SP310
12:50:00
SymmetricomTimeProvider 5000
Ericsson MINI-LINK TN
SpirentParagon-X
NEC
IxiaIxNetwork
Omnitron
GM4
AlbisACCEED 2202
12:50:00
SymmetricomTimeProvider 5000
AlbisACCEED 1416
PT2010
Aviat Eclipse
Packet Node
EricssonSPO1410
EricssonSPO1410
IxiaImpairNet
HFRCET-10216
IxiaAnue 3500
IxiaIxNetwork
IxiaImpairNet
SpirentTestCenter
iPASOLINK 400NEC
NEC iPASO-
Aviat EclipsePacket Node
Omnitron GM4
HFRCET-10448
Ericsson
SPO1460
OmnitronGM4
EricssonMINI-LINK SP210
EricssonMINI-LINK SP310
NEC iPASOLINK
400 IDU
AlbisACCEED 1416
SpirentParagon-X
AlbisACCEED 1104
IxiaIxNetwork
CEWC2012 – Interop Network Physical Topology
Analyzer/Traffic Generator
Device Types
Access device
Reference Clock
Impairment tool
Microwave radiosystem
Aggregation device
Emulator
12:50:00 IEEE 1588v2 Grandmaster
Network Areas
Connection Types
Ethernet Aggregation network
MPLS-TP network
Clock link
Gigabit Ethernet link
Access network
ERPS Rings
Bonded SHDSL link
MPLS & Ethernet World Congress 2012 Physical Topology
Interoperability Test Areas
• Fault Mgmt, Perf. Monitoring
• Service Activation
• E-Access/Wholesale Interconnect
• Ring Protection
Carrier Ethernet
2.0
• Clock Sync (IEEE 1588, SyncE)
• Multi-CoS
• Packet Microwave
Mobile Backhaul
• MPLS-TP Protection
• VPLS Termination/Interworking MPLS
• Migration Scenarios
• VPN Support
• Residential Services IPv6
Carrier Ethernet Technology Status 2011
Visibility
Y.1564 Service
Activation
IEEE 1588:2008
Performance Monitoring Y.1731
Technology Progress
Technology Trigger
Peak of Expectations
Trough of Disillusionment
Slope of Enlightenment
Plateau of Productivity
© European Advanced Networking Test Center – eantc.com Oct 2011 Hype Cycle model (five stages) © Gartner 1995
Ethernet Microwave
MPLS-TP
ERPS
SyncE
Carrier Ethernet Technology Status 2012
Visibility
Y.1564 Service
Activation
IEEE 1588 Slave Clocks
Performance Monitoring Y.1731
Technology Progress
Technology Trigger
Peak of Expectations
Trough of Disillusionment
Slope of Enlightenment
Plateau of Productivity
© European Advanced Networking Test Center – eantc.com Sep 2012 Hype Cycle model (five stages) © Gartner 1995
Ethernet Microwave
MPLS-TP Multi-Vendor
ERPS
SyncE
IEEE 1588 Boundary Clocks
Multi-Vendor
MPLS-TP Single-Vendor
New: Tests done (terminated) by access devices
Differing views on how to implement the ITU Y.1564 standard
Excess information rate testing remains a challenge for now
Carrier Ethernet 2.0: Y.1564 Service Activation
Automation Readiness
Equipment Configuration QoS
config varies widely
Test Device Configuration
Single-ended; Protocol defined with
automated execution in mind
Complexity Variety of test cases
built into standard
Root Cause Analysis Very time-
consuming, standard does not
support segmenting
Carrier Ethernet 2.0: Hierarchical Service OAM
3 Different domains
Alarm Indication (ETH-AIS)
Lock Message (ETH-LCK)
Test Message (ETH-Test)
Automation Readiness
Equipment Configuration Multi-
layer config very complex; quite
Complex CLI commands
Test Device Configuration
Again, multi-layer config non-trivial
Complexity Automation improves
control, reduces human errors
Root Cause Analysis Extremely
time-consuming for latency & partial
loss issues
Clock Synchronization – Transparent Clock
Automation Readiness
Equipment Configuration One-off
configuration enables multiple test
combinations
Test Device Configuration
Alignment of multiple test devices is
primary task; impairment generation
on multiple lines potentially much
more expensive than manual rewiring
Complexity Straightforward test
Root Cause Analysis Very time-
consuming for latency variation
issues
Tested four vendor pairs
All combinations passed G.823SEC mask
Packet population using 1-3% Floor Packet Percentage (FPP) limit as defined in G.8261.1
Compared correction fields at transparent clock
Synchronous Ethernet over Link Aggr. Results
Symmetricom SSU 2000 Reference clock
Extreme E4G-400 Master
Ericsson Mini-Link SP310 Slave
Requires versatile data collection API from test equipment
Carrier Ethernet Transport – Ethernet Ring Protection (ERPS)
Two different rings to accommodate different CFM rates supported by vendors
ERPS in access, MPLS-TP in core
Automation Readiness
Equipment Configuration Physical
and logical reconfiguration required for
different test cases
Test Device Configuration
Major test area of protection requires
single family of configurations
Complexity Straightforward tests,
mostly layer 1 switch config challenge
Root Cause Analysis Performance
analysis achieved through combinatory
analysis of test runs
Introduction of Layer 1 Crossconnect
Great idea!
Test Device 1 Test Device 2 Test Device 3
Physical Layer Crossconnect
DUT1
DUT2
DUT3
Test Interfaces
Network Interfaces
Introduction of Layer 1 Crossconnect (cont‘d)
Introduction of impairment?
Test Device 1 Test Device 2 Test Device 3
Physical Layer Crossconnect
DUT1
DUT2
DUT3
Test and Network
Interfaces
Imp
airm
ent
Gen
erat
or
Introduction of Layer 1 Crossconnect (cont‘d)
Scale for number of ports?
Crossconnects are not easily stackable
Test Device 1 Test Device 2 Test Device 3
Crossconnect 1
DUT2
Imp
airm
ent
Gen
erat
or
DUT1 DUT50 …
Crossconnect 2 Crossconnect 3
Time Spent for Manual Interoperability Test Execution
6 weeks Test Plan Development
2 weeks Configuration Planning
2 days Racking and Installation
8 days Test Execution
2 weeks Documentation
Conclusion
Exact planning required to reap automation benefits for interoperability testing
Automation better suited for continued regression testing than for campaign-based testing of new protocols and solutions
Introduction of interoperable APIs for advanced test equipment configuration needed for sustainable lab execution model
Interoperable APIs for device under test configuration are a dream
Further Information
16-page public white papers available free of charge
http://www.eantc.de/cewc2012
http://www.eantc.de/mplsewc2012
EANTC AG
Salzufer 14, 10587 Berlin, Germany
http://www.eantc.de
[email protected], office +49 30 3180595 21
