Module 2D--CS1000 5.5 Management Enhancements V005

8/3/2019 Module 2D--CS1000 5.5 Management Enhancements V005

http://slidepdf.com/reader/full/module-2d-cs1000-55-management-enhancements-v005 1/87



BUSINESS MADE SIMPLE

Nortel Proprietary2 Channel Partner SE Workshop Series: CS1000 Release 5.5 Workshop

Management Enhancement in

CS1000 R5.5Module #2DNortel CS1000 Release 5.5 Partner SE WorkshopChannel Partner SE Workshop Series




Management Hierarchy




Management Framework in Release 5




Management Framework in Release 5.5




ECM Architecture Overview

• The ECM framework is a generic system management software infrastructurethat provides the following benefits and features:• Central launch point for management facilities that oversee multiple

network elements to manage the entire network• Common UI look and feel across all supported management facilities• Web service interface where third-party developers can create applications

to access ECM• Registry of the managed elements that launch the managementapplications

• Security that provides Authentication, Authorization, and Auditing (AAA) forplug-in Web applications (elements) that reside within the ECM framework

• Centralized security policy administration and enforcement• Private certificate authority and X.509 certificate management

• Single Sign On (SSO) and external Light Directory Access Protocol (LDAP)and Remote Authentication Dial In User Service (RADIUS) authentication

• Role- and instance-based access control• Local Simple Network Management Protocol (SNMP) management• Central point to manage users, passwords, and system access


http://slidepdf.com/reader/full/module-2d-cs1000-55-management-enhancements-v005 7/87Nortel Proprietary7 Channel Partner SE Workshop Series: CS1000 Release 5.5 Workshop

ECM - Management Framework



Framework Supports Functional Plug-Ins







• The primary security service consists of the following:

• security service

• security service client

• certificate management module

• Web server• The backup security service consists of the following:

• Linux host trust management module

• security service

• security service client

• certificate management module• Web server

• The data from the primary security service is replicated to the backupsecurity service. The backup security service provides security serviceif the primary security service fails.




• The member server consists of the following:

• Linux host trust management module

• Security service client

• Certificate management module

• Web server

• The member server is the smallest footprint module. Allmember servers need IP connectivity to either the primaryor backup security server. If this connectivity is down,users cannot log on to the member server Web pages.

• Member servers Require additional Licensing in the ECMEC section




• With ECM, two installation media provide eight installation options.• The NRS CD provides the following three installation options:

• The Primary ECM Server (install NRS and the primary ECM securityservice)

• A Backup ECM Server (install NRS and a backup ECM security service)• A Member Server (install NRS with ECM joining an existing secure

network)• The Element Manager (MGMT) DVD provides the following five

installation options:• The Primary ECM Server (install EM and the primary ECM security

service)• A Backup ECM Server (install EM and a backup ECM security service)

• A Member Server (install EM with ECM joining an existing securenetwork)• The Primary ECM Server (install EM, Subscriber Manager and the

primary ECM security service)• A Backup ECM Server (install EM, Subscriber Manager and a backup

ECM security service)




ECM 5.5 Enhancements

• Support for managing multiple releases of CS1K

• Bulk provisioning of Phones

• Bulk provisioning of routes and endpoints

• SSO cookie domain• Services Management

• Courtesy Change

• UI Enhancements

• Enhanced display of CS1K traffic reports

• Security Banner display on EM on VxWorks and NRSM on VxWorks

• Complete maintenance commands support for MGC & MC32S cards




Multiple Release Support




Multiple Release SupportContinued





• During upgrade of ECM from 5.0 to 5.5, the NRSMelements in the framework gets upgraded

• For the CS1000 elements, the administrator has tomanually change the element to 5.5 using the EditRelease option shown in previous slide.





Element Multiple Release Support

(Rls 5.0 and Rls 5.5)

CS1000 Element Manager Yes

Basic Client Configuration Yes

NRS Manager No

Bookmark No




Services Management

