Platform IPv6 Support for NetAct
Jed Ingking, Nanda BR
Version 1.6 [DRAFT]
Last Update: 20.06.2016
https://sharenet-ims.int.net.nokia.com/Overview/D532433887
Reviewers : Olli Lyytikainen, Frantisek Kelemen, Jukka Niiranen, Tommi Patrikainen.
1
© Nokia Solutions and Networks 2014
Version History
2
Date
Version
Owner
Reviewers
Change
20-06-2016
1.6
Nanda BR
DRAFT
Added slides depicting current IPv6 Support capability in NetAct , NetAct Cloud Customer Interests and updated
roadmap slide
19.05.2016
1.5
Jed Ingking
DRAFT
Customer Interest: Reliance Customer (Core) and Upgrade Paths.
22.02.2016
1.4.2
Jed Ingking
Reviewed.
Customer Interest: Verizon plans to take LTE IPv6 with new installations. (added alternate view).
04.02.2016
1.4.1
Jed Ingking
Pending
Customer Interest: Verizon plans to take LTE IPv6 with new installations.
02.02.2016
1.4
Jed Ingking
Pending
2016 Target:
NetAct Cloud IPv6 Support
LTE17 IPv6 General Availability
Verizon Core Support
26.08.2015
1.3
Jed Ingking
Olli Lyytikainen, Jukka
Niiranen, Frantisek
Kelemen,
NA16.5:
Replaced Standardized NAT solution with Verizon specific FC.
Verizon Specific FC to be owned in Core.
NA16.8:
Align with LTE IPv6 general availability.
NA17:
Platform fully ready for dual-stack IPv6 support. The rest aligns depending on NE IPv6 schedules.
16.07.2015
1.2
Jed Ingking
Pending
Replaced Standardized NAT solution FC with Verizon specific FC.
26.06.2015
1.1
Jed Ingking
10.06.2015
1.0
Jed Ingking
Consider pulling back full native IPv6 support in NA16.8.
Working copy added.
Olli, Jukka
© Nokia Solutions and Networks 2014
First version
Background
Rationale for IPv6 Support in NetAct:
- Limited IPv4 addresses available as network expands (no new IPv4 addresses from regional internet
registries. With hundreds of NEs to be deployed, IPv6 provides the necessary address space to support that.
- Compatibility with IPv6-only networks according to operators policies.
- Future-proofing NetAct with latest network protocols.
Customer Request:
- OSS_FR_002411 – Complete IPv6 support on all interfaces (internal and external).
Why phase the implementation ?
- OSS_FC_012907: Original scope full NetAct Native IPv6 support is not realistic to be done in 1 release (3
Mini Release). At least 12 MRs needed for complete solution.
- Get something done and delivered to customer with quality inside 1 release.
- Solution in each phase contributes to ultimate target of having native IPv6 support in NetAct.
3
© Nokia Solutions and Networks 2014
DRAFT
Customer Interests – RED = new info
1
2
Customer
IPv6 NE
NetAct
Release
Interest Level
Point of Contact
Verizon
Wireless
IMS and
SDM
NetAct 8 EP1
Verizon has an existing IPv6 deployment and it is absolutely must for any
continued business with them
frantisek.kelemen@nokia.co
m
One-AAA,
One-NDS,
NT HLR,
HSS FE,
CSCF,
TIAMS
Tier-1
NBI
NetAct 17.2
NetAct for Core uses Upgrade with NZDT. Systems would be upgraded from NA
16.2 level
NA Cloud 17.2 is required for lab delivery
LTE
NetAct 17.2
Standard Upgrade support for LTE IPv6 Support and Tier-1/NBI
Systems might be upgraded from NA 16.5
LTE955
NetAct Cloud
16.2
Critical/Mandatory requirement. LTE eNB needs to use IPv6 for the management
connection. Current target release NetAct 16,2 and FDD-LTE 16. There is no
strict IPv6 requirement overall (NBI/SBI) for NetAct, only eNB m-plane.
AT&T
Release was
not taken by
AT&T
4
LTE16A,
LTE 17
NetAct 16.8
and NetAct
17.2
AT&T will start with standard NetAct delivery.
LTE 16A will use NA 16.8 : Upgrade is from NA 16.2 to NA 16.8: Live Trial
deployment ; IPv6 support in SBI is sufficient
LTE 17 will use NA 17.2 : Upgrade is from NA 16.2 to NA 17.2: Live [Tier1 ,
SBI] . Both Install & Upgrade cases are there
LTE 17A
[LTE2957]
NetAct 17.8
Check if migration support is required
Pure IPv6 NE. No migration usecase
© Nokia Solutions and Networks 2014
jukka.niiranen@nokia.com
huijuan.li@nokia.com
jukka.niiranen@nokia.com
huijuan.li@nokia.com
DRAFT
Customer Interests – RED = new info
5
Customer
IPv6 NE
NetAct
Release
Interest Level
Point of Contact
3
Reliance
IMS and
HSS
NetAct 17.5
Required IPv6 in NA15.5, fallback to IPv4-only but customer is following
closely our roadmap.
frantisek.kelemen@nokia.com
savita.sharma@nokia.com
ari.kukkonen@nokia.com
jawahar.m@nokia.com
4
DTAG
and ARIS
Thailand
MGW
Release 17
NetAct 17.5
Was requested in MGW 16.5
2 LoA: DTAG and ARIS Thailand
New FC to be created for NA 17.5
chris.1.wang@nokia.com
5
-
Open BGW
NetAct 17.5
BGW supports IPv6. Request was at 16.5 level
New FC to be created for NA 17.5
xiaofeng.wang@nokia.com
ari.kukkonen@nokia.com
6
-
Open TAS
UTAS
NetAct 17.5
New FC to be created for NA 17.5
xiaofeng.wang@nokia.com
ari.kukkonen@nokia.com
7
-
GSM 18 and
GSM-R
NetAct18
8
DTAG
SRAN 17A
NetAct 17.8
© Nokia Solutions and Networks 2014
vivian.ma@nokia.com
javen.li@nokia.com
ivy.1.wang@nokia.com
sami.jalonen@nokia.com
NetAct Cloud Customer Interests
6
Customer
IPv6 NE
NetAct
Release
Open Stack variant and Interest Level
Point of Contact
1
AT&T
LTE
NA Cloud
17.2
[Lab Delivery]
Mirantis OpenStack
tommi.patrikainen@nokia.com
przemyslaw.szufarski@nokia.com
2
Verizon
Core and
LTE
NetAct Cloud
17.2
RedHat OpenStack
3
Tele2
IMS and
HSS
NetAct Cloud
17.2/17.5?
Canonical Ubuntu . Discussion ongoing if Dual Stack is required
Meeting with Tele2 in August
© Nokia Solutions and Networks 2014
For Internal Use Only – Not for Customer Communications or Commitments
NetAct Platform IPv6 Roadmap
NetAct Platform Path towards Dual-Stack Native Support
NetAct 18
NetAct Cloud 18
NetAct 17.5
NetAct Cloud 17.5
NetAct 16.8
NetAct 17.8
NetAct Cloud 17.8
OSS_FC_015438:NE_Radio_
GSM: GSM 18 Management
Functionality
OSS_FC_012907: Sys_CPf: Dual Stack support in NetAct
Platform
OSS_FC_015538 NE_Radio_LTE: FDD-LTE 17A
Management Functionality
NetAct 17.2
NetAct Cloud 17.2
NetAct 16.5
OSS_FC_014466: NE_Core: Native Dual Stack Support for Verizon
Platform + IPv6 Management for Core, LTE ,Tier-1, NBI, DR
for Verizon
OSS_FC_015347: Sys_Cloud&DC: NAC VNFM #1: Deployment with
Heat Orchestaration Templates (HOT)
NetAct 16.2
NetAct 8 EP1
7
OSS_FC_013863: NE_Radio:IPv6 for LTE
management plane (LTE955)
for AT&T
NAT Based Solution
for Verizon © Nokia Solutions and Networks 2014
Open for Integration VS to create IPv6
Management Feature Components
Solution Available
Under Planning
NetAct 8 EP1 to NetAct 15.5 [Verizon]
NetAct IPv4-only stack with customized optional NAT64 for Verizon Only.
NAT converts incoming IPv6 connections into IPv4.
OSS_FC_011274
NetAct 8 Support for IPv6
element management
Solution:
2 Extra HP Gen9 blade servers
Juniper NAT Software – 2 licenses
Core Integration Instructions
Interfaces:
- Tier-1
- NBI
- SBI (Core elements)
Performance qualified for Verizon Core elements
Customer : VERIZON WIRELESS
8
© Nokia Solutions and Networks 2014
NetAct 16.2 [IPv6 for LTE Management]
Introduction of NetAct dual-stack IPv4/IPv6 deployed via scratch installation only.
NetAct dual-stack provides support for LTE IPv6 management plane.
OSS_FC_013863
NE_Radio:IPv6 for LTE
management plane (LTE955)
Solution:
NetAct native dual-stack on LTE mediations, applications and platform.
Interfaces:
- SBI – LTE Radio
Performance qualified for LTE IPv6 support
Customer: AT&T
9
© Nokia Solutions and Networks 2014
NetAct 17.2 [IPv6 Support for Verizon: Core, LTE]
Migration of Verizon NAT64 Solution to NetAct native dual-stack support.
Dual Stack support in Platform components [DB,DNS.NTP,vCenter,EXSi]
DR Solution supports IPv6 addressing
Solution:
NetAct native dual-stack on LTE mediations, applications and platform used by Verizon.
Migration Procedure from NAT64 solution to native dual-stack support [Under Discussion]
Primary Path: Upgrade with Cloning: IPv4  IPv4/IPv6.
OSS_FC_014466: NE_Core:
Native Dual Stack Support
for Verizon
Interfaces:
- Support for NEs: One-AAA, One-NDS, NT HLR, HSS FE, CSCF, TIAMS
- User Access (Tier1) Support, Node Manager[Installation needed]
- NB interface support for SNMP FM, 3GPP Corba PM, TMF-615
- NE3SWS, HPHW,3GPP PM,SNMP NBI mediations support dual stack
Performance verification in Tier-1, NBI and SBI-Core.
Customer: VERIZON WIRELESS
10
© Nokia Solutions and Networks 2014
NetAct 17.8 / NetAct Cloud 17.8
NetAct platform dual-stack support ready
Available for all deployment variants
Available for both bundled and SW-only deliveries
Solution:
Complete dual stack solution in NetAct Platform
Example: OSI, VDP, Perl , NFS, Resolver, VSE CLI and Installer, HPSIM, IPTables,Storages(HP2040 and HP MSA2000)
NAT Removal
NetAct IPv6 Security requirements are addressed
Node Manager IPv6 support in Upgrade usecase
Verizon NAT Removal for Radio Network
NWI3 NE Re-registration
OSS_FC_012907 Sys_CPf: Dual
Stack support in NetAct Platform &
Interfaces required for Radio
Element Management
AT&T LTE Requirement:
External interfaces are capable to communicate over IPv6 address
Mediations:
NWI3 SBI[LTE]
NE3SWS SBI[Small Cells controller]
3GPP FM NBI
BCM Corba NBI
3GPP CORBA Bulk CM NBI
XML Based Inventory Data Export
Optional Nodes:
CLS
SLC
Node Manager
Internal Communication also to use IPv6 address : Under clarification
Performance qualified
11
Customer:
© Nokia Solutions and Networks
2014World Wide
NetAct 18 and future
NetAct platform native dual-stack support ready.
Available for all deployment variants
Available for both bundled and SW-only deliveries
OSS_FC_015438:
NE_Radio_GSM: GSM 18
Management Functionality
DRAFT
Solution:
Complete native dual stack solution.
Interfaces:
All external interfaces to GSM 18
Customer: GSM Worldwide
Removal of NAT FC
In case not part of OSS_FC_012907 or Verizon Core.
Enabling dual-stack support
outside upgrades.
Might be used for migration cases where shift to dual-stack is done outside upgrade
No demand yet
IPv6 Only Installation
Internal Communication also using IPv6
12
© Nokia Solutions and Networks 2014
Target and Proposal for Requirement Handling
Target
•
Platform is dual-stack ready
•
All NetAct external interfaces is capable to communicate over IPv6
•
Internal Communication can still use IPv4. No customer request yet to have internal communication also over IPv6
Note: Requirements from NA 17.2 onwards should cover NetAct Standard and Cloud variants and all deployment types
Proposal for handling Open TAS, Open BGW, SRAN IPv6 requirements:
•
Open TAS, Open BGW: Integration VS to create FC for NA 17.5
•
SRAN: Integration VS to create FC for NA 17.8
Proposal for handling post NA 17.8 IPv6 requirements
•
13
Integration VS to own the requirement taking into consideration all required interfaces,applications and optional nodes
© Nokia Solutions and Networks 2014
14
© Nokia Solutions and Networks 2014
NetAct upgrade paths
NetAct 15.5
MP1
NetAct 15.2
NetAct 15.5
NetAct 15.5
MP2
NetAct 16.2
NetAct 15.5
MP3
NetAct 16.5
NetAct 15.5
MP4
NetAct 16.8
NetAct 16.8
MP1
NetAct 17.2
NetAct 16.8
MP2
NetAct 16.8
MP3
NetAct 17.5
NetAct 17.8
NetAct 18
IPv4 to IPv4
NAT Based
IPV6 Support
15
© Nokia Solutions and Networks 2014
Dual Stack Support
LTE SBI
Dual Stack Support
Platform,
SBI for Verizon Core & LTE,
Tier1 and NBI
IPv4 to IPv4
Dual Stack to Dual Stack
Dual Stack
Support
IPv4 to IPv4
Dual Stack to Dual Stack
IPv4 to Dual Stack
Not known
Hardware
Active Switches , Routers
HP VC
Flex10/10D
HP C7000 OA
Yes
No
Legacy Switches
HP 5900
HP 5500
Cisco 2951
[Router for
OSI]
HP 5100
Cisco 3020
HP 2810
Cisco
3750
Servers
Device Bays
[Blade ILO]
Inter
connect Bays [SAN Switch][17.2]
Storages
HP EVA
16
HP3PAR
EMC
VNX
[17.2]
© Nokia Solutions and Networks 2014
HP
P2040
HP
MSA2000
Partial
Platform IPv6 Support Summary [NetAct Standard]
JACORB
TOMCAT
HPSIM
OSI
DNS
[17.2]
Not known
Yes
No
OEM
DB
[17.2]
Perl
WAS
SOCKS
proxy
Resolver
Hosts
SSH
LB
LDAP
LDAPS
NTP
[17.2]
FTP
SFTP
SCP
HTTP
HTTPS
IPTABLES
VSE
Installer
VSE CLI
NFS
OS
VDP
Virtual Layer
17
vCenter
[17.2]
© Nokia Solutions
ESXi and Networks 2014
[17.2]
Servers
Partial
Not known
South Bound Mediations
18
NE3SWS
[17.2]
NX2S
XOH
Flexi NS
FTP
SAU
HPHW
[17.2]
NWI3
Q3
MML
Juniper
SCLI
PNP Server
SNMP PM
SNMP FM
FTP PM
Corba FM
© Nokia Solutions and Networks 2014
Yes
No
Partial
Not known
North Bound Mediations
3GPP XML
PM
[17.2]
19
SNMP NBI
[17.2]
3GPP FM
BCM
Corba NBI
3GPP CORBA Bulk CM
Northbound Interface
CM Operations Web Service
API
CM Data Repository Web
Service API
CSV Interface for
Configuration Management
Data
E-mail Alarm Forwarding
OSS/J Trouble Ticket Client
TMF 615 User Management
© Nokia Solutions and Networks 2014
Yes
No
XML Based Inventory
Data Export
XML Interface for Configuration
Management Data
SLNBI
Partial
Not known
Applications
Adaptation
Manager
CM Reference
AOM
Alarms Reports
Dashboard
CM Rule Editor
CM Analyzer
Dynamic Adaptation
Certificate
Authority[17.2]
[172]
HP Insight Manager
Intelligent Feature Activation
Monitor
NE Integration
Wizard
NEAC
Performance
Manager[17.2]
SON Scheduler
Site Configuration Tool
20
SWM
[17.2]
CM Editor
License Manager
MSC Server Pool
Monitor
Operating
Documentation
OIB
SWAM
© Nokia Solutions and Networks 2014
System Monitoring
Traceviewer
[17.2]
User Management
Yes
CM Operations
Manager
Flexible CM Search
Map Administrator
Optimizer
Working Set Manager
No
Partial
Not
known
Optional Nodes & Solutions
Nodes
21
CAM
T&P
[17.2]
Node
Manager
[17.2,
Insatll]
SLC
CNBI
SBTS
Adapter
Admin
Server
[17.2]
CLS
Postgres
DB
Portal:
Tomcat
Backend:
Jboss
Map:
Apache
© Nokia Solutions and Networks 2014
Yes
No
Partial
Technology License based South Bound Mediation Dual Stack Support View
Radio
Core
Transport & Others
Yes
22
© Nokia Solutions and Networks 2014
No
Partial
Working In Progress
Information
Review Date: 23.02.2016
23
© Nokia Solutions and Networks 2014
<Change information classification in footer>
vCenter supports only either
IPv4-only or IPv6-only but not
both.
Open Points
Verizon LTE deal options :
1. Dual-stack support only for LTE. Partial
Tier-1 dual-stack support. NBI remains
IPv4-only.
•
Verification effort only.
2.
New Release
Guidelines to avoid
system features in .2
release ?
Tier-1 and NBI dual-stack support in
scratch install.
16.5 On-top Feature PP ?
DSS, NASS, NBI, NeVe, PeT
•
•
3.
•
CAM IPv6
Support ?
NetAct 8 EP1
Dual-Stack Native Support for LTE
(LTE17) – upgrades
Dual-Stack Native Support for
Core / Verizon
Dual-Stack Native Support for LTE
– NetAct Cloud / AT&T
Dual-Stack Native Support for LTE + Tier-1
+ NBI – scratch install / Verizon
Dual-Stack Native Support for
LTE (LTE955) – scratch install.
Verizon Path for Core Systems
NAT Based Solution for Verizon
24
© Nokia Solutions and Networks 2014
<Change information classification in footer>
Full Dual Stack
Native Support
NetAct 17
NetAct Cloud 16.8
NetAct 16.5
NetAct 16.2
NetAct 17.2
AT&T LTE
IPv6
requirement in
NetAct
Cloud16.8 ?
Dual-stack support only for LTE paths.
Tier-1 and NBI behind NAT. (Not
preferred).
Updates to customized NAT solution
(Documentation). DSS, NASS, NBI
NetAct 17.5
NetAct Cloud 17.5
Next Steps / Support Request.
• NetAct IPv6 support hinges on Verizon Core FC to be completed in NetAct17
with need for special release for Verizon LTE earlier.
- Business Case: Verizon LTE deal, Continued business with Verizon, LTE IPv6 General Availability.
- Prioritization: Verizon Core FC GP is high enough and request that it stays that way.
• Start the work !
- Engage program (Nasar, Anila) and Lead VS for options to get this feature out.
- Nominate Feature Lead, Feature Architect from Core Integrations, Architect from DSS
(CPf+IUM), NBI and NASS VS (to refresh pre-studies), System Architect to approve study.
- Prioritize Verizon LTE IPv6 support as first target/milestone.
25
© Nokia Solutions and Networks 2014
<Change information classification in footer>
Open Points
1.
Dual-Stack IPv4/IPv6 support in NetAct Cloud deliveries [OPEN]
-
OpenStack
•
-
VMWare
•
2.
Identified solution delta is Load Balancing uses NAT routing.
Assumption: Same as NetAct SW-only installations in cloudlabs with certain VI/HW related components disabled : vmanager, HP SIM, etc.
CAM which would deploy NetAct Cloud does not support IPv6. [OPEN]
-
3.
Is this required or is it sufficient that operationally NetAct Cloud interfaces (Tier-1, SBI, NBI) support dual-stack ?
Recently approved NetAct Program Guidelines (no system contents in NA17.2 and NA17.8 releases). [OPEN]
-
4.
For LTE17 (aligns with NA17.2, work need to be merged to NA17).
Dual-stack support in VMWare management plane [OPEN]
-
5.
Not available yet and no view from VMWare roadmaps. Currently, only available is to select either IPv4-only or IPv6-only and not both. Can
Verizon remain IPv4-only for this path ?
RHEL7 dependency [CLOSED]
-
Confirmed that dual-stack solution can proceed independent of RHEL7 introduction.
•
ATC could continue to deploy their own Perl version that supports dual-stack.
•
IP6 NAT Table workaround can continue to be used in succeeding releases.
26
© Nokia Solutions and Networks 2014
<Change information classification in footer>
NetAct Dual-Stack IPv4/IPv6 Pre-Studies
• OSS_FC_011274
NetAct 8 Support for IPv6 element management System-wide
-
Pre-Study: https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D483601590
-
CPF Pre-Study: https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D503108847
• OSS_FC_012907 Native IPv6 support
-
CPF Pre-Study: https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D522241024
-
Other Components Pre-Studies: https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D528956565
• OSS OSS_FC_013863 : NE_Radio:IPv6 for LTE management plane (LTE955)
•
Pre-Study: https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D533249341
•
CPF Pre-Study: https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D533020826
27
© Nokia Solutions and Networks 2014
<Change information classification in footer>
NE and Application IPv6 Support.
• Mediation/Application components align with their corresponding NEs for IPv6 support
-
OSS_FC_013863 : NE_Radio:IPv6 for LTE management plane (LTE955)
-
OSS_FC_014466: NE_Core: Native Dual Stack Support for Verizon
-
OSS_FC_013851:NE_Radio: FDD-LTE 16A Management Functionality
-
OSS_FC_013853:NE_Radio: TD-LTE 16A Management Functionality
-
OSS_FC_013724: NE_Radio: TD-LTE 17 Management Functionality
-
OSS_FC_013725: NE_Radio:FDD-LTE 17 Management Functionality
• Applications and Tier-1 interfaces are need to support dual-stack by NetAct 16.5  follows
release for OSS_FC_014466: NE_Core: Native Dual Stack Support for Verizon
- Need to be verified depending on customer requirements.
• All interfaces should be dual-stack compliant by NetAct 17.x
- Via scratch installation or via upgrade/upgrade with cloning
28
© Nokia Solutions and Networks 2014
<Change information classification in footer>
NAT Based Solution
• NAT Based Solution would be needed during transition to full IPv6 native support and
specifically for these case:
- IPv6 NEs whose corresponding NetAct components support only IPv4.
- IPv6 Tier-1 clients whose corresponding NetAct applications support only IPv4.
• Hence, depending on customer’s NE mix and Tier-1 setup, NAT may or may not be
needed for IPv6 support.
26.08.2015 Update:
• No customer so far has requested NAT based solution. Originally planned
standardized NAT is proposed skipped.
• Cost Savings: ~5000hrs R&D effort + 1 Juniper License + 1 Extra Blade Server
29
© Nokia Solutions and Networks 2014
<Change information classification in footer>
Old Slides – Not Valid beyond this
point anymore.
30
© Nokia Solutions and Networks 2014
<Change information classification in footer>
New Proposal
• NetAct 16.2
-
FC: LTE IPv6 m-plane support
Owner: Radio Integrations XL
•
Scratch Install on LTE Radio Data Path
• NetAct 16.5
-
FC: Native Dual Stack Support for Verizon
•
(~same size as LTE m-plane) Owner: Core Integrations
Scratch Install, Upgrade, NAT migrations, NAT Removal*
• NetAct 16.8
-
FC: LTE IPv6 General Availability
Owner: Radio Integrations L
•
Includes upgrade path from what’s missed in NA16.2
•
Remaining Platform Interfaces
• NetAct 17
-
FC: IPv6 native support
Owner: CPF
•
Platform dual-stack support like Perl and vSphere6.0 and HW Devices.
•
NAT Removal for Verizon (*in case not getting done in NA16.5)
31
© Nokia Solutions and Networks 2014
<Change
in footer>
- information
FC: NEclassification
create their
own FCs for IPv6 Support
Owner: Radio or Core Integrations.
L
XL
What is available to customers ?
• NetAct 16.2
-
LTE IPv6 m-plane support would be available only for new NetAct deployments (scratch installation, AT&T specific)
• NetAct 16.5
-
Upper NMS and Core NEs IPv6 support would be available for Verizon and others with similar profile
• NetAct 16.8
-
LTE IPv6 General availability / support for new and existing NetAct deployments
• NetAct 17
-
Remaining Tier-1 platform interfaces (vSphere webclient*, HW web UI*, HP SIM UI) support dual-stack
•
-
* Dependent on OEM vendor support; older versions may not provide dual-stack and may support either IPv4 or IPv6 only.
Verizon fully migrated from NAT to native support**
•
* * Tier-1 interfaces for certain OEM components to be reviewed.
-
vSphere 6.0 supports either IPv4-only or IPv6-only and IPv6 support looks experimental.
• NetAct 17.x
-
NEs aligns with their respective NE IPv6 schedules.
32
© Nokia Solutions and Networks 2014
<Change information classification in footer>
IPv6 Phase Overview
Solutions are built on to of previous one.
Release
NetAct 15.5 ----- CP=03/2015 C5=05/2015
NetAct 16.2 ----- CP=11/2015 C5=02/2016
FC ID
OSS_FC_011274 NetAct 8 Support for IPv6 element management
OSS_FC_013863 : NE_Radio:IPv6 for LTE management plane (LTE955)
Scope
IPv4 only stack with customized optional NAT64 for Verizon Only
1.
2.
Customers
Verizon
AT&T
Benefit
All interfaces (IPv6-only NEs, Tier-1 Client, Umbrella NMS) towards NetAct are
via customized NAT64.
1.
R&D Effort
Main Development Done.
Regression Testing (NeVe, PeT, CPF) every new release.
Radio Integrations, IUM, CPF, NeVe, PeT
L: 3MRs: ~3000hrs
Costs
Optional: 2 Juniper Licenses (3keur) + 2 extra blades
Risk
33
© Nokia Solutions and Networks 2014
<Change information classification in footer>
LTE m-plane IPv6 Native Support only*
Primary Path: Scratch Installation (Dual-Stack IPv4/IPv6)
Native IPv6 support for LTE management plane only.
* RHEL6 IP6tables NAT support lacking: fallback to WA
IPv6 Phase Overview
Solutions are built on to of previous one.
Release
NetAct 16.5 ----- CP=03/2016 C5=05/2016
NetAct 16.8 ----- CP=05/2016 C5=08/2016
FC ID
OSS_FC_014466: NE_Core: Native Dual Stack Support for Verizon
OSS_FC_013851:NE_Radio: FDD-LTE 16A Management Functionality
OSS_FC_013853:NE_Radio: TD-LTE 16A Management Functionality
Scope
1.
2.
3.
4.
5.
1.
2.
3.
Customers
Verizon
AT&T
All LTE IPv6 Customers (LTE IPv6 General Availability)
Benefit
Interfaces specifically used by Verizon provides native dual-stack IPv6 support
All LTE eNBs interfaces to NetAct support native dual-stack IPv6 support
R&D Effort
Core Integrations,CPF, IUM, OSS Integrations, CM, FM, PM, NeVe, PeT All.
XL: 4-6MRs: ~7000hrs
Radio Integrations, CPF, IUM, OSS Integrations, CM, FM, PM, NeVe, PeT, All.
XL: 4-6MRs: ~7000hrs
Support for NEs: One-AAA, One-NDS, NT HLR, HSS FE, CSCF, TIAMS
User Access (Tier1) Support: vSphere6.0* IPv6, Node Manager,
NB interface support for SNMP FM, 3GPP Corba PM, TMF-615
Migration Procedure from NAT64 solution to native dual-stack support
Primary Path: Upgrade with Cloning: IPv4  IPv4/IPv6.
Costs
Risk
* vSphere 6.0 brings only either IPv6 or IPv4 but not both.
34
© Nokia Solutions and Networks 2014
<Change information classification in footer>
New LTE eNB integrations can use IPv6.
Existing LTE eNB can continue to use IPv4.
Paths: Scratch Install (IPv4/IPv6) and Upgrade: IPv4  IPv4/IPv6.
IPv6 Phase Overview
Solutions are built on to of previous one.
Release
NetAct 17.x ----- CP=08/2016 C5=11/2016
NetAct 17.x
FC ID
OSS_FC_012907 Sys_CPf: IPv6 native support
LEFTOVERS
Scope
1.
2.
3.
4.
5.
SB Interfaces provides dual-stack IPv4/IPv6 native support.
NB Interfaces provides dual-stack IPv4/IPv6 native support.
User Acces/Tier-1 interface provides dual-stack IPv4/IPv6 native support
Platform fully supports dual-stack IPv4/IPv6 (Perl, vSphere, HW).
Paths: Scratch Install (IPv4/IPv6), Upgrade and Cloning Upgrade (IPv4 
IPv4/IPv6)
Customers
All
Benefit
All interfaces (SBI, NBI, Tier-1) support both IPv4 and IPv6 connections.
R&D Effort
Core Integrations, CPF, IUM, OSS Integrations, CM, FM, PM, NSS, All.
L: 3MRs: ~3000hrs
Costs
Risk
35
© Nokia Solutions and Networks 2014
<Change information classification in footer>
1.
2.
3.
4.
5.
-
Reintegration procedures for existing NEs from IPv4 to IPv6.
NetAct on OpenStack with Dual Stack IPv4/IPv6 support
Scaling Procedure with Dual Stack IPv4/IPv6 support
NetAct Cloud with Dual Stack IPv4/IPv6 support
NetAct DataCenter with Dual Stack IPv4/IPv6 support
Support Needs
1.
Priority of the IPv6 features at a level that all VS can start in the beginning of 1st MR every
release. (e.g. Part of Top10 and System Must-Haves). Not Done.
2.
Fully-allocated feature execution team to sort out all technical issues, dependencies and
implementation from NA16 to NA17.x. Not Done.
-
Work to start by MR15.05 for the pre-study for Load Balancer issue. Done.
-
1 Lead architect + 4 representatives from CPF + 1 technical representative from each VS beginning MR15.07.
3.
Attach platform IPv6 requirements that are needed by LTE IPv6 m-plane support in
OSS_FC_013863 (a higher priority FC). Done.
4.
Completion of Citrix XenApp 7.5 and Linux IPv6 support for HIT Tool in MR15.08/NA16.2.
On Track.
5.
RedHat support for IPv6 NAT forwarding and other OS IPv6 topics. WA Available.
36
© Nokia Solutions and Networks 2014
<Change information classification in footer>
05.08.2015 Workshop Goal
• Identify the right amount of split that is:
- Technically feasible
- Better chances of getting done in 1 release.
- Still have value for Verizon / other customers.
- Solutions are forward compatible
• End Target: NetAct is Dual-Stack ready.
37
© Nokia Solutions and Networks 2014
<Change information classification in footer>
38
© Nokia Solutions and Networks 2014