HLD VF-MAN-Refresh v0 6

VF MAN Refresh
NOKIA ION
July’18
1 © Nokia 2018 Confidential

Agenda
1 2 3 4
Introductio Re- Engineeri Migration
n design ng rules procedure
highlights s

Introduction
Scope
• Swap current legacy nodes with same product family with updated Hardware and Software.
• The Hardware to be swapped are:
- SR7/12 RNAs – swapped with SR7/12/a8 with updated Chassis and cards (based on FP3 technology).
- SR7/12 RNBs – removed from network; its current services are moved to RNA/RNP.
- ESS7 RNPs – swapped with SRa8 chassis (based on FP3 technology).
• To optimize cost it is also used Nokia 7210 SAS-Sx as port extension for RNA/RNP (Satellite
mode).
• The Software is updated from SR-OS10 to SR-OS15.
• Re-design with focus on new Hardware and Software changes.
• Services design remains the same (no service redesign).
• Other MAN nodes are outside the scope of this project (MS, RPE, LNS).
• Other SR7750 nodes in VF network are outside the scope of this project (VFIX, RSR, PEES,
PPES…).

DRAFT
RR-6PE RR-VPNv6 RR-IPv4 RR-VPNv4
Introduction
Basic network topology
Integration in VF Network:
CORE
iBGP
1. MANs deployed all over Spain.
ISIS L2
 Some with single RNA and some with dual. + LDP
+ RSVP
 Depending on MAN size it may include or may not MS, RPE, LNS and RNP.
RNA RNA*
2. IGP is ISIS L1 inside MAN and ISIS L2 outside.
3. MPLS RSVP and LDP are used as MPLS transport protocols. ISIS L1
+ LDP
4. BGP IPv4/IPv6/VPN-IPv4/VPN-IPv6 are used in RNA. + RSVP
5. RNA terminate L2 & L3 services. NxRNP*

…
6. RNP will terminate L2 services.
NxRPE NxLNS*
 If L3 is needed it is backhauled to RNA (EPIPE/VPLS) except for Internet in ISIS L1
*
+ RSVP
Stinger that is terminated in RNP/IES.
MS*
RNA RNP
7750 SR7/12 or 7750 SRa8
7750 SRa8 * Optional

DRAFT
Introduction
Basic service overview
Main services
1. Enterprise L3 VPN using VPRN (VPN MPLS)
2. Enterprise L3 Internet using IES/GRT (Internet Corporativo)
3. Enterprise L2 VPN using EPIPE/VPLS (VPN VPLS)
4. DSLAM-IP Internet using IES (2 flavors, one using RIP(Stinger) and other using BNG-PPPoE(ISAM) in RNA)
5. DSLAM-IP VoIP (Multimedia)
6. HFC Residential VoD service using VPLS (VEO)
7. Several management services using IES/EPIPE/VPLS…
Most of the services are Ethernet based (FE/GE/10GE).

Enterprise services also use NxDS0, NxE1, E3, STM-1 with Frame-relay, IPCP, BCP and ATM
encapsulations!
DRAFT
Ethernet + ASAP
Introduction
Main services
1. Enterprise L3 VPN using VPRN (VPN MPLS) 2. Enterprise L3 Internet using IES/GRT (Internet Corporativo)
CE RPE RNA CE
VRF VPR
N
RNA
RNA
VPRN
IES IES
Static
BGP Static
RIP TX EPIP
RNP BGP Default-gateway
BGP Full Routing TX EPIP
RNP
E BGP other flavours
E
CE CE
CE CE
+ PE-CE redundancy BGP with SOO to avoid loops + PE-CE redundancy BGP with Local-Pref based on
communities

DRAFT
Ethernet + ASAP
Introduction
Main services
3. Enterprise L2 VPN using EPIPE/VPLS (VPN VPLS)
EPIP EPIP
 Some services may include MC-LAG and/or Active/Standby pseudowires. E E
 Some services may include explicit RSVP path to avoid link congestion. CE RNA/RNP RNA/RNP CE
Point to Point (EPIPE)
Full-Mesh
VPLS
VPLS VPLS
CE RNA RNP CE
SH
Full-Mesh VPLS
G
H-VPLS
VPLS RNA SH
G
VPLS
CE RNP
RNA CE
Multipoint to Multipoint (VPLS)

DRAFT
Introduction
Main services
4. DSLAM-IP Internet using IES (2 flavors, one using RIP(Stinger) and other using BNG-PPPoE(ISAM) in RNA)
Internet Stinger
RIPv2
IES
0.0.0.0/0 @IP Servicios Internet CE

RNA/RNP DSLA
@IP Gestión
M
Stinge
r
Internet ISAM
Only present in 2 RNA

IES with few sessions
PPPoE
RNA DSLA CE
M
ISAM

DRAFT
Introduction
Main services
5. DSLAM-IP VoIP (Multimedia)
VRRP + Hair-pinning Multimedia Stinger
Partial-mesh
IES
VPLS @IP Svc Multimedia
VPLS IES DSLA
RIPv2 M
CE RNA VRRP Stinge
r
VPLS VPLS IES
IES
CE DSLA RNP RNA @IP Svc Multimedia

M DSLA
RNA
Stinge M
r Stinge
r

DRAFT
Introduction
Main services Local VPLS
6. HFC Residential VoD service using VPLS (VEO)

VPLS VPLS HFC network
MS RNx
VoD Servers
EQAM
Local VPLS on other MANs

VPLS VPLS
HFC network
H-VPLS
Mesh VPLS
VPLS VPLS VPLS VPLS HFC network

VPLS
MS RNx RNx
MS RNP VoD Servers
VoD Servers EQAM
EQAM
Madrid & Barcelona Distributed VPLS on other MANs