• Release 5.5 ECM Framework introduces the concept of “Services” similar to“Elements”

• The authorization policies for Services work the same way as for the elements

• Services cannot be added or configured during runtime. They are configuredonly during install time.

• In release 5.5, there is only one service “Subscriber”




Security - SSO Cookie Domain

• When the primary and backup security servers areconfigured in different domains, Single Sign On (SSO)requires authentication to switch from the primary tobackup security server. For authentication, the primary

and backup security server domain names must match• This requires an administrator to change the cookie setting

• When the SSO cookie domain is changed, users must clearthe existing ECM related cookies from the cache in the

Internet browser for all users• See Next Slide




SSO Authentication from User Interface




Setting the SSO Cookie Policy




Basic Client ConfigurationBulk Provisioning of Phones




Bulk Provisioning of PhonesContinued

• Browse for the CSV file containing the phone records and import thefile to the Call Server.

• CSV File Formats can be found in the NTP Element Manager SystemReference – Administration NN43001-632





• After the import operation, user has following options

• To view the logs of the import operation.

• To download the failed records (if any) during import operation.





• The logs for the import operation provides the information abouttransmission of each record in the CSV file.





• User can download the CSV file containing only failed records. Usercan again import this CSV file by correcting all the errors displayed inthe log.




Basic Client ConfigurationUser Interface EnhancementsPop-up Windows Have Been Removed

• Less number of pages open at any point in time

• Error is shown in the same window from where the operation wasinitiated

• Low security risk

R5.0 User Interface R5.5 User Interface




Basic Client ConfigurationUser Interface EnhancementsChanges In Multiple Add Page

• Mandatory fields are added. With this, Multiple Phone Add works inR5.5.

• ZONE for IP phones

• DMC, INDX, CFW, Redirection DN length for DCS sets




Basic Client ConfigurationUser Interface EnhancementsChanges in Bulk Phone Edit Pages

• Simplified Work flow




Basic Client ConfigurationCourtesy Change

• Courtesy change feature checks the telephone’s busy/idle statusbefore transmitting the changes to the switch.

• If the telephone is busy, the change is not transmitted, because thiswill disconnect the active call.

• Transmitting large number of phones with courtesy enabled is notrecommended.




Linux-based NRSEnhancements

• Bulk export and import of routing entries• The NRS supports up to 20,000 routing entries and default routes.

Release 5.5 introduces a new feature “Bulk export and import ” toimprove the provisioning of the routing entries.

• A Comma Separated Value (CSV) file is used to create routingentries in the Standby database.

• The routing entries in the Standby or Active database can beexported into a CSV file.

• The CSV file can be edited and imported into the same NRS or intoanother NRS.

• Enhancement of the NRS Manager User Interface• The NRS Manager Navigator can be expanded to the lowest leaf

level of each node by clicking on the root node.• A Hide and Show link is introduced into the Endpoints and Routes

web pages. Clicking on the Hide link removes the search criteriapanel from the web pages, providing a larger panel for the display ofthe Routing Entries and Endpoints.




Bulk Provisioning of Routes and EndpointsImport

• Bulk provisioning of routes and endpoints (import) is a new feature in NRSM. User can import a CSVfile containing routes and endpoints

• CSV formats can be found in the NTP Network Routing Service Installation and CommissioningNN43001-564





• User can browse for the CSV file containing the routes and endpointsand import the file to the database.





• After the import operation, user has following options

- to view the import results.

- to download the failed records (if any) during import operation.




Bulk Provisioning of Routes and EndpointsExport

• User can export routes from both active and standby database.

• Export from Active database





• Export from Standby database





• User can save the exported routes CSV file and later use it for importoperation

• Also can view the export results information




EM & NRSM - Security Banner Feature

• Displays a security warning banner on the login page ofEM & NRSM on VxWorks (not applicable to ECM version,as ECM has a common login banner)

• Provides provision to configure security banner onstandalone NRS VxWorks (functionality available in 5.0 forCS)




