You are on page 1of 61

FibeAir® IP-10

Nodal solution and XC/SNCP support overview
June 2009
1
Proprietary and Confidential

FibeAir IP-10 – Integrated Nodal Solution
 Same 1RU IP-10 unit can be used for terminal and nodal solution

 The nodal enclosure is also modular
 Best economical future upgrade  Best flexibility for network designer  Easier to Install / Maintain / expand

 The solution is modular and forms a single unified nodal device
    Common Ethernet Switch Common E1s Cross Connect Single IP address Single element to manage

2

Proprietary and Confidential

FibeAir IP-10 – Integrated Nodal Solution
• • • •
Up to 6 units can be stacked to form single nodal device
Additional units can be added in the field as required Multiple nodes can be cascades to support large aggregation sites

Stacking is done using 2RU “Nodal enclosures”

• Each enclosure has 2 slots for hot-swappable 1RU units • Additional “Nodal enclosures” and units can be added in the field as required
without affecting traffic

Front

Nodal enclosure
3

Rear
Proprietary and Confidential

Integrated nodal solution – Nodal enclosures “Extension” nodal enclosure “Main” nodal enclosure 4 Proprietary and Confidential .

FibeAir IP-10 – Scalable nodal enclosure 5 Proprietary and Confidential .

can be stacked to provide an expandable system 6 Proprietary and Confidential . consisting of six IDUs. which provide the interconnectivity.XC using a Shelf Configuration XC operation is implemented using two-unit backplanes. Up to three backplanes.

The 2 lower units can be configured as Main units. and act as stand-alone units.XC using a Shelf Configuration All IDUs that operate within the XC system have identical hardware. The role an IDU plays is determined during installation by its position in the traffic interconnection topology 7 Proprietary and Confidential .

FibeAir IP-10 – Scalable nodal enclosure Additional STM1/OC3 Mux T-Card Additional 16xE1 T-Card Expand & invest only when needed 8 Proprietary and Confidential .

Integrated nodal solution – “main” units • Units located in the bottom “Nodal enclosure” are acting as the main units • The main unit performs the cross-connect. switching and management functions for all the units in the node • Mandatory “active” main unit can be located in any of the 2 slots • Optional “standby” main unit can be installed in other slot • Switchover time <50msecs for all traffic affecting functions Integrated Ethernet Switching Integrated TDM cross-connect M E Main unit M M Native2 Expansion unit 1+1 HSB 9 Proprietary and Confidential .

