Professional Documents
Culture Documents
MotorolaConfidentialRestrictedPage1
Date8/12/2009
Revision History
Revision
Date
Author
Description
R00.00.01
10/31/09
YuMei
Bennett
Initial Release
MotorolaConfidentialRestrictedPage2
Date8/12/2009
Content
Background
Project Assumptions
Scope
Solution Description
Solution Assumptions
System IP Network Design
Middleware Functions
Application Considerations
MotorolaConfidentialRestrictedPage3
Date8/12/2009
Background
POC current platform is reaching end of life
P4 NMHOST EOL 2008, project to replace it with Xeon server is in
progress.
SanNet II RAID EOL Sep. 2009, selection of next generation SAS
RAID is on going.
CPCI chassis EOL June 2009, the main objective of this project.
POC current SW
OS Linux kernel (2.2) is out-dated
OS package is home grow, no clear middleware package
separation
Employ application level redundancy as well as board level
redundancy
MotorolaConfidentialRestrictedPage4
Date8/12/2009
Background
Evaluation of HW platform have resulted 3 options
HP DL 380 2U server with 2 Nehalem quad core cpu
Emerson c2000 3U ATCA chassis, capable of 2 ATCA payload
blades. Each blade have 2 Nehalem quad core cpu
Emerson 1440 13U 14 slot ATCA chassis, 2 slot for IP switches and
12 slot for ATCA payload blade. Each blade have 2 Nehalem quad
core cpu.
SW Strategies
Clear middleware package
Linux kernel upgrade to 2.6
Go to commercially supported OS distributions.
MotorolaConfidentialRestrictedPage5
Date8/12/2009
Background
Three High Level Solution Approach
HW
OS
Middleware
Solution A
HP DL380
RedHat
CCP
Solution B
Emerson
c2000
WindRiver
Open SAF
Solution C
Emerson
1440
WindRiver
Avantellis
MotorolaConfidentialRestrictedPage6
Date8/12/2009
Scope
This HSLA is about solution A!
As the first step, define one system option that has
Simple configuration
Least effort
Enable the ability to produce effort estimate quickly to different
configurations, including SE, dev, CCP, NPI and test
MotorolaConfidentialRestrictedPage7
Date8/12/2009
Scope
Existing Control Switch
HOW?
Ret
ain
CPCI Chassis
Replace
DL 380 G6
MotorolaConfidentialRestrictedPage8
Date8/12/2009
Project Assumptions
This is only for CS next gen
M3 target is 1H 2011
NMHOST and RAID SW architecture stay as it is to minimize the
effort size
Xeon NMHOST is required and only required for Next Gen. The
effort to migrate CS NMHOST is NOT part of this HLSA!
SAS RAID is required and only required for Next Gen. The effort to
migrate CS SCSI RAID to SAS RAID is NOT part of this HLSA!
Final HW will be same DL 380 model but with newer dual six core
westmere cpu which is only available in mid 2010
MotorolaConfidentialRestrictedPage9
Date8/12/2009
Solution Description
Double DL 380 G6 server replace current 21 slot CPCI
chassis
DL 380 G6 is a 2U rack mount server with dual quad core cpu,
24GB RAM
8 Ethernet ports with one 4 ports NIC extension card
2 72GB HDD
MotorolaConfidentialRestrictedPage10
Date8/12/2009
Solution Description
CurrentcPCI
RAID
NMHOST01
NMHOST02
Custer
service
Customer Edge
Switch/Router
RAINLINK
Customer
IP Network
Customer Edge
Switch/Router
ZNYX2
ZNYX1
VRRP
MotorolaConfidentialRestrictedPage11
....
cPCI Chassis
Date8/12/2009
Solution Description
RAID
NMHOST01
Customer Edge
Switch/Router
Customer
IP Network
Customer Edge
Switch/Router
Custer
service
NMHOST02
MeshredundantIPconnections
between4boxes
NoIPswitch/router
HP DL 380
MotorolaConfidentialRestrictedPage12
HP DL 380
Date8/12/2009
Solution Assumptions
RedHat Enterprise 5 running on DL 380
CCP team provides middleware for DL 380 only
No IP switch, mesh connection between all system IP
capable elements.
DL380 will boot from local drive, unlike CPCI cpu cards net
boot from NMHOST/RAID
SNMP functionality will be the responsibility of application
layer for both client and agent. Alarms and state change
events will be sent to NMHOST by application
Associated customer documentation need to be updated per
next gen design
MotorolaConfidentialRestrictedPage13
Date8/12/2009
MotorolaConfidentialRestrictedPage14
Date8/12/2009
VLAN
subnet name
Zhp#
(VLAN)
Switches
Ports
IP Subnet
VRRP
Private
Zhp0
Znyx
1-20
192.168.chid.0/24
192.168.0.252
Management
Zhp1
Znyx/customer
switch/Nmhost
/IPMH
21
Customer provides
(typical 10.x)
m.m.m.252
Mobile
Zhp2
Znyx/MRS/IPMH
customer switch
22
s.s.s.252
RAINLINK
Zhp99
23
10.254.254.0/24
10.254.254.252
MotorolaConfidentialRestrictedPage15
Date8/12/2009
SAS
1
Edge Switch
Customer
IP Network
Edge Switch
3
1
9
2
0
2
1
2
2
1
9
2
0
2
1
2
2
ZNYX02
ZNYX01
NMHOST01
3
cPCI
Chassis
RAID
3
NMHOST02
1
SAS
19NMHOST01;private192.168.0.0/24
20NMHOST02;private192.168.0.0/24
21ManagementandinterCS/ADtraffic;m.m.m.0/24
22Mobilesignalingandmedia;s.s.s.0/24
MotorolaConfidentialRestrictedPage16
Date8/12/2009
System
Element
Ports
IP Subnet
Inter-NMHOST
Private LAN
NMHOST
NMHOST
4-5
192.168.10.0/24
InterDL380
PrivateLAN
DL380
DL380
78
192.168.20.0/24
DL380andNMHOST
PrivateLAN
DL380
NMHOST
NMHOST23
DL38056
192.168.0.0/24
InterCS<>AD
PublicLAN
DL380
CustomerEquipment
DL380
34
Customer provides
i.i.i.0/24
Customer provides
Ex. i.i.i.252
Management
Public LAN
NMHOST
Customer Equipment
NMHOST
1&6
Customer provides
m.m.m.0/24
Customer provides
Ex. m.m.m.252
Mobile
Public LAN
DL380
Customer Equipment
DL380
1-2
Customer provides
s.s.s.0/24
Customer provides
Ex. s.s.s.252
MotorolaConfidentialRestrictedPage17
Floating public IP
Date8/12/2009
Management
CS/AD traffic
Signaling and Media
5
RAID
5
4
6
DL380
(CS-2)
3
SAS
NMHOST1
2
CS/AD traffic
DL380
(CS-1)
Private
Private
Private
5
4
CS/AD traffic
Private
NMHOST2
SAS
CS/AD traffic
Signaling and Media
Customer Router 2
Customer
IP Network
MotorolaConfidentialRestrictedPage18
Date8/12/2009
DL380 CS01 Ethernet ports 1 and 2 are bonded together Signaling and Media traffic.
DL380 CS01 Ethernet ports 2 and 3 are bonded together CS/AD traffic.
DL380 CS02 Ethernet ports 1 and 2 are bonded together Signaling and Media traffic.
DL380 CS02 Ethernet ports 2 and 3 are bonded together CS/AD traffic.
Xeon NMHOST01 Ethernet port 1 and 6 are bonded together - customer O&M traffic
Xeon NMHOST02 Ethernet port 1 and 6 are bonded together - customer O&M traffic
4 internal IP connections
DL380 CS01 Ethernet ports 5 and 6 bridged/bonded together for connection to NMHOST pair
DL380 CS02 Ethernet ports 5 and 6 bridged/bonded together for connection to NMHOST pair
DL380 Port 7 and 8 are bonded together for inter-DL380 communications.
NMHOST Port 3&4 are bonded together for inter NMHOST traffics
11 IP addresses need to be provided by customer, 6 for bonded connections and 3 for logical floating IP for
mobile, inter CS/AD and system O&M traffics. Two for MRS NAT IP that lives on each DL380.
Port bonding and bridging are used to bond multiple ports towards the same destination with single physical IP
to provide link level redundancy
Logical floating IP will be used to provide redundancy for all customer visible traffics.
CCP middleware will perform physical layer monitoring on all DL380 Ethernet ports.
8 Ethernet ports required on DL 380 and 6 Ethernet ports required on NMHOST.
IPMH management traffic (inter CS <-> AD), today it is going through Znyx on the same public IP VLAN with
NMHOST management traffic. Now it will have its own public LAN connection towards customer IP equipment.
IPMH CS/AD traffic will go through separate port on DL 380
Adds inter-NMHOST, inter-DL380 and NMHOST-DL380 connections, sits on a separate private VLAN. There will
be some NMHOST SW impact.
For communication between NMHOST and DL380, if direct link between two communication end point is down,
then the traffic will be re-routed through its peer box and inter-box links. This was done through Znyx switch
pair today, no re-routing through app box needed.
MotorolaConfidentialRestrictedPage19
Date8/12/2009
Middleware Functions
Assume all hardware monitoring of DL380 will be done by middleware layer (CCP).
Middleware layer will use openHPI for hardware monitoring. For devices that cannot be monitored using OpenHPI like
Ethernet ports, file system utilization, CCP will use other methods to monitor those devices.
Application need to register with middleware layer to receive hardware state change notifications
CPU and memory utilization monitoring will be done by APP team.
Two disk drives running as RAID1 internal to DL380 transparent to the application
MotorolaConfidentialRestrictedPage20
Date8/12/2009
Middleware Functions
Watchdog timer will be configured by CCP. Watchdog timeout will cause system
reboot and dump of kernel memory will be collected before reboot.
ccpsnap (collection of debug info)
Utility used to collect/gather debug info. Configuration of this utility can be
updated to collect app debug data. Can also be integrated with app if app has
a similar utility.
MotorolaConfidentialRestrictedPage21
Date8/12/2009
DL380 will NOT perform net boot like cPCI payload cards. All SW packages including OS, middleware
and OAMP all stored locally
Provide MOP for DL380 scratch installation and field upgrade
Firmware upgrades method of procedures
Two disk drives running RAID1 internal to DL380 transparent to the application
Port towards NMHOST will be bond/bridged as active/active. (NMHOST have functional division, normally both active.
App process knows the virtual destination IP depends on the type and function of the messages.)
Port towards customer network will be bond as active/standby
MotorolaConfidentialRestrictedPage22
Date8/12/2009
Redundancy Scheme
No change to NMHOST
Two DL380 will function in load sharing mode in normal condition, failover to either single box
when necessary
The backup for the CCSW, ADHLR and IPMH on one DL380 will be on the other
When one DL380 fails, the other one will only have actives running without any backups until the
failed DL380 back in service
MRS apps have no backups, there will be equal number of MRS apps on each of the DL380s.
There will not be any movement of MRS from one DL380 to another on hardware failure.
The number of MRS on each DL380 should be such that they can take the entire call load when one
DL380 fails.
MotorolaConfidentialRestrictedPage23
Date8/12/2009
MotorolaConfidentialRestrictedPage24
Date8/12/2009