DRAFT
Agenda
1 2 3 4
highlights s

Switch Fabric
Re-design highlights
SFM/CPM5 & Fabric speed B (SR7/12)
• CPM Pluggable: reduces sparing and de-couples CPM5 from SFM5
• CPU runs 2x as fast as previous two generations
- CPM3 & CPM4 run a 10-core CPU at 750MHz
- CPM5 runs a 10-core CPU at 1.5GHz
Test CPM3 / CPM4 CPM5 Comments

BGP 1M route transfer time 83.4s 39.1s Tasks running at same CPU% utilization Pluggable CPM
OSPF 300k LSA routes transfer time 39.4s 22.9s
ISIS 10k route transfer time 10.5s (100%) 9.6s (80%) ISIS task in brackets
Cflowd PPS sampling 270k PPS 500k PPS Task running at 100%
CF copy 100MB 78.1s 42.5s
• SR7/12 Fabric-speed B:
• Switch capacity improvement on the 7750 SR-7/12: Per Slot Max Switch Capacity FD
200G per slot FD redundant Mix of T2/T3 Cards All T3 Based Cards
• Need all cards to have T3 connection to switch fabric
SFM5 100 Gb/s redundant 200 Gb/s redundant
(IMM FP3 or IOM3-XP-C)
SF/CPM4 100 Gb/s redundant 100 Gb/s redundant
• Higher capacity to switch fabric for BUM (2Gbps links on
SF/CPM3 50 Gb/s redundant 50 Gb/s redundant
legacy nodes to 8Gbps on new SR7/12).

DRAFT
SF/CPM 2* SF/CPM 3 SF/CPM 4 SF/CPM 5

C CPM type
SR/ESS -7/-12 SR/ESS -7/-12 SR/ESS -7/-12 SR/ESS -7/-12
Multicore Architecture Multicore Architecture Multicore Architecture
Technology 2 processors @ 600 MHz
10 core CPU @ 750 MHz 10 core CPU @ 750 MHz 10 core CPU @ 1.5 GHz
Memory 2 GB 4 GB 8 GB 16 GB
• High Accuracy Oscillator
• High Accuracy • BITS-in & BITS-out, 1pps Timing Output
• High Accuracy Oscillator
• Standard Oscillator Oscillator (1.0/2.3 BNC)
CPM Sync Support • BITS-in & BITS-out
• BITS-in • BITS-in & BITS-out • Ethernet timing port: GE RJ45 on CPM for
• 1588v2 supported
• 1588v2 supported Sync-E/1588v2 (in/out)
• 1588v2 supported
Centralized BFD & Eth-OAM
20k pps (P1-based) 500k pps (P1-based) 500k pps (P1-based) 500k pps (P2-based)
(runs on “P” chip)
Extra Capabilities Pluggable CPM, 2 x OES ports
Total System Switch
500G / 1Tbps HD 500G / 1Tbps HD 1T / 2Tbps HD 2T / 4Tbps HD
Capacity (Redundant)
Total Slot Switch Capacity
50Gbps FD 50Gbps FD 100Gbps FD 200Gbps FD
(Redundant)
Single-stream multicast
SFM ~2 Gbps per stream ~2 Gbps per stream ~4 Gbps per stream ~8.25G per stream (SR-OS>13.0.R4)
bandwidth
IOM1*, IOM2*, IOM3,
IOM1*, IOM2*, IOM3, IOM4-e, IOM1*, IOM2*, IOM3, IOM4-e, IOM1*, IOM2*, IOM3, IOM4-e, 50G/ 100G IMM,
Compatible IOM/IMMs
50G/100G IMM 50G/100G IMM, 50G/ 100G IMM, 200G IMM 200G IMM
200G IMM
* Obsolete HW not supported on SR-OS15

DRAFT
• Replacement of legacy IOM1/2/3 with new cards with connection to backplane ready to 200Gbps per slot:
- IOM3-XP-C (3HE08426AA) – 50Gbps FD
10G I/O
MDA XB Q2 T3
To
fabric
MDA-XP XB P2 P2
25G I/O
- IMM2-PAC-FP3 – 200Gbps FD
• 20x10GE (3HE07305BA) – License L3BQ (100VPRN, 100queues/port) FP3 (200G Layout)
• 20x10GE with license10x10GE (3HE07305XC) – License L3BQ (100VPRN, 100queues/port)
100GE Q3 T3
XB
To
fabric
100GE
P3 P3

DRAFT
FP3
RNA type SRa8
• Class-leading GE and10GE density for a range of oversubscribed scenarios

• High-performance 40GE and 100GE uplinks available today
• Highly programmable FP3 delivers feature velocity and continuous innovation
• FP3 ensures there is no tradeoff between performance and advanced services 400G (half duplex, max) capacity.
• 100G Full-Duplex each IOM (FP3).
• 2x MDA-XP up to 100GE (one each IOM)
• 6x MDA 25G (3 each IOM).
• 7RU/31 cm high, 240 mm deep, fits easily in a 300-mm
cabinet
• Modularity enables full system redundancy on all common
equipment, including control
• No switch fabric (direct connection between IOMs)

DRAFT
FP3
RNA type SRa8
• Power Supply Units (PSU)

• There are 4 slots to be used for PSU. +
• In VF nodes 1+1 high-line DC PSU are installed to provide power redundancy.
• Licenses:
• RNA: L3BQ license with up to 100 VPRN and 100 queues per port.
• RNP: L2HQ license with up to 20 VPRN, no limit on queues (hardware limit still in place…)
• Some RNA have additional limited license:

• To use only one IOM and no MDA-a XP (RTU License).

DRAFT
48 x GE SFP (3HE10492AA) 4x10GE Uplinks
Satellite support
• 7210SAS-Sx as port extension of 7750 SR7/12/a8.