TDM and Ethernet) are connected to the • main units Expansion unit is fully managed through the main units • Radios in each pair of main/expansion units can be configured as either: • Dual independent 1+0 links • Single 1+1 HSB link • Single 2+0/XPIC link Native2 1+0 Native2 E Integrated Ethernet Switching Integrated TDM cross-connect 1+0 E E Native2 E M 2+0/XPIC M E Main unit Expansion unit M Native2 1+1 HSB 10 Proprietary and Confidential .Integrated nodal solution – “expansion” units • Units located in non-bottom “Nodal enclosures” are acting as “expansion” units • All interfaces of the expansion units (radio.

Trail Configuration Guidelines 11 Proprietary and Confidential .

All Trails are transported through main unit(s) 3. XC Trails can be configured only via Main unit 2. Radio VCs must be identical on both sides of the radio link 12 12 Proprietary and Confidential . T-Cards (TDM / SDH) are not hot-swappable. When Protection is enabled. configure trails to go via the Active unit (XC Trails are automatically created on the STBY unit) 4.XC Trails Guidelines (1) 1. do not extract / insert card when IDU is powered up 5.

Maximum number of Trails per Radio = 84 13 13 Proprietary and Confidential . therefore an alarm will display next to the relevant T-Card accommodating the activated port(s) 7. Creating a TDM trail automatically activates the corresponding TDM port.XC Trails Guidelines (2) 5. XC Trails can be configured between: • • • Radio to Line Line to Radio Radio to Radio 8. Maximum number of Trails (SNCP – Protected Ring) = 180 (per Shelf) 9.

XC Trails Guidelines (3) Identify Trail interfaces prior to configuration Note that Trail configuration is Bi-Directional ! Trail starts here: For SNCP we shall need to define 3 interfaces Trail traverses through here: We shall need to define 2 interfaces IP-10 IP-10 Bypass site Protected Trail (Automatic) IP-10 Radio Link 14 14 Proprietary and Confidential Trail starts here: For SNCP we shall need to define 3 interfaces .

XC Trails Guidelines (4) Pay attention to the order of configuration: 2 The Trail Start/End points should be configured first (interface #1) 1 IP-10 3 Bypass site IP-10 Interfaces #2 and #3 can be configured in a random order Protected Trail (Automatic) 2 IP-10 1 3 15 15 Proprietary and Confidential .

Standalone non-protected Trail Configuration 16 Proprietary and Confidential .

Step #1: Access Trail Page Click on the Add button 17 17 Proprietary and Confidential .

In this example we selected the SDH connector. 18 18 Proprietary and Confidential .Step #2: Configure 1st Interface Click on the 1st interface connector In this example we selected the PDH connector. Your next step is selecting the PDH port number. Your next step would be selecting the VC number.

Step #3: Configure 2nd Interface Click on the 2nd interface connector In this example we selected the Radio as the next interface connector. Alternatively you could choose other combinations as well: • PDH to PDH • PDH to Radio (above) • PDH to SDH • SDH to Radio • SDH to Radio • Radio to SDH • Radio to PDH 19 19 Proprietary and Confidential . Your next step would be selecting the radio channel number.

Step #4: Configure Trail Attributes Make sure Trail ID is unique and identical on all sites/trails 20 20 Proprietary and Confidential .

Step #5: Trail Verification If your settings are correct. trail path is ready to be tested 21 21 Proprietary and Confidential . trail alarms should disappear.

SNCP Trail Configuration in a Node 22 Proprietary and Confidential .

Selecting Main IDU for Trail Configuration • In the following example we assume every node has 2 IDUs installed in a Main Enclosure • Make sure your Main unit is selected on every Node-EMS • Enable Protection when you configure the Trails (excluding Bypass Nodes) • Trail ID should unique and identical on all nodes 23 23 Proprietary and Confidential .

SNCP Trail in Nodal Architecture PDH interface Bypass Node IP-10 IP-10 IP-10 SDH interface 24 24 Proprietary and Confidential .

1st Node PDH interface IP-10 IP-10 Bypass site Radio CH #1 Radio CH #26 IP-10 SDH interface #1 25 25 Proprietary and Confidential .

Bypass Node PDH interface Radio CH #48 IP-10 Bypass Node IP-10 Radio CH #1 IP-10 SDH interface 26 26 Proprietary and Confidential .

3rd Node Radio CH #48 PDH interface IP-10 Bypass site IP-10 Radio CH #26 IP-10 SDH interface 27 27 Proprietary and Confidential .

Node full equiped protection 28 28 Proprietary and Confidential .

Nodal configurations 29 Proprietary and Confidential .

1+0 link with 32 E1/T1s Native2 1+0 32 E1/T1s GE/FE 32 E1/T1s GE/FE 30 Proprietary and Confidential .

1+1 HSB configuration  2 IP-10. 2 RFU units required  Integrated Ethernet switching can be enabled for multiple local Ethernet interfaces support  Redundancy covers failure of all control and data path components  Local Ethernet & TDM interfaces protection support via Y-cables or protection-panel  <50mSecs switch-over time 1+1 HSB Native2 Up to 75 E1/T1 + Ethernet Up to 500Mbps Nx GE/FE Up to 32 E1/T1s or 16E1/T1s + STM-1/OC3 Mux 31 Proprietary and Confidential Integrated Ethernet Switching .

1+0 link with 64 E1/T1s Native2 1+0 E M E M 64 E1/T1s GE/FE 64 E1/T1s GE/FE 32 Proprietary and Confidential .

 Can be configured independently for “switch” or “pipe” operation  No Ethernet traffic is shared internally between the 2 radio carriers  TDM traffic  Each of the 2 radio interfaces supports separate E1/T1 services  E1/T1 Services can optionally be protected using SNCP Native2 E M 2+0/XPIC “Multi-Radio” E M 64 E1/T1s 33 GE/FE Proprietary and Confidential 64 E1/T1s GE/FE .with 64 E1/T1s “no Multi-Radio” mode  Ethernet traffic  Each of the 2 units:  Feeding Ethernet traffic independently to its radio interface.2+0/XPIC link .

 The 2nd ("Slave") IDU has all its Ethernet interfaces and functionality effectively disabled.with 64 E1/T1s “Multi-Radio” mode  Ethernet traffic  One of the units is acting as the "master" unit and is feeding Ethernet traffic to both radio carriers  Traffic is distributed between the 2 carries at the radio frame level  The "Master" IDU can be configured for switch or pipe operation.2+0/XPIC link .  TDM traffic  E1/T1 services are duplicated over both radio carriers and are 1+1 HSB protected Native2 2+0/XPIC “no Multi-Radio” E E M M 64 E1/T1s 34 GE/FE Proprietary and Confidential 64 E1/T1s GE/FE .

2+0/XPIC/ link with 32 E1/T1s + STM1/OC3 Mux interface (No Multi-Radio. Up to 150 E1s / 168 T1s over the radio) Native2 2+0/XPIC “no Multi-Radio” E M E M 2 x STM1/OC3 32 E1/T1s (Mux) GE/FE 2 x STM1/OC3 32 E1/T1s (Mux) GE/FE 35 Proprietary and Confidential .

1+1 HSB link with 32 E1/T1s Native2 1+1 HSB 32 E1/T1s (Protected) GE/FE (Protected) 32 E1/T1s (Protected) GE/FE (Protected) 36 Proprietary and Confidential .

1+1 HSB link with 64 E1/T1s Native2 1+1 HSB E E E M M E M M 64 E1/T1s (Protected) GE/FE (Protected) 64 E1/T1s (Protected) GE/FE (Protected) 37 Proprietary and Confidential .

1+1 HSB link with 75 E1s or 84 T1ss Native2 1+1 HSB E E E E E E E M M E M M 75 E1/ 84 T1s (Protected) GE/FE (Protected) 75 E1/ 84 T1s (Protected) GE/FE (Protected) 38 Proprietary and Confidential .

1+1 HSB link with 16 E1/T1s + STM1/OC3 Mux interface (Up to 75E1s / 84T1s over the radio)

Native2

1+1 HSB

STM1/OC3 Mux (Protected)

GE/FE 16 E1/T1s (Protected) (Protected)

STM1/OC3 Mux (Protected)

16 E1/T1s (Protected)

GE/FE (Protected)

39

Proprietary and Confidential

Chain with 1+0 downlink and 1+1 HSB uplink – with STM1/OC3 Mux
Native2

1+0

16 E1/T1s

GE/FE

E M M
Native2

1+1 HSB

16 E1/T1s (Protected)

GE/FE (Protected)

STM1/OC3 Mux (Protected) 40

16 E1/T1s (Protected)

GE/FE (Protected)

Proprietary and Confidential

Node with 2 x 1+0 downlinks and 1 x 1+1 HSB uplink
16 E1/T1s GE/FE
Native2

1+0

E
Native2

E
M M

1+0

16 E1/T1s

GE/FE

16 E1/T1s (Protected)

GE/FE (Protected)

Native2

1+1 HSB

GE/FE (Protected) 32 E1/T1s (Protected)

41

Proprietary and Confidential

Chain with 1+1 downlink and 1+1 HSB uplink – with STM1/OC3 Mux Native2 1+1 HSB E E M M Native2 16 E1/T1s (Protected) GE/FE 1+1 HSB 16 E1/T1s (Protected) GE/FE STM1/OC3 Mux (Protected) 42 16 E1/T1s GE/FE (Protected) Proprietary and Confidential .

Native2 ring with 3 x 1+0 links + STM1/OC3 Mux interface at main site 16 E1/T1s STM1/OC3 Mux (Protected) GE/FE E M Native2 Native2 1+0 1+0 GE/FE E M Wireless Native2 Ring E M 16 E1/T1s GE/FE 16 E1/T1s Native2 1+0 43 Proprietary and Confidential .

Native2 ring with 3 x 1+1 HSB links + STM-1 Mux interface at main site Native2 1+1 HSB E E STM1/OC3 Mux (Protected) 16 E1/T1s (Protected) GE/FE E E M M M M Native2 1+1 HSB Wireless Native2 Ring GE/ FE 16 E1/T1s (Protected) E E M M 16 E1/T1s (Protected) GE/FE Native2 1+1 HSB 44 Proprietary and Confidential .

Node with 1 x 1+1 HSB downlink and 1 x 1+1 HSB uplink – with STM1/OC3 Mux Native2 1+1 HSB E E M M 16 E1/T1s (Protected) GE/FE Native2 1+1 HSB GE/FE 32 E1/T1s (Protected) GE/FE 16E1/T1s (Protected) STM1/OC3 Mux (Protected) 45 Proprietary and Confidential .

Native2 ring with 4 x 1+0 links – with STM1/OC3 Mux GE/FE 16E1/T1s STM1/OC3 (Mux) Native2 E M Native2 1+0 1+0 16 E1/T1s GE/FE E M Wireless Native2 Ring E M 16 E1/T1s GE/FE Native2 1+0 E M Native2 1+0 16 E1/T1s 46 GE/FE Proprietary and Confidential .

Native2 ring with 3 x 1+0 links + spur link 1+0 16 E1/T1s GE/FE GE/FE E E Native2 1+0 32 E1/T1s Native2 M Native2 1+0 GE/FE 1+0 16 E1/T1s GE/FE E M Wireless Native2 Ring E M 16 E1/T1s GE/FE Native2 1+0 47 Proprietary and Confidential .

Native2 ring with 4 x 1+0 MW links and 1 x fiber link (5 hops total) – with STM1/OC3 Mux GE/FE 16E1/T1s E M Native2 STM1/OC3 (Mux) Native2 1+0 1+0 16 E1/T1s GE/FE E M 16 E1/T1s GE/FE Native2 Wireless Native2 Ring E M 1+0 Native2 1+0 GE/FE GE 16E1/T1s 48 STM1/OC3 (Mux) Proprietary and Confidential GE/FE 16E1/T1s .

Native2 ring with 2 x 2+0/XPIC MW links and 1 x fiber link (3 hops total) – with 2 x STM1/OC3 Mux E E Native2 16E1/T1s 2 x STM1/OC3 (Mux) GE/FE 2+0/XPIC E M Wireless Native2 Ring E M Native2 2+0/XPIC GE E 32 E1/T1s GE/FE 2 x STM1/OC3 (Mux) M GE/FE 49 Proprietary and Confidential 32 E1/T1s .

protected) 50 Proprietary and Confidential .Native2 2+2/XPIC/Multi-Radio MW link – with 2 x STM1/OC3 Mux (Up to 150 E1s / 168 T1s over the radio) Native2 32 E1/T1s (protected) E 2+2/XPIC M E M GE/FE (protected) 2 x STM1/OC3 (Mux.

Integrated nodal solution – E1/T1 cross-connect • • • E1/T1 trails are supported based on the integrated E1/T1 cross-connect (XC) XC capacity is 180 E1/T1 bi-directional “VC” trails XC is performed between any 2 physical or logical interfaces in the node (in any main or expansion unit): • E1/T1 interface • Radio “VC” (75 “VC”s supported per radio carrier) • STM1/OC3 Mux VC11/VC12 Radio to radio STM1/OC3 Interface STM1/OC3 Interface Line to line E1/T1 interfaces Line to radio IP-10 integrated STM1/OC3 Mux E1/T1 interfaces IP-10 Integrated XC MW radio link 51 Proprietary and Confidential .

) • “Trace ID” for provisioning mis-match detection • A “VC overhead” is added to each “VC” trail in order to support the end-to-end OA&M functionality and synchronization justification requirements • Each “VC” trail is timed independently by the XC • XC function is performed by “active” main unit • In case of failure backup main unit takes over (<50msecs down time) 52 Proprietary and Confidential . UAS. etc. SES.Integrated nodal solution – E1/T1 cross-connect • For each “VC” trail the following end-to-end OA&M functions are supported: • Alarms and maintenance signals (AIS.) • Performance monitoring counters (ES. RDI etc.

APS commands. AIS. RDI.E1/T1 services – End-to-end multi-layer OA&M Native2 Native2 1+0 1+1 Packet or TDM based fiber aggregation network or leased lines FibeAir IP-10 FibeAir IP-10 FibeAir IP-10 Tail site Agg. etc.)  Performance monitoring  service Maintenance commands OA&M (Loop-backs. etc.) Support provisioning. site Fiber site E1/T1 service “VC” trail E1/T1 Interface Radio link Radio link STM-1/OC3 Interface  Full set of OA&M functionality is provided at all layers supporting T1/E1 services  Alarms and events  Maintenance signals (LOS. and SLA assurance 53 Proprietary and Confidential .

Example XC aggregation scenario STM1/OC3 Interface E1/T1 interfaces E1/T1 interfaces E1/T1 interfaces 54 Proprietary and Confidential .

IP-10 A • At the 2nd branching point – “Selection” of traffic from either main “VC” or back-up “VC” • Traffic from back-up “VC” is used in case of failure detection in main “VC” • Switch-over is done in <50 msecs. • Path for the Back-up “VC” (typically separate from the path of the main “VC” it is protecting • Back-up “VC” Main “VC” For each of the 2 directions of the back-up “VC” the following is performed independently: • At the 1st branching point – “Duplication” of the traffic from the main “VC” to the back-up VC.Wireless SNCP • • • IP-10 XC supports an integrated “VC” trail protection mechanism called “Wireless SNCP” Using this mechanism for each individual “VC” trail a back-up “VC” trial can optionally be defined For each back-up “VC” the following needs to be defined: IP-10 B E1 • Two “Branching points” from the main “VC” it is protecting. 55 Proprietary and Confidential E1 .

“Wireless SNCP” branching point • For each main “VC” trail the branching points can be any XC node along the path of the trail IP-10 D IP-10 B IP-10 C IP-10 A E1 #2 E1 #1 E1 #2 IP-10 B E1 #1 56 Proprietary and Confidential .

Supporting wireless SNCP with a mixed wireless/optical network IP-10 integrated STM1/OC3 Mux STM1/OC3 fiber link IP-10 Integrated XC IP-10 D MW radio link E1 #2 IP-10 C IP-10 A E1 #2 E1 #1 • Wireless SNCP is supported also over fiber links using IP-10 STM1/OC3 Mux interfaces IP-10 B • Using this feature a fully integrated solution for protected E1/T1 services over mixed wireless/optical network is provided E1 #1 57 Proprietary and Confidential .

Wireless SNCP Advantages • It’s about Flexibility • Any network topology (ring. mesh. tree) • Any traffic distribution pattern (excels in hub traffic concentration) • Any mix of protected and non-protected trails • No hard limit on the number of nodes in a ring • Switch-over time not dependant on the number of nodes in a ring • Simple provisioning of protection 58 Proprietary and Confidential .

• It’s about Performance • Non traffic affecting switch to protection (<50ms) • Switch to protection is done at the E1/T1 VC trail level – works • perfectly with ACM (don’t have to switch the entire traffic on a link) Optimal latency under protection • It’s about Interoperability • Protection is done at the end points .Wireless SNCP Advantages. cont.g.BLSR) 59 Proprietary and Confidential .independent of • equipment/vendor used in other parts of the network Interoperable with networks that use other types of protection (e.

NMS support for XC functionality • Full NMS level support using Ceragon’s NMS platform (PolyView) including: • Trail management/provisioning • Central alarm management • Central performance monitoring management 60 Proprietary and Confidential .

Thank you! 61 61 Proprietary and Confidential .