Security Banner FeatureContinued




Security Banner FeatureContinued




Traffic Reports Feature

• This feature displays the traffic data measured underSystem Traffic and Customer Traffic with proper headersand descriptions. (15 System Traffic reports and 15Customer traffic reports)




Traffic Reports FeatureContinued




Traffic Reports FeatureContinued




MGC/MC32S Commands Support

• This feature provides support for executing the MediaGateway Controller (MGC) and 32 Channel SecureMedia Card (MC32S) command line interface (CLI)maintenance commands from Element Manager.




MGC/MC32S Commands SupportContinued




MGC/MC32S Commands SupportContinued




Subscriber ManagerKey Principles

• Subscriber Manager• Intuitive and user-friendly Web-based interface that is deployed as a

plug-in application to the Enterprise Common Manager (ECM)framework.

• Provides a centralized location for the management of subscriberinformation for enterprise services

• Product agnostic – no business logic for any product• Interfaces to Products an API• Rls 1.0 only supports CS1000

• Users access the ECM framework and Subscriber Manager throughMicrosoft Internet Explorer 6.02600 or later.

• With Subscriber Manager, you can:• easily manage subscribers, subscriber accounts, and subscriberphone services within your network

• quickly search, sort, and update single and multiple subscribers• subscriber accounts within a single application interface




Subscriber ManagerBefore and After




Common Name Directory

• Subscriber Manager uses the Common Network Directory (CND) forits data store, including the CND’s backup and restore feature.

• Subscriber Manager is dependent on the CND for LDAPsynchronization and bulk updates of subscribers.

• The CND has specific hardware platform and operating systemrequirements.

• The Common Network Directory (CND) 2.2 must be installed on aWindows server. CND can be installed on Windows XP, Windows2000 Server, or Windows 2003 Server. There are limitations onlocales and service packs on each operating system.

• Installation of the CND application on a Windows server includesCND, CND Manager and the LDAP directory.

• The CND application is included on the EM application Install DVD.




SubscriberSystem Overview




Subscriber Terminology

• Subscriber Manager uses the following terminology below.

• Example User does not refer to a Telephony User.• User

• Administrator using the subscriber application

• Subscriber• Typically an employee of the organization who will be using the services provisioned by

the User.• Account

• For CS1000 an account is the same as a telephone entry in overlay 10 and 11.

• Service Type• The type of service being provided to the Subscriber such as Telephony. Future service

types may be Conferencing and Messaging.

• Element

• The Call Server as listed in the Elements table in ECM.• Target

• Each Element can further break down where an account is provisioned through the use ofa Target. In CS1000’s customer numbers are targets.

• Template• The “boiler plate” or “feature package” used for quickly creating accounts in an element.




Subscriber Manager Installation




Configure CND Connection Details




Creating Subscribers, Accounts andTemplates

• There are several steps to building Subscribers

• Build templates

• Build subscribers

• Assign Subscriber Fields

• Create Subscriber Accounts• Assign Service Type

• Assign Elements

• Assign Target

• Assign Template




Templates

• Subscriber Manager allows users to add and configure accounts(phone services) for subscribers with available templates in ElementManager (Linux Based with BCC).• When configuring subscriber accounts (phone services), the user is

redirected from Subscriber Manager to Element Manager.

• A template contains attributes that are common to a CS 1000 phone

type.• Once a template is created, you can use it to apply these common

attributes to a group of phones, without having to repetitively definethe same value for each phone.

• In general, using a template is a more efficient method of adding largenumbers of phones than maintaining each phone individually.

• The administration pages for Templates are organized as a new linknamed Templates inside phones section of EM navigator.• similar to the template administration pages existing in TM web

station.




Template – Home Page

• “Template” same concept as in TM Web Station

• The templates database is created per ECM installation (SecurityDomain), and hence only those BCC elements which are part ofthat ECM installation can share the template.

• Lists all templates that are created. Add, Delete and Update of