• Two variants in VF: 48 ports 1G SFP and 48 port 1G RJ45.
• All services and QoS functions are handled by the 77x0 SR host chassis. 48 x GE RJ-45 (3HE10494AA) 4x10GE Uplinks
• Recommended to configure 2 uplinks to one IOM/IMM and the other 2 uplinks to
another IOM/IMM and provide “Satellite Uplink Resiliency” (SR-OS15.0R8)
- Minimum 2 Uplink to provide IOM/IMM redundancy.
• Satellite automatically discovered and provisioned
7210 SAS-S\SX
• All Management is through host - Satellite is an extension of the
host reducing the number of entities to be managed
7750 SR7/12/a8 7210SAS CPEs
• No local switching; traffic is passed back to host
• Satellite adds a VLAN tag for all traffic back to host
• 1-4 10GE uplinks per satellite; 24-48 GE Access ports
• Ethernet satellites supported on the 7750 SR-7/12/a8 (and others)
• Requires SF/CPM5
• Requires IOM3/IMM linecard
7x50
• Satellite “access” ports configured as access ports on host
Uplinks (up to4x10GE) • “Access Port” services & service level QoS supported on host
• “Access Port” can be configured in access/network/hybrid mode
• Satellite software upgrades independent of host

DRAFT
BGP 6PE different RIB
SR OS
10
ADD RECEIVED IMPORT ALL NON-
ROUTES TO ONE BGP IPV6 ROUTES
IPv6 peer (SAFI1) RIB Other
IPv6 Route Table Protocols
Label-IPv6 peer BGP RIB
(SAFI4) ADV SAME BEST
PATH TO BOTH
SUBMIT BEST ROUTES
PEER TYPES
IMPORT BASED IMPORT BASED

SR OS
ON POLICY ON POLICY >14.0.R4
IPv6 Route Table LABEL IPv6
IPv6 peer (SAFI1)
BGP RIB BGP RIB Label-IPv6 peer (SAFI4)
SUBMIT BEST SUBMIT BEST
Other
Protocols
• By default BGP unlabeled routes are no longer advertised to BGP label peers and vice versa
- This can still be achieved, but it requires a non-default route-table-import policy that accepts BGP routes of the other type

DRAFT
BGP MED in VPRN
• Need to adapt Base BGP and VPRN BGP to new behavior on SR-OS >14.0R4
SR-OS10 (default):
SR OS
• Compare MED if both routes includes the attribute and comes from same AS. 10
• Compare MED also between families/RIB (for instance: IPv4VPNv4, IPv6VPNv6)
SR-OS>14.0R4 (default):
• Compare MED if both routes includes the attribute and comes from same AS.
• Do not compare between different families/RIB.
SR OS
>14.0.R4
SR-OS>14.0R4 (tuned)  “always-compare-med strict-as zero” Global+VPRN:
• Compare MED if comes from same AS; no MED  MED=0 (or MED=infinite)
• Compare MED also between families/RIB
IMPACT VF: No impact foreseen, in GRT Local-preference is used (based on marked communities by
customer) and in VPRN AS prepends are used instead, so “default” tuning can be deployed.
DRAFT
Minor BGP changes
• Next-hop-self.
• From SR-OS12.0R11/13.0R4 onwards next-hop-self is enforced included those routes learnt by iBGP.
• No high impact foreseen for VF MAN (only Loopback0 from RPE/LNS is re-advertised from RR client to RR
server).
• Direct-interface.
• From 15.0R1 onwards when using “default-action accept” in vrf-export policies each IP interfaces announces
to its iBGP VPNv4 neighbors the LAN of this IP interface along with /32 specific IP. It may impact dual-homed
scenarios.
• No impact foreseen for VF MAN (vrf-export policies do not use “default-action accept”).

DRAFT
Network QoS for new HW Only EF/Queue6 is
expedite
Strict priority
Network-queue
Port-Scheduler
Network (egress) Port Slope-policy
(>CBS)
CIR 5%
FC NC Queue 8/NC Level 8
CBS=5%
MBS=25%
No shared buffers
(CBS=MBS)
FC EF Queue 6/Pt
CIR=Rate=100%
Level 6
CBS=MBS=5ms
CIR=Rate=100%
FC AF Queue 4/Au Level 4
CBS=MBS=30ms
Rate=100%
Weight 7
FC L2 Queue 2/Ag CIR=0
Level 2 Physical Port
Rate=100%
RED on shared CIR=0
FC BE/H1 Queue 1/Bz
buffers (CBS<MBS) Rate=100% Weight 3
CIR=0
FC L1 Queue 3 Orphan
Rate=0%
CIR=0
No buffer (MBS=0) FC H2 Queue 7 DROP Some levels not in use
Queue-group
Network, Slope-policy, Network-queue and Port-scheduler policies can be the same whatever IOM/MDA
Queue-group is dependent only by port type 1GE or 10GE
DRAFT
Basic features
• Rollback
• CPM-filter harmonization and simplification (using prefix-list)
• Next-Hop tracking policies (to not consider default and /1 routes)

DRAFT
CLI changes
• Routing:
- Static-routing
- ISIS “suppress-default” to “ignore-attached-bit”
- ISIS SPF y LSP-wait timers
- LDP “peer-parameters” to “tcp-session-parameters”
- BGP 6PE (family “label-ipv6” instead of “ipv6” + “advertise-label ipv6”)
- BGP shortcut and 6PE resolution
- BGP Prefix-limit per family (instead of global)
- “Action reject” to “action drop” (+exit) on routing policies
- Community add + remove now need to be separated on two different actions (instead of 1)
• QoS “high-priority-only” parameter to “drop-tail low percent-reduction-from-mbs”
• VPRN auto-binds
• ACL/Filters “action drop” to “action” & “drop” (+exit)

