1 / 60

Nortel CS1000 Release 5.0 UPGRADES

2. Module Agenda Overview. Upgrade OverviewSupported UpgradesSoftware SimplificationUpgrade path overviewAllowed Upgrades and ExpansionsEnterprise Configurator and UpgradesOrderProMeridian 1 TDM UpgradesOption 11/11E/11COption 21/21E/51Option 51/51C/61/61C/71/81/81C. Meridian 1 to CS1000 I

gina
Download Presentation

Nortel CS1000 Release 5.0 UPGRADES

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. 1 Nortel CS1000 ? Release 5.0 UPGRADES Peter Vronsky Bell Canada

    2. 2 Module Agenda Overview Upgrade Overview Supported Upgrades Software Simplification Upgrade path overview Allowed Upgrades and Expansions Enterprise Configurator and Upgrades OrderPro Meridian 1 TDM Upgrades Option 11/11E/11C Option 21/21E/51 Option 51/51C/61/61C/71/81/81C Meridian 1 to CS1000 IP Upgrades Option 11C Option 11/11E Option 21/21E/51s Option 51/51C/61/61C/71/81/81C This is sample notes copy Keep notes clear and simple for easy reference Use as little text as possibleThis is sample notes copy Keep notes clear and simple for easy reference Use as little text as possible

    3. 3 Module Agenda Overview CS1000 Upgrades CS1000M Chassis and Cabinets CS1000S CS1000M SG and MG CS1000E Branch Upgrades MG1000B Upgrades MG1000B Supported Software Releases SRG and Release 5 Compatibility Applications Compatibility Enterprise Configuration Management Signaling Server considerations This is sample notes copy Keep notes clear and simple for easy reference Use as little text as possibleThis is sample notes copy Keep notes clear and simple for easy reference Use as little text as possible

    4. 4 Supported Upgrades All Meridian 1 and CS1000 systems can be upgraded to Release 5—hardware requirement vary by system type Some only require software upgrades Others require memory, Fiber Network Fabric or processor upgrades All CS1000 systems can now be optionally equipped with redundant hot standby CPUs—even small systems Meridian 1 systems with IP Line must be upgraded to CS1000, IP trunk is still supported on Meridian 1 Direct in-line software conversion is supported from Release 23 and higher If Telephony Manager is desired, it must be TM Release 3.1 for Concurrency with Release 5.0

    5. 5 Software Simplification

    6. 6 Upgrade Path Overview

    7. 7 Allowed Upgrades and Expansions Release 3 is Sustained, you can add TN’s and features to existing Release 3 systems. If customers do not upgrade to Release 5 they must stay on their current release, they can and should upgrade to the latest issue of that release All systems prior to Release 3 (including x11 R25 and older) are Retired or End of Life Upgrades can only be done to Release 5 Expansions require an upgrade to Release 5 first Systems on Release 25 and earlier require an OrderPro file to upgrade to Release 5 OrderPro recommended for all upgrades to populate site survey

    8. 8 Enterprise Configurator and Upgrades EC 7.x (7.1) is now available to quote upgrades to Release 5 and Release 4.5 expansions

    9. 9 OrderPro OrderPro is required for Release 25 and earlier systems to convert to the CVSD software structure OrderPro is recommended for all upgrades to assist in populating the site survey See the EC release notes for each release for the minimum OrderPro release required Log files can be extracted from earlier version of OrderPro, but may not have full site survey details

    10. 10 Meridian 1 System Upgrades TDM-to-TDM Upgrades

    11. 11 Meridian 1 Option 11/11E/11C Upgrades Option 11C has same Memory and processor vintage requirements as Release 4 and 4.5 except that the MSC (Mini System Controller) card (Option 11C Mini) must be replaced by an SSC (Small System Controller) Card Flash Memory Daughterboard requirements have not changed since Release 25, still 48 MB (NTTK13 or NTTK25) DRAM memory requirements have not changed since Release 4, still 32MB Option 11 and 11E systems upgraded to Release 5 become Option 11Cs

    12. 12 Legacy Option 11/11E Cabinets Main Cabinet NTAK11BB Option 11E Main cabinet (X11R 20-21) NTAK11BA Option 11 Main cabinet (X11R 16-18) Cabinets are compatible with Release 5 with a cabinet upgrade kit NTAK12 Expansion Cabinets Option 11 had 1 copper connected expansion cabinet maximum Option 11E had 2 fiber connected expansion cabinets maximum Expansion cabinets are not compatible with Release 5 and must be replaced

    13. 13 Option 11/11E Upgrade Software EC will provision the following parts: NTE960 System Option 11/11E Upgrade to Option 11C Contains the following: Main Security Device (Dongle) -Small System Nortel Communications Server 1000 Enterprise Multimedia Documentation CD NTSK01ADE5 SSC Programmed SW Daughterboard (Global) - Release 5.0 Small Systems Keycode The NTSK01ADE5 provides a 48MB Software Daughterboard pre-loaded with the Release 5 software load, this is the same as for a new Option 11C

    14. 14 Option 11/11E Hardware Upgrade Single Cabinet NTWB09HA Meridian 1 Option 11/11E Upgrade to a single cabinet 11C System Package NTBK48AAE6 3-Port SDI Cable NTDK18AA Kit Plastics Upgrade M1 Option 11C Cabinet NTDK20JA Small System Controller Card - 32MB NTDK27AA Cable 18 inch Option 11C Ethernet IO Adapter Provides a new SSC to replace the Option 11/11E CPU, and a cabinet upgrade kit (new door).

    15. 15 Option 11/11E Hardware Upgrade Two Cabinets NTWB09JA Meridian 1 Option 11/11E Upgrade to a two cabinet 11C System Package NTAK11BD Cabinet Option 11C NTBK48AAE6 3-Port SDI Cable NTDK18AA Kit Plastics Upgrade M1 Option 11C Cabinet NTDK20JA Small System Controller Card - 32MB NTDK27AA Cable 18 inch Option 11C Ethernet IO Adapter Provides a new SSC to replace the Option 11/11E CPU, a cabinet upgrade kit (new door) and a new expansion cabinet

    16. 16 Option 11/11E Hardware Upgrade Three Cabinets NTWB09KA Meridian 1 Option 11/11E Upgrade to a three cabinet 11C System Package 2 - NTAK11BD Cabinet Option 11C NTBK48AAE6 3-Port SDI Cable NTDK18AA Kit Plastics Upgrade M1 Option 11C Cabinet NTDK20JA Small System Controller Card - 32MB NTDK27AA Cable 18 inch Option 11C Ethernet IO Adapter Provides a new SSC to replace the Option 11/11E CPU, a cabinet upgrade kit (new door) and a two new expansion cabinets

    17. 17 Option 11C Upgrade Software Delivery Release 24 and below, Provision: NTSK01ADE5 SSC Programmed SW Daughterboard (Global) - Release 5.0 The NTSK01ADE5 provides a 48MB Software Daughterboard pre-loaded with the Release 5 software load, this is the same as Software Daughterboard that is equipped on a new Option 11C

    18. 18 Option 11C Upgrade Software Delivery Upgrades from Release 25+ two choices NTSK01ADE5 Option 11C Pre-programmed PCMCIA Card Loaded to the existing 48 MB Blank Software Daughter board by technician on site. Existing NTTK13 or NTTK25 Option 11C 48MB Blank Software Daughterboard N0140428 64MB Compact Flash with PCMCIA Adaptor (Blank) Less expensive Software downloaded from Web site on technicians PC and copied to Blank PCMCIA Memory Card, then loaded to the Daughter board on site. Existing NTTK13 or NTTK25 Option 11C 48MB Blank Software Daughterboard

    19. 19 SSC Memory Requirements M1 Option 11C Flash Memory Daughterboard requirements have not changed since Release 25—still 48 MB NTTK13 or NTTK25 NTTK13 Flash Memory Daughter boards look very much like the older NTDK81AA and use the same NTDK8101 base circuit card. Some technicians will try to replace them thinking they are the older cards Since there was an increased DRAM memory requirement (32MB vs. 16MB) with Release 4, most older installed base systems require DRAM memory upgrades Systems shipped since May 2004 are equipped with NTDK20HA or JA with 32 MB DRAM and are compatible Memory Upgrade kit (NTDK19BA) is available to upgrade DRAM SIMM on any SSC (except NTDK20AB or NTDK20CA Release 1-5) to 32 MB Because of the evolution of the NTDK20, simply adding the DRAM memory upgrade will not automatically convert any SSC into a NTDK20HA

    20. 20 SSC Upgrades or Replacements for M1 Older SSC Cards NTDK20AB and NTDK20CA Release 1-5 are not supported on Release 5 and must be replaced with a new NTDK20JA. NTDK20AB Release 1-5 cards were originally shipped with systems from August 1996 to May 1997. NTDK20CA cards are NTDK20AB cards upgraded to CA using the NTDK19AA SSC upgrade kit. For NTDK20AB/CA Release 6 and higher cards, Provision a NTDK19BA SSC upgrade kit which upgrades it to a CA vintage and 32MB of DRAM memory. Card vintage and release can only be determined by physical inspection.

    21. 21 Upgrades of Legacy Meridian 1 Option 21, 21E, 51 to Option 11C Cabinet The most economical upgrade path from any of these systems is to run a new Option 11C Cabinet quote. Put in all lines and analog trunks as “wired for” to reuse existing Analog trunk cards as well as Analog and Digital line cards Determine cards from Bay face Layout or OrderPro report Add new DTI/PRI cards, existing DTI/PRI cards are not compatible Add new CallPilot, existing Meridian Mail systems are not compatible.

    22. 22 Meridian 1 Option 51/51C/61/61C/71/81/81C Upgrades Option 61C/81C require CP-PII or CP-PIV processor Customers with CP3 (68060), CP4 (68060E) (which were supported on Release 4.5), or earlier must upgrade to CP-PIV Option 81C requires Fiber Network Fabric Option 51/51C/61 must upgrade to Option 61C with CP-PIV card cage upgrade Option 71/81 must upgrade to Option 81C with CP-PIV card cage and FNF (Fiber Network Fabric) upgrade

    23. 23 Meridian 1 to CS1000 Upgrades TDM-to-IP Upgrades

    24. 24 Upgrading a Meridian 1 Option 11C to a CS1000E IP System System becomes CS 1000E SA or HA Cabinet or Chassis SSC (Small System Controller) in main cabinet/chassis is replaced by a Media Gateway Controller (MGC) and new processor(s) added: One CP-PM Call Server for Standard Availability (SA) Two CP-PM Call Servers and Software Option 410 for High Availability (HA) Each additional Cabinet/Chassis requires a new Media Gateway Controller (MGC) with appropriate number of DSP Daughterboards Meridian Mail is not supported and CallPilot must be Release 3 or higher Contact Center Manager Server and Symposium Call Center Server “Controlled Broadcast” feature using CallPilot is not supported on CS1000E and must be converted to Broadcast RAN licenses and Integrated Recorded Announcement. Music on Hold/Delay using Conference packs must be converted to Broadcast Music licenses on CS1000E Add Signaling Server(s)—choice of In-Skin CP-PM HP/IBM COTS

    25. 25

    26. 26 Upgrading a Meridian 1 Option 11/11E to a CS1000E IP System System becomes CS 1000E SA or HA Cabinet SSC (Small System Controller) in main cabinet/chassis is replaced by a Media Gateway Controller (MGC) and new processor(s) added: One CP-PM Call Server for Standard Availability (SA) Two CP-PM Call Servers and Software Option 410 for High Availability (HA) Additional cabinets are replaced with new MG1000Es Meridian Mail is not supported Contact Center Manager Server and Symposium Call Center Server “Controlled Broadcast” feature using CallPilot is not supported on CS1000E and must be converted to Broadcast RAN licenses and Integrated Recorded Announcement. Music on Hold/Delay using Conference packs must be converted to Broadcast Music licenses on CS1000E Add Signaling Server(s), choice of In-Skin CP-PM HP/IBM COTS

    27. 27

    28. 28

    29. 29

    30. 30

    31. 31

    32. 32 Upgrading a Legacy Meridian 1 Option 21, 21E, 51 to a CS1000E IP System The most economical upgrade path from any of these systems is to run a new CS1000E quote. Put in all lines and analog trunks as “wired for” to reuse existing Analog trunk cards as well as Analog and Digital line cards Determine cards from Bay face Layout or OrderPro report Add new DTI/PRI cards, existing DTI/PRI cards are not compatible Add new CallPilot, existing Meridian Mail systems are not compatible.

    33. 33 Upgrading a Meridian 1 Option 51/51C/61/ 61C/71/81/81C to a CS1000M IP System System becomes CS1000M SG or MG Option 61C/81C upgrades require CP-PII or CP-PIV processor Customers with CP3 (68060), CP4 (68060E) (which were supported on Release 4.5), or earlier must upgrade to CP-PIV Option 81C upgrades require Fiber Network Fabric Option 51/51C/61 must upgrade to CS1000M SG with CP-PIV card cage upgrade Option 71/81 must upgrade to CS1000M MG with CP-PIV card cage and FNF (Fiber Network Fabric) upgrade Add Signaling Servers, choice of In-Skin CP-PM HP/IBM COTS

    34. 34 CS1000 Upgrades IP-to-IP Upgrades

    35. 35 Upgrading of a CS1000M Cabinet and Chassis to a CS1000E System System becomes CS 1000E SA or HA Cabinet or Chassis SSC (Small System Controller) in main cabinet/chassis is replaced by One CP-PM Call Server for Standard Availability (SA) Two CP-PM Call Servers and Software Option 410 for High Availability (HA) Each additional Cabinet/ Chassis requires a new Media Gateway Controller (MGC) Existing Media Cards can be reused or replaced by DSP Daughterboard to gain slots Existing ISP 1100 Signaling Server requires upgrade to 1 GB of memory Meridian Mail is not supported and CallPilot must be Release 3 or higher Contact Center Manager Server and Symposium Call Center Server “Controlled Broadcast” feature using CallPilot is not supported on CS1000E and must be converted to Broadcast RAN licenses and Integrated Recorded Announcement. Music on Hold/Delay using Conference packs must be converted to Broadcast Music licenses on CS1000E If adding Signaling Server(s), choice of In-Skin CP-PM HP/IBM COTS

    36. 36 CS1000M SG and MG Upgrades CS1000M SG and MG require CP-PII or CP-PIV processor Customers with CP3 (68060), CP4 (68060E—which were supported on Release 4.5—or earlier must upgrade to CP-PIV Option 81C requires Fiber Network Fabric (IGS no longer supported) Existing ISP 1100 Signaling Server requires upgrade to 1 GB of memory If adding Signaling Server(s)—choice of In-Skin CP-PM HP/IBM COTS

    37. 37 CS1000S to CS1000E Upgrades Separate Call Server with SSC card is decommissioned The SSC (Small System Controller) modules in each of the MG1000S Chassis are replaced by a new Media Gateway Controller (MGC) One of the MG1000 Chassis will be designated to house the Primary Call Server One CP-PM Call Server for Standard Availability (SA) For High Availability a second MG1000 Chassis will be designated to house a second CPPM for HA Call Server Two CP-PM Call Servers and Software Option 410 for High Availability (HA) SSC Call Processor in each MG1000S chassis is replaced by a new Media Gateway Controller (MGC) and becomes a MG1000E CPPM Alternate Call Servers added as required for N-Way Redundancy Existing Media Cards can be reused or replaced by DSP Daughterboard to gain slots Existing ISP 1100 Signaling Server requires upgrade to 1 GB of memory CallPilot must be Release 3 or higher If adding Signaling Server(s)—choice of In-Skin CP-PM HP/IBM COTS

    38. 38 CS1000E Upgrades No upgrade to existing CP-PII/CP-PIV processor or memory is required Optional upgrade to CP-PM Modules—it would be necessary to decommission the two Motorola Chassis with CP-PII/CP-PIV processor and swap out all of the SSC Gateway Controllers with the new MGC Cards Existing ISP 1100 Signaling Server requires upgrade to 1 GB of memory Increased maximum number of MG1000Es within a single CS1000E System from 30 to 50 gateways Existing MG1000Es can continue to use the existing Small System Controllers* (SSCs) only with CP-PII/CP-PIV Processors Hybrid Solutions will be supported where some of the MG1000E Gateways will have SSC* Cards in them and some will have MGC Cards off the same CS1000E Call Server CallPilot must be Release 3 or higher *No CeMUX (PRI/T1) Support or Triple Registration for N-Way Redundancy

    39. 39 Engineering Notes In a CS1000E System, the CPPM Call Servers will only work with MGC in the MG1000E—can’t be placed in a chassis with an SSC Card Mixing MG1000E with SSC and MGC is only supported in existing CS1000E 4.0 & 4.5 CP-PII/CP-PIV Process Systems upgraded to Release 5 Automated database conversion occurs when moving from SSC based Call Server to CPPM based Call Server New System dongle are issued for systems needing database conversations After database conversion, System Dongle moves to MGC

    40. 40 Options for Upgrading a MG1000T Option #1: Convert to an MG1000E MG1000T is no longer required as the MG1000E now supports digital trunks Remove existing signaling server Replace existing SSC (Small System Controller) card(s) with MGC(s) (Media Gateway Controller) in each of the chassis Existing Media Cards can be reused or replaced by DSP Daughterboard to gain slots Database for digital trunks must be manually re-entered into the CS1000E system Provides simplified management with only one system

    41. 41 Options for Upgrading a MG1000T Option #2: Migrate to a CS1000E Database is migrated from MG1000T Continue to maintain separate database SSC (Small System Controller) in main cabinet/chassis is replaced by One CP-PM Call Server for Standard Availability (SA) Two CP-PM Call Servers and Software Option 410 for High Availability (HA) Each Cabinet/ Chassis requires a new Media Gateway Controller (MGC) Existing Media Cards can be reused or replaced by DSP Daughterboard to gain slots Existing ISP 1100 Signaling Server requires upgrade to 1 GB of memory If adding Signaling Server(s), choice of In-Skin CP-PM HP/IBM COTS

    42. 42 Options for Upgrading a MG1000T Option #3: Leave MG1000T on current release MG1000T’s can remain on current release*** and continue to serve as PSTN gateways This is not the recommended option but it is supported

    43. 43 Branch Upgrades MG1000B and Survivable Remote Gateway (SRG)

    44. 44 MG1000B Upgrade to Release 5 SSC Call Processor in the main cabinet/chassis is replaced by a new Media Gateway Controller (MGC) and a new CP-PM Call Server is added Existing Media Cards may be reused or replaced by DSP Daughterboard to regain I/O slots Existing ISP 1100 Signaling Server requires upgrade by 1 GB of memory (2GB of total)

    45. 45 MG1000B Upgrade to Survivable MG1000E SSC Call Processor in the main cabinet/chassis is replaced by a new Media Gateway Controller (MGC) and a new CP-PM Call Server is added Existing Media Cards may be reused or replaced by DSP Daughterboard to regain I/O slots Existing ISP 1100 Signaling Server requires upgrade to 1 GB of memory Survivable Media Gateway (N-way) feature is then available System Decommission process is used to transfer Analog, Digital, CLASS ISM’s the Main.

    46. 46 MG1000B Supported Software Releases Recommendations If the Main Office Call Server is on Release 5.0, the Branch Offices will be able to on Release 5.0, Release 4.5 or Release 4.0. Release 3 MG1000Bs must be upgraded to Release 5 It is recommended that the software release on the Branch Office always match the software release on the Main office It is possible for the main office Call Server and the MG1000B Core to have different software releases, as long as the main office is running a release that is higher than or equal to that of the branch office The MG1000B cannot be a higher software release than the Main It is possible to have branch offices running different software releases

    47. 47 SRGs and Release 5 BCM 200/400 based SRG 1.0 should be upgraded to SRG 1.5 Move to Linux OS Up to 90 IP Users SRG 1.0 is still supported Only H.323 for VoIP Trunking BCM 50 based SRG 50 1.0 should be upgraded to SRG 50 2.0 Increase from 32 to 80 IP users Supports both H.323/SIP trunking capability SRG 50 1.0 is still supported Further details provided in the CS1000 R5.0 Inter-Operability Module

    48. 48 Hardware and Applications Compatibility Changes from Release 4.5

    49. 49 Hardware Compatibility Cards not supported on Release 5

    50. 50 Applications Compatibility Generally, only applications that are current or sustained when a release becomes Generally Available (GA) are supported See the Product Bulletin for a complete listing of compatible applications A key thing to remember for upgrades of CS1000S and CS1000M Cabinet and Chassis systems is that when they become CS1000E systems, some applications are no longer supported that were previously supported or are still supported on CS1000M SG/MG IP Phone 2004 Phase 0 Traditional Music on Hold/Delay using conference packs Call Pilot for Contact Center Broadcast announcements Meridian Mail and CallPilot 2.02 The next few charts highlight the changes from Release 4.5

    51. 51 System Compatibility Matrix Changes From Release 4.5 CallPilot – R2.02 is not supported on CS1000E Upgrades from CS1000M Cabinet/Chassis or CS1000S to Release 5 (CS1000E) will require CallPilot to be on R3 or higher Meridian Mail is not supported on CS1000E Upgrades from CS1000M Cabinet/Chassis to Release 5 (CS1000E) will require an upgrade to CallPilot Still supported on a Meridian 1 System and CS1000M-SG or CS1000M-MG running Release 5.0 Traditional Music on Hold/Delay using conference packs is not supported on CS1000E Upgrades from CS1000M Cabinet/Chassis or CS1000S to Release 5 (CS1000E) will require Broadcast Music ISM licenses instead

    52. 52 System Compatibility Matrix Changes From Release 4.5 Contact Center Manager Server and Symposium Call Center Server “Controlled Broadcast” feature using CallPilot is not supported on CS1000E Upgrades from CS1000M Cabinet/Chassis or CS1000S to Release 5 (CS1000E) will require Broadcast RAN ISM licenses and Integrated Recorded Announcement instead This is due to DSP resource limitations in the CS1000E See Product Bulletin PB2006_0312 for more details 802.11 Wireless IP Gateway with the Symbol brand telephone sets is no longer supported Remote Gateway 9110/IP Adapter is no longer supported Remote Gateway 9115/9150 must be at release 1.4.2 or higher (1.4.1 is no longer supported) Nortel Agent Greeting Release 2.0 is no longer supported, must be Release 3.0 or higher

    53. 53 System Compatibility Matrix Changes From Release 4.5—Continued IP Phone 2004 Phase 0 sets are supported on the CS1000M SG/MG running Release 5.0 IP Phone 2004 Phase 0 (original sets) is no longer supported on CS1000E, MG1000B or SRG—IP Phone 2004 Phase 1 or 2 Set is required Upgrades from CS1000M Cabinet/Chassis, CS1000S, MG1000B or SRG to Release 5 (CS1000E) will require Phase 0 2004 sets to be replaced Integrated Package for Meridian Link (IPML) for MPS 500/1000 is no longer supported Business Communications Manager Must be 200/400/1000 3.7 or 4.0 for networking with CS1000 3.5 and 3.6 are no longer supported

    54. 54 System Compatibility Matrix Changes From Release 4.5—Continued CS2000 must be at SN09—SN07 and SN08 no longer supported for networking with CS1000 CS2100 must be at SE08—SE07 is no longer supported for networking with CS1000 Earlier vintages of these products may work, but if there is a problem you must upgrade to the current GA vintage: Carrier Remote – GA Vintage 7.03 Line-Side T1 - GA Vintage 2.03 Enhanced Line-Side T1 - GA Vintage 3.06

    55. 55 System Compatibility Matrix Changes From Release 4.5—Continued Mini Carrier Remote – Recommended Vintage 12.02 or 12.03 Earlier vintages may work, but if there is a problem you must upgrade to 12.03 or later. Each MCR LMI, LMX and RMI card must be on Release 12.02 (Nov 2004), 12.03 (Nov 2005) or higher. NT5D6xBA or CA vintage Mini Carrier Remote cards can be upgraded using a NT7R76AC MCR Flash Upgrade module The purpose of this Flash Module is to upgrade the MCR firmware to Release 06 of the CB vintage, hardware Release 12 for the LMI and the LMX, or Release 11 for the RMI. NT5D6xAA vintage cards cannot be upgraded in the field and must be returned to Nortel Repair Center for upgrade as per the Advanced Replacement Procedure. See Product Bulletin P-2005-0343r1 (01 November 2005) for more details

    56. 56 Enterprise Configuration Management Signaling Server Considerations

    57. 57 Network Routing Server Mixed Versions Any Network Routing Server (NRS) that is running CS 1000 Release 5.0 software can only synchronize data with another NRS also running CS 1000 Release 5.0. The Alternate NRS must also be upgraded to Release 5.0 before synchronization can occur. Any Failsafe NRS must be running Release 5.0 Any nodes with a Failsafe NRS must be running Release 5.0. In practice this will govern the order in which NRS and Nodes can be updated, and may mean disabling any Failsafe NRS functions for a while as the network is undergoing upgrade. If the entire network is not to be upgraded to Release 5.0, but portions kept on a prior Release, there are two options available: Disable Failsafe NRS on nodes not on Release 5.0 Leave the NRS on Release 4.x and upgrade only the nodes to Release 5.0 that are required. This will of course mean that any new features that require the Release 5.0 NRS are not implemented

    58. 58 Signaling Server Options for Upgrades Reminder—Considerations Revisited

    59. 59 Enterprise Common Manager Requirements The Enterprise Common Manager (ECM) Framework is a software layer on the Linux COTS sever which provides the web server, login security and other support for System Management plug-ins . The Framework provides the following key features Single Sign On and external LDAP, RADIUS authentication Role and instance based access control Common configuration launch point from element table Provides centralized security service Support master-master real time replication for high availability Logs Certificate management Local SNMP management More details are provided in the Management Module Supported hardware is IBM306 or HP DL320, not the CPPM Supported OS is Linux only—VX Works is not currently supported

    60. 60 Questions ?

More Related