template can be initiated from this page itself




Template Details

• Similar to Phone details page

• Template name is unique




Phones - Adds

• Modifications introduced in to create phones using template

• Add using template creates an association between the template and the phone.

• From there-on this association is checked when ever the phone is updated. If thephone changes are different from the template then the association is removed (rules onnext slide).




Template Association

• Certain phone properties should be set differently for every telephoneand hence changing these properties does not break the telephone toTemplate association. Below is the list of those properties:• Designator (DES) – This property is part of General Properties

section of phone details page.• Station Control Password (SCPW) – This property is part of

Features section of phone details page.• Directory number parameter of any key feature.

• In addition, there are certain properties, which are not part of theTemplate, and hence can be changed in the phone. Below is the list ofthose properties:• Terminal Number (TN) - This property is part of General Properties

section of phone details page.• Call Party Name Display (CPND) - This property is part of Keyssection of phone details page.

• Voice Mail Box (VMB) - This property is part of Keys section ofphone details page.




Auto Assign DN

• In templates where auto assign DN is enabled, users should validatefunctionality as required. This function can be used to add single ormultiple phones

• Example: Adding a single phone• When Auto Assign DN is switched on and when starting DN is

specified –The starting DN overwrites the

existing partial DN specified in the Template. This is true for analog,digital and virtual phones. Also on the phone details page (Step 2 ofadd phone), the message “The current DN is the specified startingDN. It is not the partial DN specified in the Template” is displayedindicating that the starting DN overwrites the partial DN specified inthe Template.

• When Auto Assign DN is switched off – Partial DN specified in the

Template itself becomes the DN. This is true for analog, digital andvirtual phones. Add will fail in this case unless user corrects theDN. The message “The current DN is the partial DN specified in theTemplate. The DN must be modified in order to successfully add thephone.” is displayed.




Phones – Edit (Multiple Phones)

• Template introduced as a edit field.

• Enable the changes in the template to be applied to the associated phones.

• Also serves as a way to associate existing phones to a template.




Template Updates

• The following properties of the phone cannot be changed while doingan update using template. These properties are set differently forevery telephone and hence updating it from template is not supported.

• Designator (DES) – This property is part of General Properties section of phone details page.

• Station Control Password (SCPW) – This property is part ofFeatures section of phone details page.

• Directory number parameter of any key feature

• Terminal Number (TN) - This property is part of General Properties section of phone details page.

• Call Party Name Display (CPND) - This property is part of Keys section of phone details page.

• Voice Mail Box (VMB) - This property is part of Keys section ofphone details page.






Phones – Advanced Search

• Allows users to build their own query for more complex searches usingtemplate as one of the criteria




Phones – Report

• Reports modified to introduce template as a field and criteria.

C fi i /M dif i S b ib




Configuring/Modifying SubscribersCreate Subscribers

• In most cases users will createsubscribers using one of the followingmethods:

• Subscriber Manager Web UI

• CND CSV Synchronization

• Through CND Managers CSV Sync

• CS1000 Migration Tool (not shown)

• Used to migrate users from Linux EMin 5.0

• Allows import of 5.0 EM Users to 5.5

• Auto populates Subscriber Data• CND LDAP Sync






Delete Subscribers

• In most cases users will delete subscribers using one ofthe following methods:

• Subscriber Manager Web UI

• When deleting subscribers using the Subscriber ManagerWeb UI, all the subscribers accounts are automaticallydeleted in EM.

• Telephones associated with subscriber will be deleted




Export Subscribers

• Export subscribers into a CSV file for offline editing.

• Through CND Manager Interface




Example of Creating Subscriber




Add Subscriber Fields that can be populated

• Identification

• Last name• Note: Last name is a mandatory field.

• First name

• Middle name

• Preferred name

• Employee ID

• Subscriber type• Use this field to identify the type of subscriber such as, employee,

project, roles, or location.

• Language

• Comment• Use this field to enter any specific information for the subscriber.