DRAFT
CLI changes
• Subscriber management:
- “use-std-acct-attributes” to “include-radius-attribute std-acct-attributes”
- “Host-limits 1” to “host-limits overall 1” (in sla-profile context)
- “radius-accounting-policy” to “radius-accounting policy” (in sub-profile context)
To be completed if needed during testing…

DRAFT
Agenda
1 2 3 4
highlights s

CORE links do not need to change
even if RNA is using LAG (without
Network Engineering rules LACP)
MAN with 2xRNA NETWORK LAGs: 1-100
ACCESS LAGs: 101-200 (102&103 for Hair-
pinning)
If parallel interfaces
are needed SPLIT RNA-RNA and
CORE on different
IOM
All connections to same RNP on IOM x IOM x

same IOM/IMM/MDA (if possible) IOM y IOM y
EQAM
SPLIT (If possible) IOM 1

RNA1=IOM1
RNA2=IOM2 IOM 2 All to same IOM
MS (if possible)
All Network connections MUST be created using LAGs

DRAFT
CORE links do not need to change
even if RNA is using LAG (without
Network Engineering rules LACP)
MAN with 1xRNA NETWORK LAGs: 1-100
ACCESS LAGs: 101-200 (102&103 for Hair-
pinning)
If parallel interfaces
are needed
SPLIT each CORE on

different IOM
IOM x
IOM y
Half connections on one
IOM and other half on other
IOM (if possible) – also in
RNA
IOM 1 IOM 1
IOM 2 RNP with only 1 IOM
(or 2 IOMs but no MDA SFP on all)
All Network connections MUST be created using LAGs

DRAFT
Network Engineering rules
Satellite and others
SPLIT Satellite uplinks
• Satellite: to different IOM
RNA/RNP
SATELLITE 4x10GE Uplinks
IOM x
IOM y
• Hair-pinning: RNA/RNP Initially only 2x10GE deployed, uplinks 49

& 50 to different IOM/IMM in RNA/RNP
Build hair-pinning the same as now,
using 1x1GE in same IOM & MDA
(or satellite)
IOM 1
Hair-pinning built over LAG 102 (L2 side)
and LAG 103 (L3 side or network side)
IOM 2

DRAFT
Network Engineering rules 25Gbps MDA-a
MDAs in SR-a8
100Gbps MDA-a XP
20–port GE MDA-a
10–port 10GE MDA-a XP
2-port 10GE + 12-port GE MDA-a
22-port 1GE SFP MDA-a

(or 44-port 1GE cSFP)
RULE:
- MDA-a XP in positions 1/1 or 2/1
MDA-a (non-XP) is limited to 25 Gb/s; installing the module in a
- MDA-a in positions 1/2, 1/3, 1/4, 2/2, 2/3 or 2/4 100 Gb/s slot is possible but it does not increase the throughput.
29 © Nokia 2018
Confidential DRAFT
Network Engineering rules
ASAP MDAs
• If Nx MDA ASAP are to be installed in RNA it is recommended to install those MDA providing
redundancy of timing reference.
• This is archived if connected in different IOM positions depending on time Reference (1 MDA in IOM
Reference 1 and 1 MDA in IOM Reference 2):
Reference 1 Reference 2
SR7 MDA ASAP in IOM 1 or 2 MDA ASAP in IOM 3, 4 or 5
SR12 MDA ASAP in IOM 1, 2, 3, 4 or 5 MDA ASAP in IOM 6, 7, 8, 9 or 10
30 © Nokia 2018
Confidential DRAFT
Agenda
1 2 3 4
highlights s

Migration procedures
MAN with single RNA

Considerations for new nodes:
- New naming.
Migration procedures - New addressing.
MAN with single RNA
MANs:
 Málaga (+5RNP + 1LNS)  Lérida
 Zaragoza (+4RNP + 1LNS)  Gerona
xxx-CORE-1 xxx-CORE-2
 Tenerife (+2RNP + 1LNS)  Álava
 Valencia (+2RNP)  Navarra
 Las Palmas (+1RNP +1LNS + 2RPE)  Logroño
 Alicante (+1RNP + 1LNS)  Oviedo
 Tarragona (+1 RNP)  Coruña
 Córdoba (+1RNP)  Vigo
xxx-RNA-01  Granada (+1RNP)  Murcia
 Jaén (+1RNP)  Cádiz
 Valencia 1 (+1RNP)  Santander
 Valladolid (+1LNS)  Burgos (SRc12)
 León (+1LNS)  Huesca (SRc12)
…
NxRNP  Palma de Mallorca (+1LNS)  Lanzarote (SRc12)
 Menorca (SRc12)

DRAFT
Move connections, no spoke-sdp termination migration yet
MAN with single RNA
Interim metric N-1
xxx-RNA-01
1. New RNA installation
 Connected re-using ports (CORE, legRNA)
 Need to re-configure interMAN PATHs RSVP (if any).
Metric=1  Need to add LDP peer on connected nodes.
… New  Need to add BGP neighbor on BGP RR.
NxRNP @IP  Add new LSP/SDP to new node in MAN.
 Metric modification.
 Extend VPLS services to new RNA.
 Move connections from legacy-RNA to new RNA

DRAFT
MAN with single RNA
If LAG (or Nx connections) it is possible

to migrate port by port in order to
minimize impact. New @IP.
2. Swap RNPs
…  Connected re-using ports
NxRNP
 Need to add LDP peer on connected nodes.
 Add new LSP/SDP to new node in MAN.
 Move connections from legacy-RNP to new RNP
 Extend VPLS to new RNP
 L3 services spoke-sdp termination to new RNAs

