1 / 41

.Course ISM Transfer System for CS 1000: Keycode Retrieval and System Transfers

Learn about ISM transfer types, access in KRS, same & between system transfers, managing system capacity, transfer history, applicable systems, and how to request/access ISM transfers. 8 Relevant

jkoonce
Download Presentation

.Course ISM Transfer System for CS 1000: Keycode Retrieval and System Transfers

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. Course Title: Keycode Retrieval System (KRS) – ISM Transfers for CS 1000Course ID: KR102Issue: 1.0 • Release 3.0 and higher systems • Using KRS “Site Administration”

  2. "This session falls under the confidentiality agreement and therefore is subject to non-disclosure" Also note - any specific details shown in the training such as company names or pricing, are examples for training purposes only, and do not represent accurate data. The screen captures shown in the training may vary slightly from the screens in the current version of the tool.

  3. Course Aims & Objectives • Understand ISM transfer types and requirements • How to access ISM Transfer functionality in KRS • How to perform Same System ISM Transfers • How to perform Between System ISM Transfers

  4. Course Chapters • Managing System Capacity • ISM Transfer History • Types of Transfers • Applicable Systems • How to request access • How to access ISM Transfers • Part 1: Introduction • Part 2: Same System ISM Transfers • Part 3: Between system ISM Transfers • Part 4: Appendix

  5. ISM Transfers = Managing System Capacity • Why ? • System capacity on CS1000 Rls 3.0 & later is controlled by User Licenses (ISMs) • ISM transfers provide flexibility to manage system capacity in a customer’s business • Recommended Strategies to Manage System Capacity • Small capacity changes: Avaya recommends using “wired for” or spare software capacity per system • Medium / Large capacity changes: Avaya recommends using ISM Transfer process • What are License Transfers ? • Same system License transfers: Adjusting the relative quantity of ISMs (SW licenses) on a single system (ie. analog to digital) • Between system License transfers: Moving like for like Licenses (ie. digital to digital) from one system to another.

  6. ISM Transfer History • Purchase Order (Manual) ISM Transfers became available with the introduction of Release 3.0 • Refer to regional product bulletins for details • Automated ISM Transfers became available October, 2005 via the Site Administration Tool in KRS • KRS ISM Transfer functionality updated in May, 2011 • New Same System Transfer types added for CS1000 • IP USERS <-> SIPN • RANCON <-> IP RAN • MUSCON <-> IP MUSIC • H.323 ACCESS PORTS <-> SIP ACCESS PORTS • Same and Between System ISM Transfers added for MG1000B systems

  7. Applicable Systems – Same and Between System transfer • ISM Transfers apply to the CS1000 Family of Core systems which includes: • Meridian 1 • MG1000B – new in May, 2011 • CS1000E–excluding Geographic Redundant (1+1 Primary or Standby) • CS1000M – excluding Geographic Redundant (1+1 Primary or Standby) • CS 1000M systems that are Standby sites in an N+1 Geographic Redundant configuration (i.e. include pkg 405) can be included in Network Pools but have the following limitations for ISM transfers. • Can donate any License type except IP users and IP Basic to any system except 1+1 primary & standby sites • Can receive any License type except IP users and IP Basic from any system except 1+1 primary & standby sites • Can donate any Standby IP User Licenses to any other N+1 Standby site • Can receive any Standby IP User Licenses from any system type • ISM Transfers are NOT supported on: • CS 1000 Applications • BCM • SRG User Licenses • MG1000T • CS 1000M and CS 1000E Geographic Redundant (1+1 Primary or Standby) *

  8. Important Note – Open Orders • Never attempt ANY form of ISM transfer (i.e. Same Site or Between Sites) IF there is an open order against the site(s). • Performing an ISM Transfer while an open order is present will result in KRS returning an error message that the transfer cannot take place. • Please wait until the order has closed before attempting the ISM transfer.

  9. eBusiness Tools Landing Page – to access all the tools ! • www.avaya.com/ebizn (Americas, Asia) • www.avaya.com/ebizu (Europe, Middle East, Africa) • Alternate direct KRS access: www.avaya.com/krs

  10. Accessing ISM Transfers in KRS • Login into KRS • www.avaya.com/ebizn (Americas & APAC) • www.avaya.com/ebizu (EMEA) • Alternate direct KRS access: www.avaya.com/krs • Select “Product Family” = Communication Server 1000 • Select <Go> • Select ISM <Site Administration> from the left menu in KRS. For Same Site and Between Site Transfers • Select <Search Network Pool> in the left menu of KRS, to search and view Network pools 4. 5. • To add a new administrator to an existing Network Pool : • Open an Avaya Support ticket (on line or by phone) requesting , “Site Administrator for Network Pool” be added to your KRS account

  11. Course Chapters • Part 1: Introduction • Part 2: Same System ISM Transfers • Part 3: Between system ISM Transfers • Part 4: Appendix • Move software licenses (ISMs) of one type to another (ex. analog to digital) on the same Release 3.0 or later system

  12. Same System ISM Transfers • Decrease one ISM type and increase the second ISM type by the same amount • Analog to Digital, Digital to Analog • Existing ISM pairs must be transferred in multiples as they were purchased • System must be running CS1000 Release 3.0 or later • Creates a single new keycode with the adjusted ISM values • Same System Transfers do not require the system to be registered to a network pool • No Purchase Order required. Transfer completed via KRS • A sysload is required to activate the new keycode, since one of the ISM values have been decremented !! • The system doesn’t know which ISMs are available – un-program them prior to installing the new keycode ! • When converting programmed ISMs that are no longer required, they must be freed up (outed/un-programmed) or the sysload with the new keycode will remove the last ones programmed • Only the current listed Distributor of Record for a site may perform same system ISM transfers

  13. Available ISMs for Same Systems Transfers : • Convert ISMs of one type to another on a CS 1000 Rls 3.0 later system • 8* Analog  8* Digital (APAC and EMEA) • 1 Analog  1* Digital (Americas) • 1 Internet (IP) telephones  1 SIPN • 1 RAN CON  1 IP RAN CON • 1 MUS CON  1 IP Music • 1 H323 Access Ports  1 SIP Access Port Convert ISMs from one type to another on a MG1000B • 8* Analog  8* Digital (APAC and EMEA) • 1 Analog  1* Digital (Americas) • * Analog/Digital only applies to licenses purchased on systems prior to R6.0

  14. Same System ISM Transfers using KRS Step 1:Ensure you are the current listed Distributor of Record for a site (i.e. last keycode purchased for the site) Step 2:Use the “Site Administration” link in KRS to request same system ISM transfers No Avaya Fees Step 3:KRS will show the new keycode or you may use the “Retrieve Keycode” link in KRS to retrieve the updated keycode Updated keycode available on KRS within minutes Step 4: Install the new keycode – will require a sysload!

  15. Same Site ISM Transfer Select the “Site Administration Link” from the left menu in KRS Enter the System ID Select the “Same Site Xfer” check box Note Xfer = ‘Transfer’ Select <Continue> 3. 2. 1. 4.

  16. Same Site Transfer – select ISMs to Transfer KRS will retrieve and display system information and current ISM values for the specified site From the drop down menu, select the number of ISMs to be transferred Select <Continue> Note: The S/W release must be 3.0 or higher 1. 2.

  17. Same Site Transfer – Review & Accept/Modify Changes KRS validates the new configuration and presents a Summary of the new ISM values Review the summary Select <Generate Keycode> to proceed KRS will initiate the Keycode generation process. Average time to generate is 90 seconds or select <Revise> to make modifications 2. 4. 3.

  18. Same Site Transfer – view and download the keycode 1. • When Keycode generation is complete, KRS will display the new keycodes on the “Retrieve Keycode” page • Download the keycode file using the standard process • Refer to “KR101 - CS 1000 Training” for more information 2.

  19. ISM transfer network pool Course Chapters • Decrease ISM type(s) on one Meridian 1 / CS1000 system (donor system) and increase the same ISM type(s) by the same amount on another Meridian 1 / CS1000 system (target System) in the same ISM transfer network pool • Creates 2 new keycodes: one removing the ISMs from the donor and one adding the same ISMs to the target system • Part 1: Introduction • Part 2: Same System ISM Transfers • Part 3: Between system ISM Transfers • Part 4: Appendix

  20. Between System ISM Transfers using KRS Step 1:Register sites in Network Pool –submit one Form for each desired Network Pool • Set up a Network Pool by ordering the Registration Fee and completing a Site Registration Form. Follow the instructions on the form. • A Network Pool is a grouping of Meridian 1 / CS1000 core systems that are owned by the same customer or parent company, & located in the same theatre/region (i.e. Americas) • Systems in a Network Pool can be a mix of system types (11C / 61C etc) & a mix of SW Rls (4.0 & 4.5 etc) • Fees: NT8R80AE registration fee for every 10 sites NT8R80BE registration fee for 2 sites only Step 2: Use the “Site Administration” function on KRS to request between system ISM transfers –Fees = None Step 3:Use “Retrieve Keycode” function on KRS to retrieve the updated keycodes Step 4: Install the 2 new keycodes – Donor system will require sysload! Step 5:Send the Donor LD 22 to the Avaya KRS-Network Pool Administrator

  21. Between System ISM Transfers – CS1000 • Analog  Analog * • Digital  Digital * • Class  Class* • Internet (IP) telephones  Internet (IP) telephones • Basic IP users  Basic IP users * • Wireless (DECT)  Wireless (DECT) • ITG trunks  ITG trunks * • ACD agents  ACD agents • PCA  PCA • AST  AST • RAN con  RAN con • MUS con  MUS con • IP Peer H323  IP Peer H323 • SIP Access Port  SIP Access Port * • Survivability  Survivability * • SIP CTI TR87  SIP CTI TR87 * • SIP Converged Desktops  SIP Converged Desktops * • Temporary IP User  Temporary IP User * • TDM User  TDM User * • SIPN  SIPN * • SIP3  SIP3 * • MOBX  MOBX * • TLSV  TLSV * • FMCL  FMCL* • IP Attendant  IP Attendant * • IP Media Services  IP Media Services * • IP RAN  IP RAN * • IP Music  IP Music * • Available ISMs for Between System Transfers: • Move “like for like” ISMs from one CS1000 system to another CS1000 system within the same network pool * Some ISMs apply to certain software releases only

  22. Between System ISM Transfers – MG1000B • Available ISMs for Between System Transfers: • Move “like for like” ISMs from one MG 1000B system to another MG 1000B system within the same network pool • Analog  Analog * • Digital  Digital * • Class  Class* • TDM User  TDM User * • * Some ISMs apply to certain software releases only

  23. Between System ISM Transfer System Requirements • The donor & receiver systems must be in the same ISM transfer network pool • ISMs must be transferred in the same increments that they can be purchased • Both systems must be on the same software release but can be on a different issue within the release (i.e. Rls 4.0 and 4.5) • The target system must be at the same or lower service level than the donor system. ISM transfers to a system at lower service level does not create a credit and is a one way transfer. • The Avaya keycode database becomes the database of record • The partner and customer must agree to install both keycodes within 90 days and to send a LD 22 SLT from the donor system to Avaya. If not they agree to pay for the ISMs transferred to the receiver system. • Must leave a minimum of 16 users on a donor system or it must be decommissioned • The system doesn’t know which Licenses you don’t need – so un-program them on the donor switch before installing the new keycode • When transferring programmed Licenses that are no longer required, they must be freed up (outed/un-programmed) or the sysload will remove the last ones programmed

  24. Viewing Network Pool Information – Search Network Pool Network Pools are created by an Avaya “Pool Administrator” in response to receiving completed “License Transfer Site Administration Registration form” Once a Network Pool is created the Partner “Site Administrator” can view their pool Select <Search Network Pool> from the left menu Enter search criteria (see slide notes). Select <Search> KRS will return a report showing all Sites contained in the pool 2. 1. 3.

  25. Network Pool Information – Search Results • By entering a Network Pool name and selecting Search, KRS will return a report displaying: • All Sites contained in the pool • A record of each site that has been used as a Donor and whether or not the Avaya Pool administrator has received confirmation (ld 22) that the downgrade keycode has been applied. • An entry will exist each time a site is used as a donor (even if used more than once). • View transfer details by clicking on any site ID listed: • the transferred Licenses • the quantity • who performed the transfer • the Receiver (target) system 1. 3. 2.

  26. Between System ISM Transfer – select the donor system Select < Site Administration> to initiate Between Site Transfer Enter the System ID of the site that you want to transfer ISM’s FROM (this is the Donor site) Select <Continue> 1. 2. 3.

  27. Between System Transfer – select target system KRS retrieves the current system configuration of the specified “Donor” site The Donor site information is displayed Enter the System ID of the site which is to receive the ISMs (Target System) Select <Continue> 2. 2. 3. 4.

  28. Between System Transfer - review sites selected • KRS retrieves and displays the system information of the Receiver site • Review and ensure the following criteria is met: • Both sites are at S/W Rls 3 or higher • Both sites are of the same release • The Receiver Site (or Target) is at the same Service level (or lower) as the Donor site • Note: KRS will automatically apply this validation when the Generate Keycode request is made but a visual check may avoid wasted time of making the License transfer selections 1. 1.

  29. Between System Transfer – select transfer values • Below the Summary of the Donor and Receiver systems, a list of the current available ISM values of the Donor site will appear • A drop down menu is used to select the ISMs desired to be transferred • If there isn’t a drop down box, enter the desired value • Select <Continue>for KRS to validate the License Transfer request meets the commercial rules for the 2 sites (Both are same Core SW Release etc…) 1. 2. 3.

  30. Between System Transfer – Review Summary • After selecting the transfer values, and selecting <Continue> • KRS displays a summary screen showing the ISM values that will be enabled for both systems • Current (Installed) • Future (New) ISM values • Review the summary and select <Generate Keycode> to proceed • Select <Revise> to make modifications 2. 4. 3.

  31. Between System Transfer RECEIVER DONOR After selecting <Generate Keycode> KRS will initiate the generation of new Keycodes for both the Donor site and the Receiver Site (~ 2 ½ mins) When complete KRS will display the standard KRS “Retrieve Keycode” pages, (one Retrieve page to view & download the new Keycode for the Donor site and the other Retrieve Page to view & download the new Keycode for the Receiver site KRS will note in the Network Pool the creation of a Donor keycode for the site ID and will create a status flag for the Avaya Network Pool Administrator to expect to receive with in 90 days a LD22 via email when the Donor sites “downgrade” Keycode has been installed

  32. Sites with PASS+ SRS – Software Rls Subscription • Sites that have existing PASS + SRS contracts can be registered in network pools for ISM transfers • Transferring of ISMs between systems is unlimited • Systems with a PASS +SRS Contract which increase ISMs from a donor system (with no PASS+ SRS Contract) must be brought up to the current ISM count (“true up”) prior to requesting an upgrade using the PASS + SRS Program • End Customer is responsible for notifying the Distributor of Record holding the PASS +SRS Contract that the ISM count has changed

  33. PASS + SRS Example: Mixed Systems • If System A donates 250 ISMs to System B, then no update is required for the PASS+ SRS Contract. No credit for the PASS+ SRS contract on System A is available. • If System B donates 250 ISMs to System A, then the PASS+ SRS contract for System A will be required to be updated to 750 ISMs prior to applying the PASS+ SRS order codes for any upgrade System B 500 ISMs WithoutPASS +SRS Contract System A 500 ISMs WithPASS+ SRS Contract

  34. Example: Both Systems on PASS + SRS • If System A donates 250 ISMs to System B, then PASS+ SRS Contract for System B is required to be updated, however, no fees will be applied • If System B donates 250 ISMs to System A, then PASS+ SRS Contract for System A is required to be updated, however, no fees will be applied System A 500 ISMs WithPASS+ SRS Contract System B 500 ISMs WithPASS+ SRS Contract

  35. Course Chapters • Part 1: Introduction • Part 2: Same System ISM Transfers • Part 3: Between system ISM Transfers • Part 4: Appendix • Bulletins and documentation • Network Pool Requirements • Between System ISM Transfers • – General Considerations • – Channel Responsibilities • – Customer Responsibilities

  36. Additional Info • The following Bulletins referenced in this training package are available on the Avaya Partner Portal: • ISM Transfers using KRS for Communication Server 1000 Systems (Rev 2 - May, 2011; formerly P-2005-0296_ISM Xfers_rev1 for Americas) • System Decommission, Software License and/or Software Service Level Reduction (P-2004-0092 for the Americas) • Transferring ISMs on CS1000 Rls 3 or later using Purchase Orders (P-2004-0093 for the Amercias) • Add’l documentation on KRS ISM Transfers: • KRS: www.avaya.com/krs • From the M1 / CS1000 product login, Click ‘Documentation, Forms & User Guides’ • Select folder “Forms” for the Network Pool Registration Form • Select folder “Product Info Bulletins_Policy” for product bulletins • Select folder “User Guides”, then “ISM Transfers” for KRS documentation

  37. Between System ISM Transfers – Network Pool Requirements • There is no limit to the number of sites in an ISM transfer network pool, • the registration fee (NT8R80AE) will apply to each block of 10 sites or fewer in any one network pool. For Network pools of 2 sites only, Partner’s may order NT8R80BE. • A system can only be registered in one ISM transfer network pool • PBXs on software releases lower than 3.0 can exist in a Network pool in anticipation of when they upgrade, but will not be able to donate or receive ISMs until they upgrade to Release 3.0 or higher • A customer can authorize any partner to manage their ISM transfers – the partner will automatically become the distributor of record for the ISM transfer keycode(s) when requested • Where 2 Partners maintain a customer’s systems – the customer and Partners must elect one Partner to manage their License transfers. The chosen Partner will be the single point of contact held accountable to Avaya, but may subcontract installation to any other Partner as required • A minimum of 3 working days should be allocated to set up an ISM transfer network pool • An updated “ISM Transfer Site Administration Registration” form is required to make changes (adds/deletes) to existing network pools

  38. Between Systems ISM Transfers - Considerations • Avaya recommends that between-System License transfers should only be considered for larger scale License moves: • 2 new keycodes are required – one must be sysloaded • There is considerable work and associated labour cost for Partners to request, install and manage 2 keycodes • Small scale moves: Avaya recommends these should be handled through the purchase of additional capacity on individual systems (Wired For etc.). • Existing maintenance agreements may be violated if another Partner is brought in to work on a system • Care should be taken when identifying a single Partner to represent a customer for License transfers • If it is not possible to identify a single Partner, then it may be necessary for each Partner to manage the transfer of Licenses between the systems that they control only • The system doesn’t know which Licenses you don’t need – so un-program them on the donor switch before installing the new keycode • When transferring programmed Licenses that are no longer required, they must be freed up (outed/un-programmed) or the sysload will remove the last ones programmed

  39. Between Systems ISM Transfers – Partner Responsibilities • If multiple Channel Partners support an End Customer’s systems today – then a single Partner must be elected to manage License transfers for all the customers sites. They will become the single point of contact for Avaya for the customer’s License transfers. • Note: the chosen Partner may choose to subcontract to another Partner for keycode installation. • Work with the customer to complete the “License Transfer Site Administration Registration” form • Submit the completed and signed form to Avaya • Request / Order the License transfer keycodes for the customer when required • Install or coordinate the installation of the License transfer keycode(s) within 90 days of shipment of the keycode. • Automatic email reminders will be sent to the Partner prime that created the License Transfer at 30, 60 & 90 days if they have not returned a LD 22 SLT from the donor system to Avaya • LD 22 SLT should be emailed to the Avaya Network Pool admin prime (see form for regional addresses) • Channel Admin Primes can query KRS to search for all their Network Pools where keycode transfers have taken place within 30, 60 & 90 days & where a LD22 has not been received by Avaya via the ‘Search Network Pool link • Submit billing purposes only purchase order after 90 days if the LD 22 is not returned to pay for the Licenses added to the receiver system • If LD 22 is not received then the Channel Partner will be removed from the program, all License transfer Network Pools will be eliminated and no further transfers will be possible • Will submit an updated “License Transfer Site Registration” form to Avaya to make changes to an existing License transfer Network Pool

  40. Between Systems ISM Transfers - End Customer Responsibilities • If multiple Partners support your systems today – you need to select a single Partner to manage your License transfers. They will become the single point of contact for Avaya for your License transfers. Note: the chosen Partner may subcontract to another Partner for keycode installation • Work with the chosen Partner to complete the “License Transfer Site Administration Registration” form • Sign the “License Transfer Site Registration” form – by signing you are agreeing that the chosen Partner is the Partner that will manage your License transfers and that you will abide by all policies associated with the process • Request License transfers from the Partner as required • Work with your Partner to ensure that they load the new keycode(s) within 90 days and that they send the LD 22 to Avaya • If a transfer is requested and the LD 22 is not returned (ie the receiver keycode is installed but the donor keycode is not) you may be asked by the Partner to pay for the additional users on the receiver system

  41. Thank You

More Related