Add Subscriber Fields That Can Be Populated

• Directory and Phone Numbers• Extension• External• ESN• Cell• Pager

• Fax• Address

• E-mail• Office location• Mailing address• Street

• City• Province/State• Country• Postal/Zip code

• Organization• Job title• Department• Company• Service start date

•




Accounts

• Accounts

• An account is a provisioned service,

available through an element, for asubscriber.

• A subscriber can have more than oneaccount,

• telephone service(only supported account on Rls 1.0)

• conferencing service

• voice mail service

• etc

• Required subscriber accountproperties

• Subscriber Manager only requires thesubscriber’s last name to create anew subscriber. Individual elementshave specific requirements forrequired subscriber properties for thecreation of accounts.




Account Properties




Create Account

• Users must use a Template to create accounts through SubscriberManager.

• Optionally, users can accept all defaults when creating an account, orspecify more details for the account.




Update Account

• There are two waysto update accounts

• Click on the“service type” linkin the account listof the subscriberdetails page

• Search for thetelephone in EMand make thechanges there.These changeswill be reflected inSubscriberManager.




Delete Account(s)

• There are three variations to deleting accounts inSubscriber Manager.

• Select a subscriber on the Subscriber List page and click“Delete”. This will delete the subscriber and the associated

accounts.• Select a subscriber on the Subscriber List page and click“Delete All Accounts”. This will delete all the accounts but notthe subscriber.

• Select the accounts on the Subscriber Details page and click

“Delete”. This will delete the selected accounts.




Synchronize Account(s)

• EM is always the master of account data from Subscriber’s point of view. • Accounts between Subscriber Manager and EM can become out of synch for a number of reasons:

• network issues prevent messages from being delivered to Subscriber Manager• Database crash in EM requiring a restore of data from the previous day.• Directory crash in Subscriber Manager requiring a restore of data from the previous day.




Anonymous Account(s)

• Anonymous accounts are accounts that exist in EM but do not have asubscriber, in Subscriber Manager, associated with the account.

• Anonymous accounts can be assigned to subscribers using theAnonymous Account web page.

Schedule Backup of Data




Schedule Backup of Dataand Directory Server

• The CND Manager supports schedule backup of data inthe directory. This will backup subscribers and theiraccounts.

• It does not backup the accounts in the Elements.




Subscriber Limitations

• Only CS1000 accounts are currently supported.

• No reporting mechanism for accounts.

• No account move supported.

• Search results limited to 1000 subscribers.

• Only data from one account can be published into the customer’scorporate directory.

• Selectable by administrator• Example Subscriber has two Phones only 1 can be published

• No account search capability

• Search by subscriber and then drill into accounts

Note: Future releases of Subscriber will deal with these limitations.




Dependencies

• ECM 5.5 on Linux

• CND 2.2 on Windows

• EM 5.5 on Linux




Subscriber Manager Capacities







Backup Slide




Publishing Accounts

• When account properties are published, account information is copied to specific subscriberproperties within the system.

• Publishing account specific information allows the user to synchronize account specificinformation in the corporate directory.

• By default, the first account created for any distinct service type is automatically published.

• The following conditions apply when publishing accounts:

• Only one account for each service type can be published to the subscriber data.

• When a new account is selected for publishing, it overwrites any data already present in theparticular subscriber attribute.

• If an existing account is published and the user needs to publish a different account, publishing thedifferent account removes the publish flag from the old account in the account list.

• •External applications such as LDAP Subscriber Synchronization and CSV Subscriber Synchronization can result in data mismatch between the subscriber properties and the publishedaccount properties.

• If a data mismatch occurs, users must do one of the following:

• update the account

• manually update the subscriber properties

• select the account and click Publish

• synchronize the affected accounts with the element




Date post:	07-Apr-2018
Category:	Documents
Upload:	donnalaird
View:	234 times
Download:	0 times

Module 2D--CS1000 5.5 Management Enhancements V005

Documents