DRAFT
MAN with single RNA
2. Swap RNPs
…  Connected re-using ports
NxRNP
 Remove legacy-RNP
Repeat until all RNPs are migrated

DRAFT
MAN with single RNA
Metric N
3. Remaining CORE re-connection

…  Re-configure interMAN PATHs RSVP (if any).
NxRNP
 Configure metric to its original value.
4. Remove legacy-RNA

DRAFT
MAN with single RNA
xxx-RNA-1
…
NxRNP

DRAFT
MAN with 2x RNA

- New naming.
MAN with 2xRNA
MANs:
 Barcelona (+22RNP + 3RPE + 2LNS + 2MS)
xxx-CORE-1 xxx-CORE-2  Sevilla (+9RNP)
xxx-RNA-01 xxx-RNA-02
… Barcelona and Sevilla have an additional RNA each one (without RNPs). When main MAN
NxRNP is migrated those SAPs from this 3rd RNA must be moved from legacy-RNA to new RNAs.
BARC-RNA-02 chassis is re-used in network.

Strategy would consist on install new-RNA in BARC, move BARC-RNA-02 connections
to new-RNA in BARC and re-use chassis with new-RNA in BAR2.

DRAFT
MAN with 2xRNA
Interim metric N-1

Metric=1
New
 Connected re-using ports (CORE, legRNA).
@IP  Need to re-configure interMAN PATHs RSVP (if any).
…  Need to add LDP peer on connected nodes.
NxRNP  Need to add BGP neighbor on BGP RR.
 Move connections from legacy-RNA to new RNA.

DRAFT
MAN with 2xRNA

…  Need to re-configure interMAN PATHs RSVP (if any).
NxRNP  Need to add LDP peer on connected nodes.
 Need to add BGP neighbor on BGP RR.
 Metric modification

DRAFT
MAN with 2xRNA
New
@IP
3. Swap RNP
 New RNP connected to new RNA (connection 1)
…  Need to re-configure interMAN PATHs RSVP (if any).
NxRNP  Need to add LDP peer on connected nodes.
 Extend VPLS services to new RNP

DRAFT
MAN with 2xRNA
New
@IP
3. Swap RNP
…  Move connections from legacy-RNP to new RNP
NxRNP
 Move MS and Veo connections (BCN)

DRAFT
MAN with 2xRNA
…
3. Swap RNP
NxRNP  New RNP connected to new RNA (connection 1)
 Move MS and Veo connections (BCN)
Repeat until all RNPs are migrated

DRAFT
MAN with 2xRNA
Metric N
New
@IP
…
4. Remove legacy-RNA (connect new RNA between them)
NxRNP  Need to re-configure interMAN PATHs RSVP (if any).
 Configure Metric to its original value.

DRAFT
MAN with 2xRNA
…
NxRNP

DRAFT
Madrid MAN (& re-merge)

- New naming.
Madrid MANs
MANs:
• Initial topology: MA3-CORE-1 MA1-CORE-2
 Madrid (+42RNP +4RPE +2LNS +2MS)
 + Additional RNAs (BPAL-RNA-03/04)
ATC-RNA-01 BPAL-RNA- ATC-RNA-02 BPAL-RNA- BPAL-RNA- BPAL-RNA- MA3-RNB-01 MA1-RNB-02

01 02 03 04
… … Once new RNAs available all

NxRNP NxRNP Ethernet/ASAP SAPs can be moved to new
nodes.
FOCUS ON MAN MIGRATION &

MERGE
MA1-AT-MS- MA1-AT-MS- BPAL-RNA-04 chassis is re-used in network.
1 2 Strategy would consist on install new-RNA in BPAL, move BPAL-RNA-04
connections to new-RNA in BPAL and re-use chassis with new-RNA in
ATC.
DRAFT
Madrid MANs
MA3-CORE-1 MA1-CORE-2
Interim metric N-1
Metric=1
New 1. New RNA installation
… … @IP
NxRNP NxRNP
 Metric modification
MA1-AT-MS- MA1-AT-MS-
1 2  Extend VPLS services to new RNA
DRAFT
Madrid MANs

… …  Connected re-using ports (CORE, legRNA).
NxRNP NxRNP
1 2  Extend VPLS services to new RNA.
 Move connections from legacy-RNA to new RNA.
DRAFT
Madrid MANs
New
@IP
3. Swap RNP
… …  New RNP connected to new RNA (connection 1)
NxRNP NxRNP
MA1-AT-MS- MA1-AT-MS-  Extend VPLS services to new RNP (except VPLS VEO).
1 2  L3 services spoke-sdp termination to new RNAs

DRAFT
Madrid MANs
New
@IP
3. Swap RNP
NxRNP NxRNP
1 2

DRAFT
Madrid MANs
3. Swap RNP
NxRNP NxRNP
 Move MS and Veo connections
1 2

DRAFT
Madrid MANs
3. Swap RNP
NxRNP NxRNP
MA1-AT-MS- MA1-AT-MS- Repeat until all RNPs are migrated
1 2

DRAFT
Madrid MANs
Metric N
New
@IP
4. Remove legacy-RNA (connect new RNA between them)

… …  Need to re-configure interMAN PATHs RSVP (if any).
NxRNP NxRNP  Need to add LDP peer on connected nodes.
1 2

DRAFT
During RNP swap migration redundancy is penalized
(spoke-sdp termination with RSVP LSP – alternative mixed-lsp
Migration procedures SDP)
Madrid MANs
New
@IP
5. Swap RNP from other MAN
… …  Add new LSP/SDP to new node in MAN.
NxRNP NxRNP
 Extend VPLS services to new RNP (except VPLS VEO)
 Need to re-configure interMAN PATHs RSVP (if any)
1 2 Warning: New RNPs with connection to both MANs must use 2 ISIS instances

DRAFT
Madrid MANs
New
@IP

NxRNP NxRNP
1 2

DRAFT
Madrid MANs

NxRNP NxRNP
1 2 Repeat until all RNPs are migrated

DRAFT
Madrid MANs
6. Remove legacy-RNA
… (previously move connections from legacy-RNA to new RNA)
NxRNP
1 2

DRAFT
Madrid MANs
xxx-RNA-1 xxx-RNA-2
…
NxRNP
1 2

DRAFT
Impact analysis

Impact Analysis
Type of movement Detail Estimated impact
Uplink movement Uplink redundancy to different nodes is routing/mpls protected No impact foreseen for most services.
(RNAs, RNPs in Madrid/Barcelona/Sevilla, most RPEs) Few seconds for high capacity VPLS based on inter-
MAN if RSVP resignal is needed..
Uplink redundancy to same node (without LAG/LACP) is No impact foreseen for most services.
routing/mpls protected (some RNPs in single-RNA MANs) Few seconds for high capacity VPLS based on inter-
MAN if RSVP resignal is needed.
Uplink redundancy to same node (with LAG) produces micro- Few seconds.
cut when last LAG member is moved (most of RNPs in single-
RNA MANs)
No uplink redundancy impact during port movement (few RNP Few minutes (depends on physical port movement).
in single-RNA MAN, few RPE, and LNS)
Access port movement It’s service affecting when moving the port Few minutes (depends on physical port movement).
VPLS 11 (VEO) It’s service affecting when moving the ports Few minutes (depends on physical port movement).
migration

DRAFT
List of MOPs

List of MOPs – Main MOPs
MOP Basic notes
1 MAN Swap – 1xRNA MAN type It includes procedures to swap MANs with single RNA, this MAN may or may not have RNP.
2 MAN Swap – 2xRNA MAN type It includes procedures to swap Barcelona, Sevilla and 1st Madrid MAN.
3 RNP MAN Swap & movement It includes procedures to swap RNP nodes at same time this nodes are migrated to another
MAN (2nd Madrid MAN).
Already highlighted on previous slides

DRAFT
List of MOPs – 3rd party elements MOPs
MOP Basic notes
1 New LDP peer Include new node as LDP peer (open firewall, configure MD5, …)
It affects legacy RNA/RNP, MS, CORE, RPE/LNS.
2 New iBGP session Include new node as BGP client (IPv4, 6PE, VPNv4, VPNv6) (and adapt filters if needed)
It affects Route-Reflectors, RPE/LNS, legacy RNA.
3 Physical connection change Change descriptions for those ports re-utilized.
It affects legacy MS, CORE, RPE/LNS (it would affect legacy RNA/RNP but it isn’t meaningful
to do this job for short-timed nodes).
4 Metric modification Change metric on connections towards RNA at CORE routers.
5 Static-routing modification on L3 HSI service (Internet Corporativo) management adaptation to new topology.
SSGG router Static-route to new-RNA instead to legacy-RNA.

DRAFT
List of MOPs – Services related MOP
MOP Basic notes
1 VPLS extension Include new nodes on VPLS (it doesn’t apply to MS connections)
2 VPLS interMAN TE RSVP Modification of TE RSVP Path to adapt to new nodes introduction
modification
3 Access port migration Movement of access ports from legacy-RNx to new RNx (Ethernet and ASAP) (except MC-
LAG)
4 VEO VPLS migration Movement of network and access ports for VEO connections
5 Hair-pinning remaining services Movement of specific services using Hair-pinning from legacy-RNA to new-RNA
migration
6 MC-LAG port migration Movement of ports belonging to MC-LAG

DRAFT
MOP Basic notes
1 VPLS extension Include new nodes on VPLS (it doesn’t apply to MS connections)
 If MAN already have the VPLS configured:

 On all participating MAN nodes add the mesh-sdp to new node.
 On new node create VPLS with mesh-sdp with each other participating node in MAN.
VPL VPL  If new node is a new RNA & interMAN spoke-sdps are in legacy RNA move those
S S
spoke-sdp to new RNA.
 If MAN doesn’t have the VPLS configured:
 Elect an RNA of the MAN as exit point and configure the VPLS with Spoke-sdp to
VPL
… VPL other MANs (RNAs) (need to configure in all participant RNAs).
S S
NxRNP  Proceed with same procedure as “if MAN already have VPLS configured”.

DRAFT
MOP Basic notes
2 VPLS interMAN TE RSVP modification Modification of TE RSVP Path to adapt to new nodes introduction
New path!
VPL VPL
S S
Old path!
Strict HOP from local to remote
Strict HOP from remote to local
 Adapt TE RSVP paths to include interim/final topologies into account with changes on hops.
 For each RSVP-TE interMAN LSP several transitions would be needed (it can be optimized if movement of Network
links and these kind of services are done altogether).
DRAFT
MOP Basic notes
3 Access port migration Movement of access ports from legacy-RNx to new RNx (Ethernet and ASAP)
RNA case:
 Extend VPLS services if needed.
 Define new services and SAPs on new node (port shutdown).
 Move ports (shutdown on legacy node and no shutdown on new node).
 Adapt configurations:
 EPIPE: change remote site configuration with new node.
 VPLS: if high capacity interMAN adapt RSVP-TE Path at both ends.
Note: L2 services terminating to RNB should be migrated to terminate in this new RNA.
“Mirror” PORT/SAP configuration
… “Mirror” services (it may include QoS, routing policies,…)
NxRNP

DRAFT
MOP Basic notes
3 Access port migration Movement of access ports from legacy-RNx to new RNx (Ethernet and ASAP)
RNP case:
 Extend VPLS services if needed.
 Define related L3 services in new RNA (spoke-sdp termination).
 Define new services and SAPs on new node (port shutdown).
 Move ports (shutdown on legacy node and no shutdown on new node).
 Adapt configurations:
 EPIPE: change remote site configuration with new node.
 VPLS: if high capacity interMAN adapt RSVP-TE Path at both ends.
“Mirror” PORT/SAP configuration

… “Mirror” services (it may include QoS, routing policies,…)
NxRNP changing sdp-termination to new RNAs instead of
legacy-RNA/RNB

DRAFT
MOP Basic notes
4 VEO VPLS migration Movement of network and access ports for VEO connections
Legacy-RNP New-RNP Procedure for Madrid/Barcelona MAN:
 (previous procedure) Add new LDP peer in MS

 Define related L3 Network interface in new RNP.
 Define related L2 services in new RNP.
 Define new network Interface + LSP in MS. This is specific for Madrid/Barcelona MANs
Other MANs have a slightly different procedure
 In MS modify:
EQAM  Change port description.
 Modify SDP far-end and LSP.
MS
 Move all VEO connections (network and access)

DRAFT
MOP Basic notes
5 Hair-pinning remaining services Movement of specific services using Hair-pinning from legacy-RNA to new-RNA
migration
Partial-mesh
Multimedia service:
VPLS
VPLS IES  Configure Hair-pinning SAPs in new-RNA (L3 service and L2
SAP)
CE
 L3 interface must be configured in shutdown state.
 “shutdown” L3 interface on legacy-RNA and “no shutdown” on
VPLS VPLS IES
new-RNA.
CE DSLA RNP RNA
M
Stinge N3-VPN Legacy:
Hair-
r Conexión en red
pinning SDP
VL
L
PTN VF  Create Hair-pinning SAPs in new-RNA (L2 and L3 services)
SA
P
L3 PTN  L3 interface must be configured in shutdown state.
SA
P
VL SDP
L SDP
A/S Pseudowire
SDP
VL
L
 “shutdown” L3 interface on legacy-RNA and “no shutdown” on
CPE new-RNA.
RNA
VFIX
 Modify VFIX spoke-sdp from legacy-RNA to new-RNA.
DRAFT
MOP Basic notes
6 MC-LAG port migration Movement of ports belonging to MC-LAG
A. Preparation
MCS session  Extend VPLS service to new-RNA/RNP.
 Configure port (in shutdown), LAG, MC-LAG and services in new RNA/RNP.
 Configure MC-LAG peer session at MC-LAG peer to new-RNA/RNP in legacy-
RNA/RNP (for now without moved LAG).
New-RNx MC-LAG peer B. Port movement
Legacy-RNx
 Shutdown ports at legacy-RNA/RNP
 Move ports to new-RNA/RNP (ports still in shutdown)
C. Config adaptations
 Re-Configure LAG in MC-LAG context with new RNA/RNP in MC-LAG peer.
 Reconfigure EPIPEs from remote RNx/VFIX (if any)
 Activate ports in new-RNA/RNP.
CPE

DRAFT
Madrid MAN RNB & Capacity

LEGACY NETWORK NEW MAN REFRESH
MA3-CORE-1 MA1-CORE-2 OPTION 1:

- RNB2 CE moved to BPAL-RNA-1
- RNB1 CE moved to MA3-RNP-1
OPTION 2:
RNB RNA RNA RNA RNA RNA RNA RNB - MA3-RNP-1 converted to MA3-RNA-1 (RNB1 CE
1 1 2 3 4 2 1 2
moved to MA3-RNA-1)
ATOCHA
OPTION 3:
BASAUR FRAY - New MA3-RNA-1
I LUIS
Problems to MAN Refresh:
- ATC Uplink to CORE and B2B (not enough 10GE transmission)
- RNB access port movement from RNB to new nodes (not considered in BoM)
RNB1: 5x 10GE CE + 12x 1GE CE
RNB2: 4x 10GE CE + 9x 1GE CE

DRAFT
OPTION 1: OPTION 2: OPTION 3:

- RNB2 CE moved to BPAL-RNA-1 - RNB2 CE moved to BPAL-RNA-1 - RNB2 CE moved to BPAL-RNA-1
- RNB1 CE moved to MA3-RNP-1 - MA3-RNP-1 converted to MA3-RNA- - New MA3-RNA-1
1 (RNB1 CE moved to MA3-RNA-1)
10GE uplinks collocated with CORE-1 10GE uplinks collocated with CORE-1
and Tx from current RNB2 to CORE-2 and Tx from current RNB2 to CORE-2
MA3-CORE-1 MA1-CORE-2 MA3-CORE-1 MA1-CORE-2 MA3-CORE-1 MA1-CORE-2
New Tx New Tx New Tx 2xIOM-a L3BQ

(4x10GE) New Tx (2x10GE) (2x10GE) (HW from 01GOY-RNP-1)
(4x10GE)
ATC-RNA-1 BPAL-RNA-1 MA3-RNA-1 MA3-RNA-1

MDA 2x10GE IOM3
MDA 20xGE
New Tx MDA 2x10GE ATC-RNA-1 BPAL-RNA-1 ATC-RNA-1 BPAL-RNA-1
(2x10GE) IOM3
IOM3
10GE Tx from current New Tx New Tx
MDA 20xGE MDA 20xGE
RNB2 to CORE-2 (2x10GE) (2x10GE)
2xIOM-a L3BQ
MA3-RNP-1
MDA-a XP 5x10GE and 2x MDAa 2-10G+12G from 01GOY-RNP- MDA-a XP 5x10GE and 2x
1 MDAa 2-10G+12G from
01GOY-RNP-1 MA3-RNP-1
CONS: HW + worst case TX (10x10GE) + special CONS: HW + TX (best case Tx) + special migration CONS: HW + TX (best case TX)
migration procedure procedures/inventory (most HW is reused from (most HW is reused from 01GOY)
01GOY)
DRAFT
ANNEX

ANNEX
To be discussed
 What about naming? Proposal:

 Same naming without “0”, ex. BPAL-RNA-01  BPAL-RNA-1
 What about sdp-id? Proposal:

 New nodes to new nodes = follow current rule*  this is the target numbering 
 New nodes to old nodes and vice versa
 Range 0-999.
 Assign an ID per node 0-165.
 SDPs to this node will be NxID (with N up to 6 to consider: LDP, RSVP, others…)
 Special-cases:
 MS with RNP  one-shot VEO migration (per-node) – keep same numbering.
 VFIX with RNA/RNP  need to change as previous step or as last step.
* little adaptation on demarcation ID to follow postal codes

DRAFT
WARNING MA3-RNB-01: CPE with MC-LAG configured, it must have uplink
redundancy otherwise MCS session would be broken and dual Master may cause
Migration procedures outages.
MA3-RNB-01 special case (non collocated to any RNA)
BASAUR FRAY
1GE or 10GE access I LUIS
connections moved to MA3-CORE-1 MA1-CORE-2
MA3-RNP-01 ATOCHA
ATC-RNA BPAL-RNA
CPE MA3-RNB-01
MA1-RNB-02
Old RNB-RNB connection used to add uplink capacity in RNP
MA3-RNP-01 Old 1GE uplinks should be dismounted
MDAa-XP 5-10G
Need 10GE cards… not included in 2x MDAa 2-10G+12G
BOM
RECOMMENDED (MUST) 2x10GE NEW TRANSMISSION BETWEEN BASAURI & ATOCHA

DRAFT
Madrid capacity planning
LEGACY NETWORK REFRESH NETWORK
ATOCHA
MA3-CORE-1 MA1-CORE-2 MA3-CORE-1 MA1-CORE-2
2G+2G 2.5G 3G 4G 5G 2G+2G
RNB RNA RNA RNA RNA RNA RNA RNB RNA RNA
1 1 2 3 4 2 1 2 1 1
2G + 1.5G 200M
More capacity
recommended
(4x10GE)
BASAUR FRAY BASAUR ATOCHA FRAY

I LUIS I LUIS
June 1st 9:00 and June 6th 15:00 ≈ 26 Gbps BPAL 6x10GE
6x 10GE uplinks (paired)
MA3 ≈ 11.5 Gbps + MA1 ≈ 14.5 Gbps uplinks
ATC 2x10GE
CAPACITY PLANNING?? uplinks

DRAFT
Confidential

HLD VF-MAN-Refresh v0 6

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

HLD VF-MAN-Refresh v0 6

Caricato da

Copyright:

Formati disponibili

VF MAN Refresh

1 © Nokia 2018 Confidential

2 © Nokia 2018 Confidential

3 © Nokia 2018 Confidential

5. RNA terminate L2 & L3 services. NxRNP*

4 © Nokia 2018 Confidential

Most of the services are Ethernet based (FE/GE/10GE).

6 © Nokia 2018 Confidential

Point to Point (EPIPE)

Multipoint to Multipoint (VPLS)

7 © Nokia 2018 Confidential

0.0.0.0/0 @IP Servicios Internet CE

Only present in 2 RNA

8 © Nokia 2018 Confidential

VRRP + Hair-pinning Multimedia Stinger

CE DSLA RNP RNA @IP Svc Multimedia

9 © Nokia 2018 Confidential

Main services Local VPLS

6. HFC Residential VoD service using VPLS (VEO)

Local VPLS on other MANs

VPLS VPLS VPLS VPLS HFC network

Madrid & Barcelona Distributed VPLS on other MANs

10 © Nokia 2018 Confidential

11 © Nokia 2018 Confidential

Test CPM3 / CPM4 CPM5 Comments

12 © Nokia 2018 Confidential

SF/CPM 2* SF/CPM 3 SF/CPM 4 SF/CPM 5

13 © Nokia 2018 Confidential

14 © Nokia 2018 Confidential

• Class-leading GE and10GE density for a range of oversubscribed scenarios

15 © Nokia 2018 Confidential

• Power Supply Units (PSU)

• Some RNA have additional limited license:

16 © Nokia 2018 Confidential

• 7210SAS-Sx as port extension of 7750 SR7/12/a8.

• Satellite automatically discovered and provisioned

17 © Nokia 2018 Confidential

IMPORT BASED IMPORT BASED

SUBMIT BEST SUBMIT BEST

18 © Nokia 2018 Confidential

20 © Nokia 2018 Confidential

22 © Nokia 2018 Confidential

23 © Nokia 2018 Confidential

To be completed if needed during testing…

24 © Nokia 2018 Confidential

25 © Nokia 2018 Confidential

All connections to same RNP on IOM x IOM x

SPLIT (If possible) IOM 1

All Network connections MUST be created using LAGs

SPLIT each CORE on

All Network connections MUST be created using LAGs

SATELLITE 4x10GE Uplinks

• Hair-pinning: RNA/RNP Initially only 2x10GE deployed, uplinks 49

28 © Nokia 2018 Confidential

10–port 10GE MDA-a XP

2-port 10GE + 12-port GE MDA-a

22-port 1GE SFP MDA-a

31 © Nokia 2018 Confidential

32 © Nokia 2018 Confidential

33 © Nokia 2018 Confidential

Interim metric N-1

34 © Nokia 2018 Confidential

If LAG (or Nx connections) it is possible