Avaya Remote Feature Activation (RFA) User Guide

Transcription

1 Avaya Remote Feature Activation (RFA) User Guide Issue 5.0 September 2007

2 2007 Avaya Inc. A Rights Reserved. Notice Whie reasonabe efforts were made to ensure that the information in this document was compete and accurate at the time of printing, Avaya Inc. can assume no iabiity for any errors. Changes and corrections to the information in this document may be incorporated in future reeases. For fu support information, pease see the compete document, Avaya Support Notices for Software Documentation, document number To ocate this document on our Web site, simpy go to and search for the document number in the search box. Documentation discaimer Avaya Inc. is not responsibe for any modifications, additions, or deetions to the origina pubished version of this documentation uness such modifications, additions, or deetions were performed by Avaya. Customer and/or End User agree to indemnify and hod harmess Avaya, Avaya's agents, servants and empoyees against a caims, awsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deetions to this documentation to the extent made by the Customer or End User. Link discaimer Avaya Inc. is not responsibe for the contents or reiabiity of any inked Web sites referenced esewhere within this documentation, and Avaya does not necessariy endorse the products, services, or information described or offered within them. We cannot guarantee that these inks wi work a of the time and we have no contro over the avaiabiity of the inked pages. Warranty Avaya Inc. provides a imited warranty on this product. Refer to your saes agreement to estabish the terms of the imited warranty. In addition, Avaya s standard warranty anguage, as we as information regarding support for this product, whie under warranty, is avaiabe through the foowing Web site: Copyright Except where expressy stated otherwise, the Product is protected by copyright and other aws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a crimina, as we as a civi, offense under the appicabe aw. Avaya support Avaya provides a teephone number for you to use to report probems or to ask questions about your product. The support teephone number is in the United States. For additiona support teephone numbers, see the Avaya Web site:

3 Contents What s new in RFA RFA 10.9 enhancements License fie simpification for LSP and ESS servers Feature screen sort enhancement RFA 10.8 enhancements for Ca Center Type II Per User upgrades RFA genera and detaied information/warning messages Ca Center Type III features Chapter 1: Getting Started About this chapter RFA training and approva About RFA Group Authorization Identification (GAI) License fies When is a icense fie required? When is a icense fie not required? How does a icense fie work? Deivering a icense fie Feature Keywords Transactions and system records A transaction The system record System Identification (SID) number The Modue Identification (MID) number Understanding the Features tab Understanding seria numbers RFA Reease 9.1 seria number enhancement Communication Manager Avaya DEFINITY Server Hardware Firmware Avaya S8100 Server, DEFINITY ONE, and IP Hardware Firmware Avaya S8300 Server Hardware Firmware Avaya S8400 Server Hardware Issue 5.0 September

4 Contents Firmware Avaya S8500 Server Hardware Firmware Avaya S8700 series server Hardware Firmware Security Gateway Branch Gateways Hardware Firmware Understanding Host IDs Format of the Host ID Using WebLM to find the Host ID Using the product software Genera information tabe Appication Enabement (AE) Services Contact Center Windows Soaris AIX SIP Enabement Services (SES) Meeting Exchange Moduar Messaging Persona WorkSpace Unified Communication Center Voice Sef Service Accessing RFA Computer requirements User requirements The SSO ogin Creating a SSO ogin Logging in to RFA Registering for RFA product famiies Registration for Avaya Associates Registration for Avaya BusinessPartners Accessing the RFA Appication Main Menu for a product famiy RFA Hep Avaya Remote Feature Activation (RFA) User Guide

5 Contents Chapter 2: The RFA Appication Main Menu About this chapter Accessing the RFA Main Menu Left side of the main menu My RFA Authorization Information View My Fie Deivery Status View My Upoaded Switch Config Fie Status (Communication Manager ony) Work With My Pending Transaction Records Work With My Pending System Records (Communication Manager ony) 59 Center of the main menu New Insta and Migrations Pre R Maintenance Additions Upgrades and Additions Additions, Upgrades and Migrations (Communication Manager) RFA Record Updates Deiver Fies Right side of the main menu Search/View Menu Change Product Famiy Exit RFA Chapter 3: New Insta About this chapter Before you start Procedures for a new insta High-eve steps Detaied steps Step 1: Start from the RFA Appication Main Menu Step 2: Enter the SAP order number Step 3: Verify that the SAP order data is correct Step 4: Record the transaction number Step 5: Compete the customer and genera system information Step 6: Compete the Modue and Appication Detais information Step 7: Compete the feature information Step 8: Compete the transaction Step 9: Record the SID and the version number Step 10: Deiver the icense fie Issue 5.0 September

6 Contents Chapter 4: Additions About this chapter Before you start Addition procedure to add a feature or a modue High-eve steps Detaied steps Step 1: Start at the RFA main menu Step 2: Enter the SAP order number Step 3: Verify that the SAP order data is correct Step 4: Record the transaction number Step 5: Enter the SID Step 6: Verify the SID information Step 7: Compete the Assign Patforms, Reeases, and Add Modues screen Step 8: Compete the Customer and Genera System information Step 9: Compete the Modue and Appication Detais information Step 10: Compete the feature information Step 11: Compete the transaction Step 12: Record the SID and version number Step 13: Deiver the icense fie Chapter 5: Updates and Upgrades About this chapter Introduction What is the difference between an update and an upgrade? What is a Support Upgrade? Procedure for a Support Upgrade from a pre Reease 10 and upgrade from a pre Reease Support Upgrade from a pre R10 and upgrade from a pre R10 procedure.. 98 Before you start High-eve steps Detaied steps Step 1: Start from the RFA Appication Main Menu Step 2: Enter the SAP order number Step 3: Verify that the SAP order data is correct Step 4: Record the transaction number Step 5: Compete the Customer and Genera System Information Step 6: Compete the Modue and Appication Detais information Step 7: Compete the feature information Step 8: Compete the transaction Avaya Remote Feature Activation (RFA) User Guide

7 Contents Step 9: Record the SID and version number Step 10: Deiver the icense fie Switch Updates from a pre R High-eve steps Detaied steps Step 1: Identify the switch Step 2: Record the transaction number Step 3: Obtain the switch configuration fie Step 4: Assign the sub-modues Step 5: Compete the Customer and Genera System information Step 6: Compete the Modue and Appication Detais information Step 7: Compete the feature information Step 8: Compete the transaction Step 9: Record the SID and version number Step 10: Deiver the icense fie Support Upgrade from R High-eve steps Detaied steps Step 1: Enter the SAP order number Step 2: Verify that the SAP order data is correct Step 3: Record the transaction number Step 4: Enter the SID Step 5: Verify the SID information Step 6: Compete the Assign Patforms, Reeases, and Add Modues screen Step 7: Compete the Customer and Genera System information Step 8: Compete the Modue and Appication Detais information Step 9: Compete the feature information Step 9b: Make any necessary changes for the next modue Step 10: Compete the transaction Step 11: Record the SID and version number Step 12: Deiver the icense fie Switch update from R High-eve steps Detaied steps Step 1: Enter the SID and the Maestro troube ticket number Step 2: Verify the SID information Step 3: Enter the software reease Step 4: Compete the Customer and Genera System information Step 5: Compete the Modue and Appication Detais information Issue 5.0 September

8 Contents Step 6: Compete the feature information Step 7: Compete the transaction Step 8: Record the SID and version number Step 9: Deiver the icense fie Chapter 6: Deivering A Fie From RFA About this chapter Introduction Before you start Options for deivering a fie from RFA License fie simpification for LSP and ESS servers Deivering a fie from RFA procedure High-eve steps Detaied steps Step 1: Start with the RFA Appication Main Menu Step 2: Enter the SID Step 3: Verify the SID data Step 4: Cose the confirmation window Step 5: Seect a deivery option Chapter 7: Viewing The Deivery Status Of A Fie About this chapter View My Fie Deivery Status procedure High-eve steps Detaied steps Step 1: Seect a date range and a status Step 2: Seect a singe record to see a detaied status report Step 3: Review the detaied status report What do you do next? Chapter 8: Viewing And Changing Your RFA Authorization Information 167 About this chapter Procedures to View and change your authorization information High-eve steps Detaied steps Step 1: Cick My RFA Authorization Information on the RFA Appication Main Menu Step 2: Request the appropriate change Avaya Remote Feature Activation (RFA) User Guide

9 Contents Chapter 9: Working With Transaction Records About this chapter Find and continue work on a transaction record Working with transaction records procedure Method one: Using the RFA Appication Main Menu Method two: Using the Search/View Menu Which screen do you see when you find the transaction record? Do you have to compete the transaction now? Deeting a transaction record Chapter 10: Working With System Records About this chapter Introduction Using the Search/View menu How to find a system record when you do not know the SID How to view a system record when you know the SID Modifying a system record Procedure to modify a system record Competing a pending system record (Communication Manager ony) Why you might need to find and continue work on a system record How you can find and continue work on a system record Work with your pending system records Compete a pending system record Chapter 11: The Communication Manager Product Famiy In RFA About this chapter Working with Communication Manager icense and authentication fies Communication Manager systems requiring a icense fie When is a icense fie required for Communication Manager? Appications under the Communication Manager product famiy IP connect to Muti-Connect migration changes Creating a icense fie for an ESS server, WSP, LSP, or SRP License-Error and No-License modes Working with authentication fies Type II Per User upgrades Per User feature enhancement exampes Upgrade guideines RFA genera and detaied information/warning messages Issue 5.0 September

10 Contents Feature screen enhancements for the PER USER upgrade functionaity. 192 Support Upgrades Using the Feature Extraction Too (FET) Using the License Instaation Too (LIT) The Shared Bade Server Additions, Upgrades R10+, and Migrations R Before you start Information and warning messages High-eve steps Detaied steps Step 1: Cick Additions, Upgrades and Migrations Step 2: Enter the SAP order number Step 3: Verify that the SAP order data is correct Step 4: Record the transaction number Step 5: Enter the SID Step 6: Verify the SID information Step 7: Compete the Assign Patforms, Reeases, and Add Modues screen Step 8: Compete the Customer and Genera System information Step 9: Compete the Modue and Appication Detais information Step 10: Compete the feature information Step 11: Compete the transaction Step 12: Record the SID and version number Step 13: Deiver the icense fie License fie seria number swap-out Before you start Overview High-eve steps Detaied steps Step 1: Cick License Fie Seria Number Swap-Out from the Maintenance menu Step 2: Enter the troube ticket number and the seria number of the existing processor Step 3: Verify that the information on the resuts screen is correct Step 4: Record the SID and the new SID version number Step 5: Enter the seria number for the new processor Step 6: Compete the transaction Chapter 12: Product Famiies Supported in RFA Advanced IP Phone Features Appication Assurance Networking Avaya Remote Feature Activation (RFA) User Guide

11 Contents Appication Design Environment (ADE) Appication Enabement Services RFA-icensed Appication Enabement Services appications Avaya IQ Avaya Proactive Contact Licensed Features Branch Gateways The seria number for the G250 or G350 Media Gateway Post instaation verification Activating the VPN Repacing a Branch Gateway Communications Process Manager Contact Center E-mai icense request and Contact Center Customer Interaction Express Directory Enabed Management Enterprise Network Management Consoe Event Processor Integrated Management Meeting Exchange Moduar Messaging one-x Mobie one-x Porta Security Gateway Security Gateway modes that require a icense fie Repacing a Security Gateway Softcients Unified Communications Center (UCC) UCC icense server UCC Feature settings UCC software reease number Instaing the icense fie Voice Sef Service (VSS) Voice Over IP (VoIP) stations Appendix A: RFA enhancements Reease 9 enhancements New RFA supported product famiies Issue 5.0 September

12 Contents RFA Reease 9.6 Type III Feature enhancements RFA Reease 9.1 seria number enhancement Overview of RFA Reease 9.0 enhancements Unsupported Communication Manager operations Terminoogy for RFA Reease Modues Operations SAP order detai sequence number Quaified modues Fu upgrade Partia upgrade Patform migration RFA Main Menu changes RFA main menu for Additions and Upgrades RFA main menu for the Communication Manager product famiy SAP Order tab and SAP Order Data button changes SAP Order tab SAP Order tab enabed Aowabe operations SAP Order Data button Patform migrations Upgrades Features screen changes The Assign Patforms, Reeases, and Add Modues screen Overview On-ine Hep Screen ayout The SAP Order Detais section The Add Modues box The Existing Modue Detais section How to use this screen High-eve steps to assign an operation to a modue Patform Migrations Upgrades Materia codes with mutipe operations RFA Reease 9.0 Exampes Exampe one: Migrating and upgrading the main server and adding a modue Exampe two: Upgrading and/or adding a modue Exampe three: Migrating and upgrading modues Avaya Remote Feature Activation (RFA) User Guide

13 Contents Hepfu hints When do I have to submit the data in the Assign Patforms, Reeases, and Additions screen? How do I know which modue to seect? What do I do if I forgot to change the seria number on a patform migration? What do I do if I appied the migration or upgrade to the wrong modue before the transaction was compete? What do I do if I seected the wrong modue for an operation? Gossary Index Issue 5.0 September

14 Contents 14 Avaya Remote Feature Activation (RFA) User Guide

15 What s new in RFA RFA 10.9 enhancements License fie simpification for LSP and ESS servers Starting in RFA 10.9, text appears on the Deivery screen that instructs the user when to deiver a icense fie for the sub-modues. Hepfu information appears in the Detaied Deivery screen as shown in Tabe 1. Tabe 1: Information contained in the Detaied Deivery screen Action If you are instaing a new system If the main server icense fie is modified (by an SAP Order or by using the Features screen) in one or more of the foowing ways: An upgrade to the Communication Manager software A patform migration Changes to or additions of shared features If the main server icense fie is modified by a icense fie seria number swap out. If you change an un-shared feature on the main server icense fie using the Feature screen and you seect to appy changes to a modues. You wi need to deiver a icense for: The main server and a the sub-modues The main server and a sub-modues that are at a reease ess than R014. In this case you do not need to deiver a icense fie for any sub-modues that are at R014 or greater. However, if one or more of the foowing features are added or changed on the main modue, you must re-deiver the icense fies for the LSPs and the ESS servers that are at R014: FEAT_DS1MSP FEAT_STTRKMSP FEAT_SYCCMSP The main server The main server and a sub-modues 1 of 2 Issue 5.0 September

16 What s new in RFA Tabe 1: Information contained in the Detaied Deivery screen (continued) Action If you change an un-shared feature on the main server icense fie using the Feature screen and you seect to appy changes to this modue ony. You wi need to deiver a icense for: The main server If a sub-modue is added to the system If a sub-modue s icense fie is modified by a icense fie seria number swap-out If a sub-modue icense fie is modified using an SAP order or by the Features screen in one or more of the foowing ways: Upgrade to the Communication Manager software Patform migration Changes to features or additions of features The sub-modue The sub-modue The sub-modue 2 of 2 Feature screen sort enhancement The Keyword Description coumn and the Keyword coumn can now be sorted aphabeticay by cicking on the individua coumn heading (see Figure 1). After cicking the coumn heading, the coor changes from bue to purpe. A hep screen is provided by cicking the Changing the Feature Sort ink on the top of each tabe type. Cicking on the coumn heading sorts the information in a the tabes on the Feature screen. 16 Avaya Remote Feature Activation (RFA) User Guide

17 RFA 10.8 enhancements for Ca Center WARNING:! WARNING: You must submit any changes to the Features screen before you perform a re-sort or your changes wi be ost. Figure 1: Feature screen with sort enhancement RFA 10.8 enhancements for Ca Center In RFA 10.8, Ca Center becomes a separate appication under the Communication Manager product famiy. The Ca Center appication appears in a Communication Manager system records created after RFA 10.8 and in a new Communication Manager transactions. New materia codes have been created to support this change. For more information on the new Issue 5.0 September

18 What s new in RFA materia codes, see JobAidsToos.! Important: Important: Use the ASD Communication Manager Configurator when creating an SAP order for the Communication Manager product famiy. Faiure to use the ASD Communication Manager Configurator may resut in capacities and features that are dropped from the icense fie. The resuting icense fie may not oad on the server. SAP orders for new instas, Pre R10 upgrades, and Pre R10 updates must incude a materia code specifying the Ca Center reease version. In Assign Order Items screen in exampe Figure 2, the Ca Center appication appears as a separate appication under the Communication Manager appication. The Assign Order Items screen dispays the current version of Ca Center in back and the version Ca Center wi upgrade to in red. Figure 2: Assign Order Items tab with Ca Center appication A separate screen appears for the Ca Center appication in the Modue/Appication Detais tab (Figure 3). To dispay the screen for the Ca Center appication, seect Main Server Ca Center from the drop-down menu. 18 Avaya Remote Feature Activation (RFA) User Guide

19 RFA 10.8 enhancements for Ca Center Figure 3: Modue/App Detais screen Ca Center appication Type II Per User upgrades Starting with RFA 10.8 and Ca Center 4.0, Per User upgrades wi be avaiabe for Ca Center. The use of the Per User upgrade functionaity ensures that the correct number of upgraded agents are enabed in the RFA icense fie. For exampe, when deuxe agents are being upgraded to Ca Center 4 or ater, a Feature Keyword of VALUE_LOGGIN_DLX with a setting type of PER_USER must be on the order. The materia code associated with this order contains a setting type of PER USER. An existing SID or an SAP order may contain more than one agent type. Possibe agent types in order of the owest to the highest ranking are, VALUE_LOGGIN (basic), VALUE_LOGGIN_DLX (deuxe), and VALUE_LOGGIN_ELT (eite). RFA does not keep more than one agent type, a types except for the highest ranking are dropped. The vaue associated with the keyword on the order must be correct. The quantity to be upgraded shoud not exceed the amount of agents as you can never upgrade more agents than you have. On the other hand, any agents not upgraded during the upgrade transaction are ost as they are not carried forward and cannot be recaimed in a future transaction. The materia code, quantity and description for the features in the order dispay in the SAP order tab. To obtain more information about the Type II features and their associated Setting Types, RFA provides a Detaied Feature Information button that appears on the bottom of the SAP Order screen as shown in Figure 4. Issue 5.0 September

20 What s new in RFA Figure 4: Detaied Feature Information button on SAP Order screen After cicking Detaied Feature Information, the Detaied Feature Information screen appears (Figure 5). The Detaied Feature Information screen dispays Type I, Type II, and Type III feature information for appications that appears on the order. In the Type II tabe, if a PER USER setting type is used for a Feature Keyword, the quantity being upgraded appears in the Materia Code Quantity coumn. Figure 5 shows an exampe of a Type II Feature Information tabe for the Ca Center appication. The materia codes shown in the exampes in this book may not be current or correct and shoud not be used as a reference when pacing an order in SAP. 20 Avaya Remote Feature Activation (RFA) User Guide

21 RFA 10.8 enhancements for Ca Center Figure 5: Feature Detais screen for Ca Center appication Features that are associated with Ca Center that previousy appeared under the Communication Manager feature ist have been moved under the Ca Center appication. The features can be viewed by seecting Main Server Ca Center using the drop-down menu in the Features tab. The vaue associated with each Type II feature appears in the Setting coumn. Important:! Important: Ca Center features appear in RFA for the main modue ony. When a icense fie for the sub-modue is generated, RFA adds the Ca Center features to the icense fie for the sub-modue. Issue 5.0 September

22 What s new in RFA Figure 6: Feature tab with Main Server Ca Center features dispayed In exampe Figure 6 a warning message dispayed to aert the user that there are 50 more agents on the upgrade order than appear in the RFA system record. In this case, RFA can ony upgrade the 200 agents that it knows about. For more information on RFA messages, see RFA genera and detaied information/warning messages on page 22. RFA genera and detaied information/warning messages There are two categories of information/warning messages that appear in RFA for upgrades associated with features using a PER USER setting type. RFA uses genera messages to aert you that an issue has occurred and to indicate which appication has the issue. Some genera messages appear before the transaction is created whie others appear after the transaction is created but before the transaction is compete and the information on the order is appied to the RFA system record. Genera warning messages appear on the foowing screens: The SAP Order screen: The genera message appears before the order is accepted and once again after the order is accepted. The genera message appears for the foowing transaction types: - New Insta, Migrations Pre R10, and Support Upgrade: The message dispays after Accept is entered on the SAP Order tab. - Upgrade Pre R10 and PCN Updates Pre R10: The message dispays after the switch configuration fie has been upoaded on the Upoad Switch Config tab. Order Items Assigned Screen: For an Upgrade R10+ transaction the message appears after cicking the Finish button on the Assign Order Items screen. Genera Customer Info: A message appears at the top of the Genera Customer Info screen. This message appears for a transactions that encounter a warning condition. 22 Avaya Remote Feature Activation (RFA) User Guide

23 RFA 10.8 enhancements for Ca Center - Upoad Switch Config tab - Upgrades Pre R10 - PCN Updates Pre R10 Detaied warning messages appear in the Features tab directy beow the Type II and Type III Feature information tabe. You must seect the appication that received the warning from the drop-down ist to view the features for that appication. RFA dispays warning messages when there is an issue with a Type II feature that has a PER USER setting type. Exampes of the warning messages associated with each screen are expained in detai in the Job Aid for Per User Upgrade Warning Messages. The Job Aid can be found on the Features tab by cicking the More Information button and on the RFA Information page at, CAUTION:! CAUTION: If you see information or warning messages on the RFA transaction, it is sti possibe to compete the transaction and deiver the icense fie. Be aware that if you do compete the transaction, the icense fie may not be correct. To avoid an incorrect icense fie, it is important that you understand the warning or informationa message and it is strongy recommended that you contact the Saes/Design team before competing the transaction. Ca Center Type III features The Ca Center type III features, IP_Agent and AgentSC, appear under the Ca Center appication in the Type III Feature ist. Any warning messages associated with IP_Agent and AgnetSC appear in the Type III Feature ist. Issue 5.0 September

24 What s new in RFA 24 Avaya Remote Feature Activation (RFA) User Guide

25 Chapter 1: Getting Started About this chapter This chapter contains the foowing basic information that you need to know before you work with RFA: RFA training and approva on page 25 About RFA on page 26 Understanding seria numbers on page 39 Understanding Host IDs on page 44 Accessing RFA on page 50 The SSO ogin on page 51 Logging in to RFA on page 52 Registering for RFA product famiies on page 53 RFA Hep on page 55 RFA training and approva Training is a requirement for a new users or users registering for a new product famiy. Training is provided in the form of two documents, The Remote Feature Activation (RFA) User Guide, and The Getting Started With Remote Feature Activation User Guide. Both documents can be found at web site. On-ine testing for RFA is part of Avaya s overa certification program. RFA assessments can be found at You must have manager or coach approva for each supported product famiy before you can use the RFA appication. Issue 5.0 September

26 Getting Started About RFA Remote Feature Activation (RFA) is a web-based appication that is used to create, modify, and deiver a icense or an Communication Manager authentication fie. RFA does not change any existing procedures for instaing, upgrading, maintaining, or administering an Avaya system or product. Foow the standard procedures in the product documentation to the point where you need the icense fie and the authentication fie. Then use the procedures in this book. Once you have the icense fie or an authentication fie on your computer, return to the product documentation for the remaining procedures. Tip: Tip: Authentication fies are used for Avaya servers that are running Avaya Communication Manager on an open operating system. For more information on authentication fies, see Working with authentication fies on page 187. RFA uses terms and processes that might be unfamiiar to a new user. This section contains information on: Group Authorization Identification (GAI) on page 26 License fies on page 26 Feature Keywords on page 28 Transactions and system records on page 29 The Modue Identification (MID) number on page 30 Group Authorization Identification (GAI) Each BusinessPartner is assigned a unique Group Authorization Identifier (GAI) number. The GAI must be entered in the system record before the BusinessPartner can access the system record. If you are a BusinessPartner that requires access to a system record that does not contain your GAI, you must submit a Transfer System Record form to a Different BusinessPartner form. A copy of the form can be found on the RFA Information page at For more information on system records see Transactions and system records on page 29. License fies A icense fie is an encrypted fie that you use to activate software features such as capacities, reease, and offer categories. The Avaya servers, modes, and appications that require a icense fie are isted in this book under the chapter for that product famiy. 26 Avaya Remote Feature Activation (RFA) User Guide

27 About RFA An RFA icense does not contain Communication Manager software, nor does an RFA icense change Communication Manager from one reease to another. Communication Manager software must be instaed on the server before you insta a icense fie. When is a icense fie required? A icense fie is required for: New instaations Upgrades, migrations and additions Support Upgrades Maintenance updates without a Support Upgrade order Seria number swap-outs Changes in the Host ID Each Enterprise Survivabe Server (ESS) Each Loca Survivabe Server (LSP) When is a icense fie not required? You do not need to obtain a new icense fie when you: Upgrade or update an existing system to a dot reease, uness the dot reease contains new features. Change hardware that is not reated to the Host ID or the seria number in the icense fie. Make administration changes that are outside the customer options, offer options, and specia appications form. Are instaing a Security Gateway and you do not want to add any additiona capabiities beyond the defaut capacities. Issue 5.0 September

28 Getting Started How does a icense fie work? Once you insta a icense fie, the Avaya system checks to ensure that: The seria number or the Host ID in the icense fie matches that of the system. A features and capacities are within the prescribed imits. For Communication Manager ony: - A Survivabe Remote Processor (SRP) is not serving as the active processor. - A Wide Area Network (WAN) Spare Processor is not serving as the active processor. - A Loca Survivabe Processor (LSP) is not serving as the active processor. Deivering a icense fie Depending on the product, RFA provides severa ways to deiver a fie: E-mai - A fie can be deivered as an e-mai attachment to your e-mai address. Downoad - Fies can be downoaded to your PC. Direct connect - This option is avaiabe ony on the Avaya DEFINITY servers. With the direct connect option, the icense fie oads directy on the Avaya DEFINITY server. For more information on deivering a fie see Chapter 6: Deivering A Fie From RFA on page 153. Feature Keywords RFA creates a icense fie based on the materia codes that appear in the SAP order. RFA maps between the SAP materia codes and the features and capacities in the icense fie. Whie the icense fie does not contain the materia codes themseves, it does contain the features and the capacities that wi be activated for the system. The features and capacities are represented by Feature Keywords. Feature Keywords are Engish text that uniquey identify which features and capacities to activate. For a compete isting of the Communication Manager Keywords see the RFA Information page at You can find Keywords for other product famiies in the Getting Started With Remote Feature Activation (RFA) at 28 Avaya Remote Feature Activation (RFA) User Guide

29 About RFA Transactions and system records When you create or modifying a icense fie: 1. RFA creates a transaction record that contains the information from the SAP order and the manuay entered information. The transaction record is assigned a transaction number. For more information on transactions see A transaction on page When you compete the transaction, RFA creates a system record. For more information on system records see The system record on page RFA assigns a System Identification Number (SID) to the system record. For more information on SIDs see System Identification (SID) number on page 30. A system record is a permanent record that is stored in the RFA database. A SID is a number that is inked to the system record that is used by RFA to identify the Avaya product or appication. A transaction When you start to work in RFA you are conducting a transaction. RFA creates the transaction with information from the SAP order and information that you enter. During the course of the transaction you are given a transaction number. Using the transaction number, you can stop and restart or deete a transaction at anytime before you compete it. A competed transaction becomes a system record. The icense fie is created from the system record. Transactions that are oder than two months are automaticay deeted from the RFA database. The system record A system record is created from a transaction. A system record is a permanent record in RFA and cannot be deeted. The system record permanenty tracks the: Sod-to customer information Product reease Product category, if appicabe Product features Capacities Seria number or Host ID Issue 5.0 September

30 Getting Started System Identification (SID) number When you compete a transaction you receive a System Identification (SID) number and a SID version. Each SID is a unique number that is never changed or deeted in RFA. A SID version number changes when you modify information that the SID contains. The SID is the most effective way to ocate a system record. If you do not know the SID, you can sti find the system record by using the search functionaity. For more information on how to search for a system record, see Search/View Menu on page 61. The Modue Identification (MID) number Every Avaya server requires a separate icense fie. RFA refers to each Avaya server within an Avaya system as a modue. Each modue is has a Modue Identification (MID) number. The MID for the main server is aways 1. Additiona modues, such as a Loca Survivabe Processor (LSP) or an Enterprise Survivabe Server (ESS) are assigned MIDs that are greater than 1. Each system is assigned a SID. For exampe, a LSP or an ESS server are considered modues because the servers are part of entire network. You can have one SID and mutipe MIDs if one network incudes many LSP or ESS servers. Understanding the Features tab The Feature tab shows the features, the capacities, and the genera software information. This screen aso shows any additiona features and capacities that were contained in the SAP order when the customer purchased them. These are the features and capacities that the icense fie contros. The Feature screen can contain a maximum of five tabes. The system dispays ony those tabes that appy to the product famiy that you are creating a icense fie for. The foowing ist incudes a the possibe tabes as they appear on the screen: Drop-down menu on page 31 Information section beow the drop-down menu on page 31 Type II features on page 31 Type I Features tabe on page 34 Type III Features Tabe on page Avaya Remote Feature Activation (RFA) User Guide

31 Understanding the Features tab Starting with RFA Reease 9.0, the foowing enhancements have been appied to the Feature screen: A feature in a muti-modue system that is shared across a modues in the same system is caed a shared feature. A shared feature is dispayed on the Features screen of a main modue. You do not see a shared feature on the Feature screen of a sub-modue. A shared feature is identified within the Shared Features coumn. The Shared Feature coumn contains a yes if the feature is shared or a no if the feature is ony avaiabe on the main modue. Even though the shared features no onger dispay on the sub-modues, the shared features are incuded in the icense fie for each sub-modue. For muti-modue systems, there are some features that ony appy to sub-modues. These features can be on the main modue and on a sub-modue with different settings. If the feature is a sub-modue feature it cannot be a shared feature. The radio buttons for the Appy Changes to this Modue Ony option and the Appy Changes to A Modues option, have been removed for the sub-modues. The Appy Changes to this Modue Ony radio buttons sti appear on the main modue. When you submit the feature information for a modue, the system dispays a message that the action appies to the dispayed modue ony. Additiona system messages have been added to aert you to create and deiver a icense fie for the current modue and for a modues when you modify a feature. Drop-down menu - The drop-down menu is used to seect additiona modues or appications. Information section beow the drop-down menu - This read-ony tabe contains information about the Avaya system incuding the modue ID, the modue type, the transaction number, the SID, and the SID version. Type II features - The Type II features tabe contains features that have a vaue or capacity. Cick Notes under the Notes coumn to see detais about the Keyword in that row. For some Keywords, the Setting coumn can be used to set the vaue for the Keyword. The range for the Setting coumn is to the right of the fied. For exampe, in Figure 7 you can set a maximum of 5200 or a minimum of 0 for Logged-In ACD Basic Agents (VALUE_LOGGIN). Issue 5.0 September

32 Getting Started Figure 7: Type II Features tabe Type II Features warning and informationa messages - RFA dispays warning messages when there is an issue with a Type II feature that has a PER USER setting. The warning messages appear in a tabe directy after the Type II tabe on the Features screen. Figure 8 shows an exampe of the Type II Per User feature tabe. Figure 8: Type II PER USER Feature tabe The Type II Per User Feature tabe contains the foowing fieds: Per User Feature Keyword: Dispays the Feature Keyword contained on the order with the Setting Type of PER USER. Upgrade Setting Vaue from Order: Dispays the setting vaue associated with the Feature Keyword as it appears on the order. 32 Avaya Remote Feature Activation (RFA) User Guide

33 Understanding the Features tab Setting Vaue on SID (Additions, Upgrades, Migrations) or Avaiabe to Upgrade (New Instas, Upgrade Pre R10 and PCN Updates Pre R10): Contains the current setting as it appears in the RFA system record and the RFA icense. A vaue of None appears for New Instas, Upgrades Pre R10, and PCN Updates Pre R10 transactions. Warning Message: Contains detaied warning information describing the inconsistency between the setting vaue on the order and the setting vaue on the SID. Tabe 2 provides a ist of detaied warning messages that coud appear in this fied. Important:! Important: The warning messages do not stop you from competing the transaction and deivering the icense fie. However, if you do not read and understand the warning message before you compete the transaction, you may not get the resuts you expected from the SAP order Tabe 2: Type II Per User warning message tabe Per User warning message RFA-239 RFA-240 RFA-241 Per User warning message description Per User Feature upgrades are not aowed on a New Insta transaction. RFA coud not compete this piece of the order. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. To view the Per User Feature upgrades on the order, seect the SAP Order tab, scro to the bottom of the screen, and cick on the Detaied Feature Information button. Look for features with a Setting Type of PER USER. Per User Feature upgrades are not aowed on an Upgrades Pre R10 transaction. RFA coud not compete this piece of the order. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. To view the Per User Feature upgrades on the order, seect the SAP Order tab, scro to the bottom of the screen, and cick on the Detaied Feature Information button. Look for features with a Setting Type of PER USER. Per User Feature upgrades are not aowed on a PCN Updates Pre R10 transaction. RFA coud not compete this piece of the order. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. To view the Per User Feature upgrades on the order, seect the SAP Order tab, scro to the bottom of the screen, and cick on the Detaied Feature Information button. Look for features with a Setting Type of PER USER. 1 of 2 Issue 5.0 September

34 Getting Started Tabe 2: Type II Per User warning message tabe (continued) Per User warning message RFA-242 RFA-243 RFA-244 RFA-245 Per User warning message description The upgrade setting vaue for feature VALUE_XYZ on the order exceeded the setting vaue for that feature on the SID. <Vaue> were upgraded, <Vaue> upgrades coud not take pace. You can compete the transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. The setting vaue for feature VALUE_STA on the SID exceeded the upgrade setting vaue for that feature on the order. <Vaue> were upgraded, the remaining <Vaue> on the SID were dropped. You can compete the transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. Feature <Feature Keyword> was on the SID with a setting vaue of <Vaue> but that feature was not on the order, therefore, the feature was dropped in the transaction and wi not appear in the new version of the SID. It is recommended that you consut with the Saes/Design team regarding this warning to correct the order. This order contains a materia code that indicates a Support Upgrade. If aso contains one or more Per User feature upgrades. Per User feature upgrades cannot be processed on orders that contain a Support Upgrade. RFA coud not compete this piece of the order. You can compete this transaction but it is recommended that you consut with the Saes/Design team regarding this warning before competion. To view the Per User feature upgrades on the order, seect the SAP Order tab, scro to the bottom of the screen, and cick on the Detaied Feature Information button. Look for features with a setting type of PER USER. 2 of 2 Type I Features tabe - The Type I Features tabe contains the software features that are entitements, and the additiona features that the customer purchased. Type I features have an on and an off setting. For a detaied description of the Keyword for that row and important feature interaction messages, cick Notes in the Notes coumn. To turn purchased features on and off, cick the box in the ON/OFF coumn. This tabe does not show any feature to which you are not entited. 34 Avaya Remote Feature Activation (RFA) User Guide

35 Understanding the Features tab Figure 9: Type I Features tabe The most common reasons to make a change to this screen are: Turn a feature off that conficts with another feature. Turn a feature off that you do not want to use. Issue 5.0 September

36 Getting Started Type III Features Tabe - The Type III Features Tabe contains features that have a product ID, a reease, and a capacity setting. Figure 10: Type III Features tabe Type III Features warning and informationa messages - RFA dispays warning and informationa messages when Type III Feature upgrades on the SAP order do not precisey correspond to the feature information in the RFA system record. The foowing exampes generated a Type III Feature warning and an informationa message: The SAP order specifies an upgrade of IP_XYZ from a reease 4 to a reease 5. The RFA system record does not show IP_XYZ running on a reease 4. In this case, a warning message is generated that expains why the upgrade was not performed, instructs the user to inform the saes/design team about the warning, and expains that it is possibe to compete the transaction but the upgrades did not take pace. The SAP order specifies a quantity of 10 upgrades of IP_XYZ from reease 4 to reease 5. RFA shows a quantity of 50 IP_XYZ features on reease 4 in the RFA system record. In this case, an informationa message shows that ony 10 IP_XYZ features were upgraded and 40 were not. Detaied warning or informationa messages appear in a Warning Message tabe (Figure 11) in the Feature tab on the bottom of the screen. The Warning Message tabe contains the foowing coumns: Product ID: This coumn dispays the product ID associated with the warning or informationa message. From Reease Version: This coumn dispays the reease of software that the product ID is currenty running. An entry of Any aows the product ID to upgrade from the current reease to the new reease specified in the To Reease Version coumn. When Any is used, RFA first upgrades the product IDs that are running the owest reease. Limit on From Reease: This coumn dispays the current imit for this product ID in the RFA system record. To Reease Version: This coumn dispays the reease that the product ID is upgrading to as specified in the SAP order. 36 Avaya Remote Feature Activation (RFA) User Guide

37 Understanding the Features tab Limit on Order: This coumn dispays the maximum number of product ID upgrades contained on the SAP order. Warning Messages: This coumn contains one of the warning or informationa messages shown in Tabe 3. The Warning Message tabe aso contains a ink to the Job Aid for Type 3 Feature Upgrade Warning Messages. The job aid provides information that heps you to understand the warning and/or informationa messages isted in Tabe 3. Figure 11: Features tab with Type III Feature Warning Important:! Important: The warning messages do not stop you from competing the transaction and deivering the icense fie. However, if you do not read and understand the warning message before you compete the transaction, you may not get the resuts you expected from the SAP order. Issue 5.0 September

38 Getting Started See Tabe 3 for a description of the warning and informationa messages. Tabe 3: Type III warning message tabe Type III warning message RFA-229 RFA-230 RFA-231 RFA-232 RFA-233 RFA-234 RFA-235 Type III warning message description This warning message states that there are no entries for the product ID in the RFA system record. RFA coud not compete this piece of the order. You may want to inform the Saes/Design team of this warning. You can compete the transaction but the upgrade for this feature wi not take pace. This warning message states that there were no entries for the product ID at the reease specified on the order. RFA coud not compete this piece of the order. You may want to inform the Saes/ Design team of this warning. You can compete this transaction but the upgrade for this feature wi not take pace. This warning message states that the imit on the order exceeded the imit on the From Reease. The warning shows the number of the product IDs that were upgraded and the number of the product IDs that were not upgraded. You may want to inform the Saes/ Design team of this warning. This informationa message states that the imit on the From Reease exceeded the imit on the order. The message dispays the number of the product IDs that were upgraded and the number of the product IDs that remain. This warning message states that the imit on the order exceeded the imit on a the avaiabe From Reeases that are ess than the To Reeases. The warning dispays the number that were upgraded and the number that coud not be upgraded. You may want to inform the Saes/Design team of this warning. This warning message states that there were no entries for the product ID at a reease ess than the To Reease on the order. RFA coud not compete this piece of the order. You may want to inform the Saes/Design team of this warning. You can compete this transaction but the upgrade for this feature wi not take pace. This informationa message states that the imit on the From Reease exceeded the imit on the order. The message dispays the number of the product IDs that were upgraded starting at the owest From Reease. 38 Avaya Remote Feature Activation (RFA) User Guide

39 Understanding seria numbers Understanding seria numbers Every product famiy in RFA uses either a seria number or a Host ID to tie the icense fie to the system hardware. This section expains what products use a seria number and how to obtain the seria number from your system. A seria number is a unique string of etters and numbers that is: Used to identify the Avaya system Tied to specific hardware components Used with the Communication Manager, Security Gateway, and the Branch Gateways product famiies Use the information in this section to identify the seria number for your Avaya system. RFA Reease 9.1 seria number enhancement Prior to Apri 2006, RFA did not aow dupicated seria numbers in the same product famiy associated with a singe end-user customer. Starting in Apri 2006, RFA aows a main server and its associated LSP to use the seria number of the same gateway. This change pertains to environments where Shared Bade Servers (SBS3000) or S8500 Servers use H.248 gateways with at east one LSP. The main server and the first LSP can use the seria number of the same gateway in the RFA system record and icense fies. The foowing format is used: The 12 digit format of a seria number for the main server is entered as it is today for icensing a Communication Manager patform. The seria number for the first LSP is entered using the same 12 digits foowed by an s. After the first LSP, a other LSPs use the standard icensing practices. Communication Manager You can find the seria number for a Communication Manager system in the foowing ways: Hardware: On Communication Manager servers and IPSI boards, the seria number is printed on a abe in the front or the back of the hardware. Firmware: Seria numbers can aso be identified through the firmware of the server or IPSI board. RFA (DEFINITY ony): RFA provides a method to retrieve seria numbers on Avaya DEFINITY servers. The foowing sections expain how to find the seria number using hardware and firmware on each server type. Issue 5.0 September

40 Getting Started Avaya DEFINITY Server Hardware Use the information in this section to identify a seria number for a DEFINITY server. A seria number appears on the abe of each Avaya DEFINITY server. Tabe 4 shows the ocation of the seria number for each DEFINITY server. Tabe 4: DEFINITY server seria number tabe Server name Avaya DEFINTIY Server R Avaya DEFINITY SERVER SI Avaya DEFINITY Server CSI Location of the seria number UN332C MSSNET processor board TN2404 processor board TN2402 processor board Firmware To obtain the seria number for an Avaya DEFINITY server through firmware, run the ist configuration icense ong command. Run this command from the System Administration Termina (SAT), or from a computer where Avaya Site Administration software is instaed. If the Avaya DEFINITY server is running Communication Manager 9.0 or ater and you have dia-in connectivity, you can use RFA to obtain the seria number. Avaya S8100 Server, DEFINITY ONE, and IP600 Use the information in this section to find the seria number for a S8100 Server, a DEFINITY ONE, and an IP600. Hardware The seria number appears on the abe of the Avaya S8100 Server (TN2314 processor board). 40 Avaya Remote Feature Activation (RFA) User Guide

41 Understanding seria numbers Firmware From the BASH prompt, type serianumber and press Enter. If the number that you received from the serianumber command is different than the seria number that is printed on the hande of the TN2314 processor board, use the seria number that you receive from the serianumber command. Avaya S8300 Server Hardware Use the information in this section to find the seria number for an S8300 Server. When a S8300 Server is used in a G250, G350, or G700 media gateway, use the seria number of the DAF1 processor motherboard. The DAF1 seria number is printed on a sticker ocated on the back of the media gateway. Firmware You can use any one of the foowing procedures to find the seria number on the S8300 in a G250, G350 or G700 media gateway: From the MGP command ine interface; type show system. From the S8300 Web interface; cick Misc, then Seria Number. If a icense fie has aready been oaded on the server, type serianumber - from a she prompt. Avaya S8400 Server Hardware Use the information in this section to find the seria number for an S8400 Server. When a S8400 Server is used, the seria number is obtained from the TN8412AP (SIPI) or the TN2312BP Internet Protoco Server Interface (IPSI). The seria number appears on the hande of the TN8412AP and the hande of the TN2312BP. Issue 5.0 September

42 Getting Started Firmware You can find the seria number in firmware in one of two ways: By cicking icense fie in the Maintenance Web interface under the Security heading. Typing serianumber from a BASH she prompt. Avaya S8500 Server Hardware Use the information in this section to find the seria number for a S8500 Server. When an S8500 is used in a configuration with port networks, the seria number is obtained from the TN2312BP or TN2312AP Internet Protoco Server Interface (IPSI). Where mutipe IPSI boards are used in a configuration, use the seria number from the reference IPSI. The IPSI seria number appears on the hande of the IPSI. S8500 main server without port networks or S8500 as an LSP Starting with Communication Manager 3.1, when an S8500 is used as an LSP or as a main server in a configuration without port networks, the seria number of an Avaya media gateway is used. The Avaya media gateway that is seected to be used as a icense host cannot have an S8300 Server instaed. The seria number of the DAF1 processor motherboard is used for the gateway. The DAF1 seria number is printed on a sticker ocated on the back of the media gateway. Firmware You can find the seria number in firmware in one of two ways: By cicking icense fie in the Maintenance Web interface under the Security heading. Typing serianumber from a BASH she prompt. Avaya S8700 series server Hardware Use the information in this section to find the seria number for a S8700 series server. When a S8700 series server is used, the seria number is obtained from the TN2312BP or TN2312AP Internet Protoco Server Interface (IPSI). Where mutipe IPSI boards are used in a configuration, use the seria number from the reference IPSI. The IPSI seria number appears on the hande of the IPSI. 42 Avaya Remote Feature Activation (RFA) User Guide

43 Understanding seria numbers Firmware You can find the seria number in firmware in one of two ways: By cicking icense fie in the Maintenance Web interface under the Security heading. Typing serianumber from a BASH she prompt. Security Gateway The seria number of a Security Gateway consists of the mode of the unit pus a 10 digit number. To find the seria number on the Security Gateway: 1. Open the Avaya Security Gateway Web interface. 2. Cick the Inspect tab 3. Cick Software For more information on the Avaya Security Gateway Web interface, see the Avaya Security Gateway documentation # and the Avaya Security Gateway User Guide at Branch Gateways Hardware Use the information in this section to find the seria number for a Branch Gateway. Currenty, the G250 and the G350 are the ony RFA supported gateways in the Branch Gateways product famiy. For the G250 and the G350 Media Gateways, use the seria number of the DAF1 processor motherboard. The DAF1 seria number is ocated on a sticker that is printed on the back of the media gateway. Firmware Use one of the foowing ways to find the seria number on a gateway: Type show system from the MGP command ine interface. Cick Misc, Seria Number from the MGP command ine interface. If a icense fie aready exists on the server, type serianumber - from a bash prompt. Issue 5.0 September

44 Getting Started Understanding Host IDs For a RFA-supported products that use Host IDs (except Moduar Messaging), a Host ID is the Media Access Contro Address (MAC) of the first Ethernet port (eth0) on the server or icense server. Format of the Host ID The MAC address consists of: A 12-digit hexadecima (0,1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F) number. The etters A through F can be entered in owercase or uppercase. A format of A or 00:20:78:1A:38:78. The MAC address must be entered in RFA without any punctuation such as: A3878. Using WebLM to find the Host ID The easiest way to find the Host ID of the WebLM server is through WebLM. To use the WebLM appication: 1. Log on to the WebLM appication on the WebLM server. 2. Cick Server Properties. The system dispays the server information (Figure 12). 44 Avaya Remote Feature Activation (RFA) User Guide

45 Understanding Host IDs Figure 12: WebLM server properties window 3. The Host ID for the WebLM server appears under the Server Host ID heading. Using the product software WebLM is the easiest way to find the Host ID of the WebLM server. However, you might aso need to find the Host ID through software. The foowing section provides a tabe with genera information and expains how to use the product software of some of the RFA-supported famiies to find the Host ID. Issue 5.0 September

46 Getting Started Genera information tabe For information on how to obtain the Host ID of your server, see Tabe 5. Tabe 5: Host ID information tabe Operating System Command Description Windows ipconfig/a A 12 digit hexadecima physica address is shown. Remove the hyphens before entering the address in RFA. AIX /usr/bin/uname -m An eight digit hexadecima Host ID is returned. Linux /sbin/ifconfig -a grep HWaddr A 12 digit hexadecima HWaddr is returned. Remove the coons before enter the address in RFA Soaris ifconfig -a An eight digit hexadecima Host ID is returned. Appication Enabement (AE) Services! Important: Important: CVLAN is caed Appication Enabement in RFA. Appication Enabement is the new RFA name for the products that were formery known as Computer Teephony Integration (CTI). To find the Host ID for an Avaya CVLAN Server for 9.0 Linux: 1. Start your browser and type the appropriate URL for the CVLAN server. Use the foowing format: 2. For the variabe cvanhostname, substitute the name of your CVLAN server. For the variabe port, substitute the port number of the CVLAN server. See the foowing exampes: The system dispays the Avaya WebLM page. The WebLM page contains the Host ID. When a dua Network Interface Card (NIC) is instaed, the Host ID is the MAC address of the first NIC. 46 Avaya Remote Feature Activation (RFA) User Guide

47 Understanding Host IDs Contact Center Windows Soaris AIX Use the information in this section to find the Host ID for Contact Center. To identify a Host ID or a physica address on a server that is running Windows: 1. Cick Start > Run, and type cmd in the Open fied. 2. At the prompt, type ipconfig /a. The system dispays the physica address, such as: Physica Address : To identify a Host ID or a physica address on a server that is running Soaris: Run the hostid command. Soaris dispays the physica address as a ist of hexadecima digits, such as e9. To identify a Host ID or physica address on a server running AIX: Run the uname -m command. AIX dispays the physica address as a ist of hexadecima digits, such as 000c066A4c00. SIP Enabement Services (SES) To find the Host ID on an Avaya Converged Communications Server: Type get-mac-address on the command ine interface. Issue 5.0 September

48 Getting Started Meeting Exchange For Meeting Exchange the MAC address of the active network interface card (Ethernet port 0) is used to create the icense fie in RFA. Use the foowing steps to find the Host ID on the Meeting Exchange server: 1. Use the termina emuation package to create a SSH connection to og in to the Meeting Exchange server. Third party remote access appications such as PuTTY are not supported by Avaya. 2. At the command ine prompt, type ifconfig eth0 grep HWaddr. The system dispays the Host ID as a string of six pairs of characters that are separated by coons such as: 00:14:5E:0A:1F:0A 3. When you enter the Host ID in RFA be sure and remove the coons and do not add any spaces. Moduar Messaging For Moduar Messaging, the Host ID is the voice mai domain identifier. The Host ID can be apha numeric and up to 50 characters in ength. The format for a Moduar Messaging Host ID is: <8 hex char>-<4 hex char>-<4 hex char>-<4hex char>-<12 hex char> Moduar Messaging does not distinguish between uppercase and owercase etters. To obtain the Host ID for Moduar Messaging: 1. Run the Voice Mai System Configuration utiity (VMSC). VMSC is instaed as part of the Messaging Appication Server (MAS) system toos. Ony designated Moduar Messaging System Administrators can run VMSC. VMSC dispays the system configuration. 2. Right-cick Licensing and choose Copy Host ID to Cipboard from the pop-up menu. 3. Paste the Host ID from the cipboard in to a text editor, an e-mai message, or a Web form, as required. 48 Avaya Remote Feature Activation (RFA) User Guide

49 Understanding Host IDs Persona WorkSpace For Persona WorkSpace the Host ID is the Media Access Contro Address (MAC) of the first Network Interface Card (NIC) in the WebLM server. For more information on how to find a Host ID using WebLM see Understanding Host IDs on page 44. Unified Communication Center For Unified Communication Center (UCC), the Host ID is the MAC of the first NIC in the icense server. For WMA or WCA the Host ID is the MAC Address of the first NIC in the UCC Base Server. For ASA ony, the Host ID is the MAC address of the first NIC in the ASA Server or UCC Speech Server. The Host ID is incuded in the UCC icense fie to ensure that each icense fie ony works with one UCC. If the Host ID in the icense fie does not match the MAC address of the NIC card, the UCC appications do not work. To find the Host ID for UCC: Start your browser and type the appropriate URL for the UCC License Server. Use the foowing format: For the variabe cvanhostname substitute the name of your CVLAN server. For the variabe port substitute the port number of the CVLAN server. For exampe: The browser dispays the Avaya WebLM page. The WebLM page contains the Host ID for the UCC. Voice Sef Service For Voice Sef Service, the Host ID is the MAC of the first NIC in the WebLM server. For more information on how to find a Host ID using WebLM see Understanding Host IDs on page 44. Issue 5.0 September

50 Getting Started Accessing RFA This section expains the computer and user requirements needed to access RFA. Computer requirements Before you attempt to access RFA, verify that your computer has: Internet Exporer 5.0 or ater 128-bit encryption Internet access to the RFA web site at A supported monitor resoution of 800 X 600 User requirements An RFA user must meet the foowing requirements: Be either: - An Avaya associate or contractor with a vaid Avaya Human Resources Identification (HR ID) number. - An approved BusinessPartner with a vaid BusinessPartner number. - An Avaya contractor who works with Avaya. Be a registered and authenticated RFA user: - To be registered in RFA means you have a Singe Sign-On (SSO) ogin and you have registered for each product famiy in which you wish to create a icense fie. If you do not aready have a SSO ogin see The SSO ogin on page To be authenticated in RFA means you have successfuy registered and your Avaya coach or Group Authorization Identification (GAI) manager approved your access to RFA. See Group Authorization Identification (GAI) on page 26 for information on GAI. Read and understand this guide. 50 Avaya Remote Feature Activation (RFA) User Guide

51 The SSO ogin The SSO ogin After you type in your browser window, the system prompts you to enter a SSO ogin and password. If you are an Avaya BusinessPartner, the SSO ogin is the same ogin and password that you use to access the BusinessPartner porta or the ATAC. If you aready have a ogin to one of these sites you do not need to create a new ogin. If you do not have an SSO ogin see Creating a SSO ogin on page 51. If you are an Avaya empoyee, you do not need to register for a SSO ogin. You can use your goba NT ogin and password. Creating a SSO ogin Use the foowing steps to create an SSO ogin: 1. Type in your browser window. The system dispays the Avaya SSO Login screen (Figure 13). Figure 13: Avaya SSO Login screen Issue 5.0 September

52 Getting Started 2. In the Log In window cick Register Now. The system dispays the Terms of Use screen. 3. Read the information in the screen. If you agree to the terms of use, cick I Accept. You can not register if you do not accept the terms of use. The system dispays the Site Registration screen. 4. Compete the mandatory fieds on the Site Registration screen. 5. When you have competed the mandatory fieds, cick Register. Logging in to RFA Use the foowing steps to og in to RFA: 1. Verify that you have the correct computer requirements before you attempt to access RFA. For more information on computer requirements see Accessing RFA on page To access the RFA website type from your browser window. 3. Enter your SSO ogin and password. For more information on the SSO ogin see Registering for RFA product famiies on page 53. The system dispays the RFA Information Page. The RFA Information page contains the foowing: Information for the first time user A ink to this guide Hep information - Job aids - Frequenty asked questions - RFA news - Hep desk information - RFA job function descriptions for Avaya associates The foowing downoadabe software toos and associated documentation: - Feature Extraction Too (FET) for pre R10 Avaya DEFINITY Servers - License Instaation Too (LIT) for Avaya DEFINITY Servers A ink that you can use to register for an RFA product famiy A ink that you can use to access the RFA Appication Main Menu 52 Avaya Remote Feature Activation (RFA) User Guide

53 Registering for RFA product famiies Registering for RFA product famiies You must compete the foowing procedure to register for each product famiy in which you want to create a icense fie. You can ony register for one product famiy at a time. Once you are authenticated for one product famiy, you can register for another. RFA is in the process of expanding support for many products and product famiies. For current product famiy information see the RFA Information page or Getting Started With Remote Feature Activation (RFA) at support.avaya.com. Registration for Avaya Associates If you are an Avaya associate, use the foowing steps to register for a product famiy: 1. Log in to the RFA web site at The system dispays the RFA Information Page. 2. Cick Register to Use RFA for a product famiy 3. From the drop-down menu, seect the product famiy: a. Seect the job function that most cosey resembes the job function that you perform. For a detaied description of each job function, go to the RFA Information Page and cick on RFA Job Function Descriptions. b. Compete the required information and cick Submit. c. Your supervisor automaticay receives an e-mai message that he or she must approve before you can become an RFA user. Registration for Avaya BusinessPartners If you are an Avaya BusinessPartner, use the foowing steps to register for an RFA product famiy. 1. Log on to the RFA web site at If you aready have a SSO ogin, type the ogin and the password. If you do not have a SSO ogin, cick New User and compete the required information. The system dispays the RFA Information Page. 2. Cick Register to Use RFA for a product famiy Issue 5.0 September

54 Getting Started 3. From the drop-down menu seect your user type. - Tier 1 BusinessPartner if you purchase directy from Avaya. - Tier 2 BusinessPartner if you purchase from a Tier 1 BusinessPartner. - Contractor if you are a contractor with Avaya and do not have an Avaya HRID number. 4. Enter your Group Authorization Identification (GAI) number. The GAI was distributed to BusinessPartner principes. Cick Show GAI Name to verify that you are entering the correct GAI. For more information on GAI, see Group Authorization Identification (GAI) on page The authorization e-mai address that your company provided to Avaya receives the RFA generated authorization e-mai message. This message contains the request to authorize you for RFA access. Avaya must receive a repy to the authorization e-mai message before you can become an authenticated RFA user. Accessing the RFA Appication Main Menu for a product famiy Use the foowing steps to access the RFA Appication Main Menu for an RFA supported product: 1. Type in your browser window. The system dispays the SSO ogin window. 2. Log in to RFA using your SSO ogin and password. The system dispays the RFA Information page. 3. From the RFA information page, cick Start RFA Appication. The system dispays the terms of use and privacy statements. 4. To agree to the terms of use and privacy statements, cick I agree. The system dispays the product famiy seection window. 5. Seect the product famiy from the drop-down menu. 6. Perform one of the foowing actions: a. If you want to set this product famiy as your defaut famiy, cick Login and Set Defaut Product Famiy. This product famiy now appears as your defaut product famiy every time you og in to RFA. b. If you do not want to set this product famiy as your defaut famiy, cick Login. The system dispays the RFA Appication Main Menu for the product famiy you seected. 54 Avaya Remote Feature Activation (RFA) User Guide

55 RFA Hep RFA Hep There may be times when you need hep with RFA or with a RFA icense fie. The organization that you ca for hep depends on the type of probem you are experiencing. Tabe 6 shows exampes of the types of probems for which each Hepdesk provides support. Tabe 6: RFA support information Organization What they support The IT Hepdesk The RFA appication, such as: - SSO ogins and passwords - RFA navigationa support such as screens, error messages, and so on. - Mistakes made in the RFA system record such as using the wrong SAP order number or the wrong seriaized hardware component in the system record. Probems with the SAP order number or creation of the transaction record. Downoading the FET or LIT Probems with system records such as creating, ocating, and accessing a system record. The Avaya Services Hepdesk The icense fie or the authentication fie(s) such as: Getting the icense fie in to the Avaya product incuding reading the error messages and providing soutions FET and/or LIT interactions with DEFINITY License-Error mode and No-License Mode The inabiity to connect to DEFINITY using Connect2 Important:! Important: If you are having troube with the RFA appication, or creating a icense fie or an authentication fie, ca the IT Hepdesk. If you need hep instaing a icense or an authentication fie, or if you are having troube with a icense or an authentication fie that is aready instaed, ca the Avaya Services Hepdesk. Issue 5.0 September

56 Getting Started Tabe 7 shows the Hepdesk group to contact and the Hepdesk s contact information for RFA appication support. Tabe 7: Hepdesk information Groups Contact United States and Canada Avaya associates Members of one of the Variabe Workforce Groups Avaya Contractors Avaya BusinessParters For urgent matters ca or (303) For ess urgent matters with an expected 48 hour (or more) response time send an e-mai message to [email protected]. A internationa caers No anguage support: or (303) Language support: Contact your regiona support center. Support center contact information see jappe/css/ jappe?page=avaya.css.openpage&temp.te mpate.name=escaations_goba 56 Avaya Remote Feature Activation (RFA) User Guide

57 Chapter 2: The RFA Appication Main Menu About this chapter This chapter expains the options that are avaiabe from the RFA Appication Main Menu. Later chapters describe these options in more detai. Accessing the RFA Main Menu You can access the main menu for a product famiy once after you receive approva. To access the main menu screen: 1. On the RFA Information page, cick Start RFA Appication. 2. Read the contents of the discaimer box and cick I agree. 3. Seecting the product famiy from the drop-down ist. The system dispays the main menu for that product famiy. The main menu screen varies depending on the product famiy. Figure 14 shows an exampe of the Communication Manager product famiy main menu. Figure 14: RFA Appication Main Menu screen Issue 5.0 September

58 The RFA Appication Main Menu Left side of the main menu The eft side of the main menu contains options that hep manage your information, view deivery status of fies, and view the status of a configuration fie upoad (DEFINITY ony). Figure 15 shows an exampe of the options on the eft side of the main menu for Communication Manager. Remember, the options on the eft side change sighty depending on the product famiy that you are ogged in to. Figure 15: Exampe of the eft side of the main menu for Communication Manager The options on the eft of the main menu can be different depending on the product famiy. This section describes a possibe options. My RFA Authorization Information Cick My RFA Authorization Information to request a change for: Avaya associates, your job function. Avaya BusinessPartners, your assigned Group Authorization Identifier (GAI). For more information see My RFA Authorization Information on page 58. View My Fie Deivery Status Cick View My Fie Deivery Status to determine if a fie was deivered or if there was an error. For more information see Chapter 7: Viewing The Deivery Status Of A Fie on page 163. View My Upoaded Switch Config Fie Status (Communication Manager ony) Cick View My Upoaded Switch Config Fie to determine if a switch configuration fie was upoaded to RFA or if there was an error. This option ony appears when you are ogged in to the Communication Manager product famiy. For more information see Chapter 7: Viewing The Deivery Status Of A Fie on page Avaya Remote Feature Activation (RFA) User Guide

59 Accessing the RFA Main Menu Work With My Pending Transaction Records Cick Work With My Pending Transaction Records to find and resume work on a transaction record. For more information see Chapter 9: Working With Transaction Records on page 171. Work With My Pending System Records (Communication Manager ony) Cick Work With My Pending System Records to find and change seected fieds in a system record. This option is avaiabe ony for the Communication Manager product famiy. For more information see Chapter 10: Working With System Records on page 177. Center of the main menu The center of the RFA Appication Main Menu contains options to create or modify RFA records and deiver fies. Figure 16 shows an exampe of the center of the Communications Manager RFA Appication Main Menu. Figure 16: Exampe of the center of the main menu for Communication Manager The options in the center of the main menu can be different depending on the product famiy. This section describes a possibe options. New Insta and Migrations Pre R10 New Insta and Migrations Pre R10: A Migrations Pre R10 and a New Insta are on the same main menu seection. Systems migrating from a pre R10 reease do not have any information in RFA and are seen by RFA as a new insta. Maintenance Swap-Outs - Use the Swap-Out capabiity when you must repace the component that contains the seria number or Host ID that was used in the RFA icense. The Seria Number Swap-Out capabiity is used for the Communication Manager, the Security Gateway, and the Branch Gateways product famiies. Issue 5.0 September

60 The RFA Appication Main Menu Switch Updates from Pre R10 - Use the Switch Updates from Pre R10 capabiity when you are updating Communication Manager from a reease that is pre R10. Switch Updates from R10+ - Use the Switch Updates from R10+ capabiity when you are updating Communication Manager from a reease that is ater than Reease 10. PCN Update from Pre R10 - Use the PCN Update from Pre R10 capabiity when you are updating a Communication Manager server using a PCN update and the server is running a Communication Manager version that is pre-reease 10. Change Host ID - Use the Change Host ID functionaity when you must repace the hardware component to which the Host ID beongs. The Change Host ID capabiity is used for a the product famiies that use the Host ID for identification. Support Upgrade - Use the Support Upgrade functionaity when you must update the system due to a software issue. Support Upgrades are for the Communication Manager product famiy ony. Additions The Additions menu item appears for Contact Center, Security Gateway, and Softcients. Use the Additions seection when you are adding functionaity, capacity, or modues to the system. Upgrades and Additions The Upgrades and Additions menu item appears for a product famiies except Communication Manager, Contact Center, Security Gateway, Enterprise Communication Manager, and Softcients. Use either Upgrades or Additions when adding functionaity, capacity, or modues to a system. Additions, Upgrades and Migrations (Communication Manager) The Additions, Upgrades and Migrations seection dispays when you are working with the Communication Manager product famiy ony. Cicking on Additions, Upgrades, and Migrations resuts in the foowing seections: Additions, Upgrades R10+, and Migrations R10+ Upgrades from Pre R10 RFA Record Updates Use the RFA Record Updates capabiity to find and change a system record. 60 Avaya Remote Feature Activation (RFA) User Guide

61 Accessing the RFA Main Menu Deiver Fies Use the Deiver Fies capabiity to deiver the icense fie by way of an e-mai message or a downoad. A Direct Connection option is avaiabe for DEFINITY servers ony. Right side of the main menu The right side of the RFA Appication Main Menu contains options that you use to: Search for a System Identification (SID) number or a transaction number. Change product famiies (if you are approved for more than one product famiy). Exit from the RFA appication. Figure 17 shows an exampe of the options on the right side of the main menu for Communication Manager. Figure 17: Exampe of the right side of the main menu for Communication Manager Search/View Menu Use the Search/View menu to search for a SID or a transaction. Figure 18 shows an exampe of the Search/View menu screen. Figure 18: Search/View menu screen Issue 5.0 September

62 The RFA Appication Main Menu You can search for a SID or transaction number by entering information in the appropriate fieds, and cicking GO. This is the most efficient method to find a record. You can aso cick Advanced Search if you want to search using the one of the foowing parameters: Transaction Number (Fu vaue) SID (Fu vaue) Seria Number or Host ID (Fu vaue) Dia-in Teephone Number (Fu vaue): Used for Communication Manager ony IP Address (Fu vaue): Used for Communication Manager ony Sod to Customer Name (Partia or fu vaue) Tier I BusinessPartner Name (Partia or fu vaue) Tier II BusinessPartner Name (Partia or fu vaue) End Customer Name (Partia or fu vaue) Patform Type (fu vaue) SAP order number (Fu Vaue) Maintenance Troube Ticket # (Fu vaue) Appication PID (Fu vaue): Used for Communication Manager ony Patform PID (Fu vaue): Used for Communication Manager ony Not every advanced search option is avaiabe for a product famiies. Change Product Famiy Exit RFA The Change Product Famiy option is at the top of the RFA Appication Main Menu. Use the Change Product Famiy capabiity to change product famiies without the need to og off and back on to RFA. To seect the product famiy from the ist, cick the drop-down arrow. To cose the RFA Appication Main Menu, cick Exit RFA. 62 Avaya Remote Feature Activation (RFA) User Guide

63 Chapter 3: New Insta About this chapter The information in this chapter expains how to create a icense fie for a product that does not have a system record in RFA. The RFA New Insta capabiity is used for a product famiies. The Security Gateway product famiy is equipped with a defaut icense fie. You do not need to create a icense fie for a Security Gateway unti you add additiona capabiities. For more information on the Security Gateway product famiy see Security Gateway on page 245. Before you start You must have the foowing information before you access RFA: The customer impementation package The SAP order number with the: - Appropriate materia codes for the Right To Use (RTU) - Hardware codes that are used for dupication, if appicabe - Hardware materia codes and the software materia codes or software-ony materia codes You cannot use the same SAP order number to generate mutipe icenses for the same product famiy. You must have one SAP order number for each product. The GAI for any BusinessPartner who might need access to the system record. The name, address, teephone number, and contact name for the Tier I, Tier II BusinessPartner, and the customer. Deivery method information: - If the fie is deivered by way of an e-mai message, the e-mai address - If the fie is deivered by way of the Direct Connection method for an Avaya DEFINITY Server, the IP address or teephone number Issue 5.0 September

64 New Insta The seria number if this is a Communication Manager system, a Branch Gateway, or a Security Gateway. See Understanding seria numbers on page 39 for more information on obtaining a seria number. For a other product famiies, the Host ID. For more information on obtaining a Host ID see Understanding Host IDs on page 44. Procedures for a new insta Use the new insta procedure to create an RFA icense fie for a new server or a server that has never had an RFA icense fie. Ensure that you are ogged in to the correct product famiy before you start. If you do not seect the correct product famiy, you receive unexpected errors and cannot compete the transaction. High-eve steps The foowing ist summarizes the steps that you must perform to create a icense fie for the first time: 1. In the RFA Appication Main Menu, cick New Insta (Step 1: Start from the RFA Appication Main Menu on page 65). 2. Enter the SAP order number (Step 2: Enter the SAP order number on page 65). 3. Verify that the SAP order data is correct (Step 3: Verify that the SAP order data is correct on page 67). 4. Record the transaction number (Step 4: Record the transaction number on page 68). 5. Compete the customer and genera system information (Step 5: Compete the customer and genera system information on page 68). 6. Compete the detai information for the modue and appication (Step 6: Compete the Modue and Appication Detais information on page 71). 7. Compete the feature information (Step 7: Compete the feature information on page 75). 8. Compete the transaction (Step 8: Compete the transaction on page 77). 9. Record the SID and the SID version number (Step 9: Record the SID and the version number on page 78). 10. Deiver the icense fie (Step 10: Deiver the icense fie on page 78). The foowing section provides the detaied instructions for each of these steps. 64 Avaya Remote Feature Activation (RFA) User Guide

65 Procedures for a new insta Detaied steps Before you start on the foowing instaation steps, verify that you have accessed the RFA Appication Main Menu for the correct product famiy. For more information on how to access RFA, see Accessing RFA on page 50. Step 1: Start from the RFA Appication Main Menu From the center of the RFA Appication Main Menu, cick New Insta. The system dispays the SAP order number screen (Figure 19). Figure 19: SAP order number screen Step 2: Enter the SAP order number Enter the SAP order number in the text fied and cick Retrieve. The SAP order number must be between 1 and 10 digits. Important:! Important: Use the SAP order number that incudes the software right to use (RTU) materia codes and the hardware materia codes that are used for dupication. Do not use the SAP order number that incudes hardware materia codes ony. If software codes exist on more than one SAP order, use the SAP order number that contains the main serving vehice to create the system record. Then use the subsequent SAP order numbers and foow the process for each SAP order. In this situation, you first create and then modify the system record. You can use a singe SAP order number mutipe times, as ong as you appy the number to different product famiies. For exampe, when you insta a Converged Communications Server and a Communication Manager server, you can use a singe SAP order number to generate both icense fies for the Communication Manager server and the Converged Communications Server. Issue 5.0 September

66 New Insta If the SAP order number is vaid, the system dispays the SAP Order Data screen. If the SAP order number is not vaid, or if there are probems with the order number, the system dispays an error message. See Tabe 8 for information on SAP error messages. Tabe 8: SAP error messages Error messages Description Action The SAP order number is invaid. The SAP order number does not contain any software materia codes. You do not have permission to access the SAP order information. The SAP order number that you entered is aready in use for this product famiy. You can continue to work on the transaction record but cannot use this SAP order number to generate a new icense fie. The SAP order number does not contain the materia codes for the icensing of the product famiy for which you are buiding the icense. The SAP order number does not contain the materia codes that you need to icense this product. This error message might appear to BusinessPartners who try to access a system record that does not contain their GUI. The SAP order number is aready in use in RFA to generate a icense for this product famiy. Ensure that you have ogged in to the correct product famiy and that you have the correct materia codes. If the product famiy and the materia codes are correct, contact the RFA Hepdesk. Contact the ordering team. For more information see Group Authorization Identification (GAI) on page 26. Ensure that you are ogged in to the right product famiy for the materia codes on your SAP order. If the product famiy is correct, a new SAP order number must be created to generate a icense. Contact the ordering team. 66 Avaya Remote Feature Activation (RFA) User Guide

67 Procedures for a new insta Step 3: Verify that the SAP order data is correct After you cick Retrieve, the system dispays the SAP Order Data screen. The product you are working on may rey on features that must be enabed on other product famiies. For a ist of product feature dependencies, cick the Licensing Dependency Tabe ink at the top of the screen. It is recommended that you use the information in this chart to ensure that you have a the features enabed that integrate with the product famiy you are working on. Review the SAP order data to ensure that the foowing information is correct: Sod To Customer Information The quantity, the materia code, and the description Information The information in the SAP Order screen ony shows the materia codes for the items that must be incuded in the icense fie such as the reease, the category, the features, and the capacities. This screen might not show everything that was ordered. If a the SAP Order Data is correct, cick Accept. Cick Back if the SAP order data on this screen is for the wrong customer, or does not incude the software RTU materia codes and the hardware materia codes for dupication.! Important: Important: If the SAP Order Data shows the information for the correct customer, but either the customer information or the materia code is incorrect, do not continue. Contact the account team immediatey. The SAP order information must be correct before you create and deiver the icense fie. After you cick Accept, the system dispays a transaction number (Figure 20). Figure 20: Transaction Number screen Issue 5.0 September

68 New Insta Step 4: Record the transaction number Record the transaction number that appears in the screen. You wi need this number ater. After you record the transaction number, cick Continue. The system dispays the Customer and Genera System Information screen. Step 5: Compete the customer and genera system information Step 5 has two parts: Step 5a: Compete the GAI tabe on page 69 Step 5b: Compete the BusinessPartner and customer information on page Avaya Remote Feature Activation (RFA) User Guide

69 Procedures for a new insta Step 5a: Compete the GAI tabe Compete the GAI fieds as appropriate: If you are an Avaya associate, do not add a GAI in the ist uness you are starting a transaction that a BusinessPartner wi compete. You must add the GAI for any BusinessPartner who needs access to this record. If you are a Tier I BusinessPartner, your GAI is aready on this ist from the SAP order. You must add the GAI for any Tier II BusinessPartner who needs access to this record.! CAUTION: CAUTION: If you make changes on this screen you must cick Submit before you go to another screen. If you do not cick Submit your changes are ost. Figure 21: Customer and Genera System Information screen Issue 5.0 September

70 New Insta Step 5b: Compete the BusinessPartner and customer information Compete the Tier I BusinessPartner Information, Tier II BusinessPartner Information, and End User Customer Information fieds as appropriate: If this is a direct order, compete ony the End User Customer Information fieds. Cick Same As Sod To above the End User Customer Information fieds to copy the SAP Sod to Customer Information from the top of the screen. Then compete any empty fieds. If this is a BusinessPartner order, compete a three coumns. Since the Tier I BusinessPartner is probaby aso the Sod To Customer, cick Same As Sod To above that coumn to copy the SAP Sod To Customer Information. Then manuay enter the necessary information for the Tier II BusinessPartner and the customer. Figure 22: Customer Information Screen Tier I, Tier II, and customer information You must enter a name in the Point of Contact s Name fied before you can compete the transaction. On the bottom of the Customer Information screen: Cick Submit if you have correcty fied out a the necessary fieds Cick Cear Form to cear the fieds and start again Cick SAP Order Data to view the SAP data that is associated with this icense fie After you cick Submit, the system dispays a window and asks if you want to continue. Cick OK to continue. The system dispays a Customer and Genera System Information screen with a message containing the status of your updates. 70 Avaya Remote Feature Activation (RFA) User Guide

71 Procedures for a new insta Step 6: Compete the Modue and Appication Detais information Cick the Modue/App Detais tab. The system dispays the Modue and Appications Detais screen (Figure 23). See Figure 24 for an exampe of the Host ID Information tabe. Figure 23: Modue and Appications Detais screen for Communication Manager Figure 24: The Host ID information tabe on the Modue and Appications Detais screen Step 6 has two parts: Step 6a: Review and change (if needed) the tabe information on page 72 Step 6b: Seect any additiona modues from the drop-down menu on page 74 Issue 5.0 September

72 New Insta Step 6a: Review and change (if needed) the tabe information If needed, change or update the appropriate tabes in the Modue and Appications Detais screen. Fieds in the Modue Information tabe change sighty depending on the product famiy. The Modue Information Tabe: - The foowing ist describes each fied in the Modue Information tabe: Modue ID - This fied contains the modue ID number for this product or appication. The Modue ID is aways 1 if: - This is the main server for Communication Manager. - This order does not contain mutipe modues. - The product famiy does not support mutipe modues. Modue Type - This fied contains a description of the modue type. Patform Type - The patform type identifies the type of hardware that this product uses. Modue Description (optiona but recommended) - Enter a name or a description to hep identify this modue such as "South Campus". Modue Location (optiona but recommended) - Enter a ocation to hep identify this modue such as "Room B2H10". IP Address (Communication Manager ony) - Enter the Internet Protoco (IP) Address for this modue if you want RFA to deiver the icense fie over a oca area network (LAN). Dia-in Teephone Number (Avaya DEFINITY servers ony) - Enter the teephone number for this modue if you want to use the RFA Direct Connection option over the INADS port to deiver the icense fie. Information that you enter in this fied automaticay appears in the dia-in teephone fied when you request deivery of a fie by way of the Direct Connection option. You must enter the teephone numbers in one of the foowing formats: - For the United States and Canada; +1 XXX XXX XXXX - For a other countries; +Country Code CityCode LocaPhoneNumber, Extension. Commas and extensions are optiona. Athough you cannot use the Direct Connection option with the Avaya S8000 series servers, you can enter the S8000 series dia-in teephone number in this fied. You can use the S8000 series dia-in teephone number with the search functionaity to find transaction or system records. E-mai Address - Enter the e-mai address if you want RFA to use e-mai to deiver the icense fie. Information that you enter in this fied automaticay appears in the e-mai address fied when you request the downoad of a fie by way of e-mai. 72 Avaya Remote Feature Activation (RFA) User Guide

73 Procedures for a new insta Deivery Instructions - Enter notes on how you want the icense fie for this modue to be deivered. RFA does not use this information. This information is for the use of peope who compete the transaction or deiver the fie. For more information on how to deiver a icense fie see Chapter 6: Deivering A Fie From RFA on page 153. Seria Number or Host ID Information Tabe - Depending on the product famiy, a Seria Number Information tabe or a Host ID Information tabe appears in the Modue/Appications screen. You must enter the correct seria number or Host ID for the Avaya server where the icense fie is to be instaed. The icense fie can t operate on a system that does not contain the correct seria number or Host ID. Type the foowing data in either the Seria Number Information tabe or the Host ID Information tabe: Enter the seria number or the Host ID. Confirm the seria number or Host ID: The seria number or the Host ID must match the data that you entered in the seria number or Host ID fied. When you use dupication for DEFINITY, the system prompts for seria numbers of both the A and the B SPE. Retrieve SN - If you are working on an Avaya DEFINITY server you have the option to have RFA retrieve the seria number from the processor board. To use this option, the software on the DEFINITY server must be Reease 9 or ater, and you must have dia-up connectivity. Use the foowing steps to enter data in the Retrieve SN fied: 1. Next to the seria number fied, cick Retrieve SN. 2. In the Dia-in Teephone Number fied, enter the dia-in teephone for the system. If a dia-in teephone number exists in the Modue Information tabe, that number automaticay appears in the Dia-In Teephone Number fied. 3. Cick Submit to connect to the system and retrieve the seria number. WARNING:! WARNING: The retrieve seria number process can take up to six minutes to compete. You can cick Cance this Request at any time to return to the Modue/Appication Detais screen from where you can enter the seria number manuay. 4. Once approved, the seria number is entered in the Seria Number fied in the Seria Number tabe. Issue 5.0 September

74 New Insta Appication Information Tabe - You do not need to compete the fieds in the Appication Information tabe. Appication - Contains the name of the product or appication that you are instaing. This fied is pre popuated using the information on the SAP order. Expiration Date - This fied is reserved for future enhancements. Appication PID (Communication Manager ony) - This number is assigned when registering the system for aarming. This fied is not required to create a icense fie. Reease Version - This fied identifies the version of the software. This fied is pre popuated with the information on the SAP order. To enter any changes that you made on this screen, cick Submit. The system dispays the Modue/Appication Detais screen with the status of the updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. When you cick Submit, RFA checks the Host ID and the seria number to see if the Host ID and the seria number are vaid. RFA generates an invaid Host ID message if the Host ID aready exists in another RFA icense within this product famiy. RFA generates an invaid seria number if the seria number has an invaid status or is active in another Communication Manager system. See Tabe 9 if RFA dispays a message that the Host ID or if the seria number is invaid. Tabe 9: Invaid seria number or Host ID tabe Invaid seria number For Communication Manager - Ensure that you are obtaining the seria number from the correct processor board, IPSI circuit pack, or MSSNET board. Ensure that you read the seria number correcty. Ensure that you entered the seria number correcty. If the seria number does not work the second time contact the RFA Hepdesk. Invaid Host ID Ensure that you are obtaining the MAC address of the first port on the first Network Interface Card (NIC). Ensure that you are reading the Host ID correcty. Ensure that you entered the Host ID correcty. If the Host ID does not work the second time you must obtain a new NIC with a MAC address that is not aready icensed in RFA. Step 6b: Seect any additiona modues from the drop-down menu Some Avaya systems contain more than one modue or appication. Use the drop-down menu that is beow the tab bar to view and seect additiona modues or appications. If this is a Communication Manager instaation with mutipe modues, you must enter the seria number information for each modue that you seect. For Unified Communications Center (UCC), you do not need to enter any additiona information. The information that you submit for one appication is automaticay copied to the other appication screens. 74 Avaya Remote Feature Activation (RFA) User Guide

75 Procedures for a new insta Review and if necessary, change or update the tabe information according to the instructions in Step 6a: Review and change (if needed) the tabe information on page 72. To enter any changes, cick Submit. The system dispays the Modue/Appication Detais screen with a message about the status of the updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. Step 7: Compete the feature information Starting in RFA Reease 9.0, the Features screen wi contain a Shared Features coumn for muti-modue Communication Manager systems. You wi not see the Shared Features coumn on transactions prior to RFA Reease 9.0. Cick the Features tab. The system dispays the Features Information screen (Figure 25). The Keyword Description coumn and the Keyword coumn can now be sorted aphabeticay by cicking on the individua coumn heading. After cicking the coumn heading, the coor changes from bue to purpe. A hep screen is provided by cicking the Changing the Feature Sort ink on the top of each tabe type. Cicking on the coumn heading sorts the information in a the tabes on the Feature screen. Issue 5.0 September

76 New Insta Figure 25: RFA Reease 9 Features screen for Communication Manager If you are unfamiiar with the Features Information screen, see Understanding the Features tab on page 30. If you are aready famiiar with the tabes, continue with step 7. Step 7 has two parts: Step 7a: Make any necessary changes for the first modue on page 76 Step 7b: Make any necessary changes for the next modue on page 77 Step 7a: Make any necessary changes for the first modue Verify that the tabes in the Feature Information screen are correct. If not, make the necessary changes to the information. If the system contains more than one modue, use the drop-down menu to appy the changes to this modue ony or appy the changes to a modues. You must cick Submit if you make any changes to the feature information. After you cick Submit the system dispays the Feature Information screen with the status of the updates. 76 Avaya Remote Feature Activation (RFA) User Guide

77 Procedures for a new insta Feature dependency is vaidated when a change is made on the feature screen and before a transaction is competed. Vaidation ensures that the features are set correcty before you insta a icense fie. Step 7b: Make any necessary changes for the next modue If this system contains more than one modue, use the drop-down menu to seect the other modues. Then make any necessary changes to the feature information for the next modue in the ist. Cick Submit after you make any changes. Repeat these steps unti you change and submit the feature information for a the modues in the system. After you enter the information for each modue and cick Submit, the system dispays the Feature Information screen with the status of the updates. Step 8: Compete the transaction Cick the Compete Transaction tab. The system dispays the Compete Transaction screen (Figure 26). Figure 26: Compete Transaction screen Before you can compete the transaction, you must verify that you reviewed the feature settings on a the modues and agree that the settings are correct. Verify that you reviewed the feature settings by seecting the box next to the statement. Cick Submit to compete the transaction. If you are not ready to compete the transaction you can eave the screen by cicking on one of the foowing: A different tab A different item on the RFA Appication Main Menu Issue 5.0 September

78 New Insta Important:! Important: Unti you compete the transaction, you have the option to deete the transaction. Once you compete the transaction the transaction becomes a permanent system record. You cannot deete a system record from RFA. Step 9: Record the SID and the version number After cicking Submit on the Compete Transaction screen, the system dispays a window asking if you want to compete the transaction. If you want to continue, cick Ok. The system dispays a System Identification screen (Figure 27). Figure 27: System Identification screen Record the SID and the version number. The SID is a pointer to the system record in the RFA database.you need the SID to obtain the icense fie from RFA. Cick OK to cose the window or cick Print to print the window. After you cick OK, the system dispays the RFA Appication Main Menu. Step 10: Deiver the icense fie You must deiver the icense fie from RFA to the Avaya server or to a computer. For more information on deivering a icense fie see Chapter 6: Deivering A Fie From RFA on page Avaya Remote Feature Activation (RFA) User Guide

79 Chapter 4: Additions About this chapter This chapter expains how to create a icense fie that contains additiona features or additiona modues. The procedure for adding additiona features is the same for a product famiies. Tip: Tip: This chapter contains steps that are in previous chapters. The steps are repeated so that the additions procedure is compete and can be downoaded or printed separatey from the rest of this document. Before you start You must create a new version of the current icense fie to add additiona capacity of feature functionaity to a system. You begin the additions procedure from the RFA Appications Main Menu. Before you start, you need the foowing information: The SAP order number The SID The GAI for any BusinessPartner who might need access to this record The name, the address, the teephone number, and the contact name for the Tier I and Tier II BusinessPartner and the customer, as appropriate A deivery method: - Communication Manager ony An IP address A dia-in teephone number - An e-mai address An option to deiver the RFA fie to a computer is aways avaiabe in RFA. You do not have to provide any information in RFA for this option. Issue 5.0 September

80 Additions Addition procedure to add a feature or a modue Use this procedure when adding a new feature or an additiona modue to the system. Ensure that you are ogged in to the correct product famiy before you start. If you do not seect the correct product famiy, you receive unexpected errors and cannot compete the transaction. High-eve steps The foowing ist summarizes the steps that you must perform to create a icense fie for an addition: 1. In the RFA Appication Main Menu, - For Communication Manager: Cick Upgrade and Additions or Additions (Step 1: Start at the RFA main menu on page 81). - For a other product houses: Cick either Additions or Additions and Upgrades (Step 1: Start at the RFA main menu on page 81). The Enterprise Communication Manager product famiy does not support additions. 2. Enter the SAP order number and cick Retrieve (Step 2: Enter the SAP order number on page 82). 3. Verify that the SAP order data is correct and cick Accept (Step 3: Verify that the SAP order data is correct on page 84). 4. Record the transaction number and cick Continue (Step 4: Record the transaction number on page 85). 5. Enter the SID number and cick Retrieve (Step 5: Enter the SID on page 85). 6. Verify the SID information and cick Accept (Step 6: Verify the SID information on page 85). 7. For a modue addition: Compete the Assign Patforms, Reeases, and Add Modues screen and cick Finish (Step 7: Compete the Assign Patforms, Reeases, and Add Modues screen on page 86). Skip step seven is this is an feature addition ony. 8. Update the customer and the genera system information (Step 8: Compete the Customer and Genera System information on page 86). 9. Update the modue and the appication detai information (Step 9: Compete the Modue and Appication Detais information on page 89). 80 Avaya Remote Feature Activation (RFA) User Guide

81 Addition procedure to add a feature or a modue 10. Update the feature information. Verify that the feature information incudes the additiona functionaity or the additiona capacity (Step 10: Compete the feature information on page 93). 11. Compete the transaction (Step 11: Compete the transaction on page 95). 12. Record the SID and the version number (Step 12: Record the SID and version number on page 96). 13. Deiver the icense fie (Step 13: Deiver the icense fie on page 96). The foowing section provides the detaied instructions for each of these steps. Detaied steps Use the foowing steps to add additiona features or additiona modues. Step 1: Start at the RFA main menu From the RFA Appication Main Menu seect one of the foowing: For Communication Manager, cick Additions, Upgrades or Migrations and cick Additions. For Branch Gateways, Contact Center, Enterprise Communication Manager, Security Gateway, and Softcients, cick Additions. For a other product houses, cick Upgrades and Additions. The system dispays the SAP Order Data screen (Figure 28). Figure 28: SAP Order Data Issue 5.0 September

82 Additions Step 2: Enter the SAP order number Type the SAP order number in the text fied and cick Retrieve. The SAP order number must be between 1 and 10 digits.! Important: Important: Use the SAP order number that incudes the software right to use (RTU) materia codes and the hardware materia codes that are used for dupication. Do not use the SAP order number that incudes hardware materia codes ony. If software codes exist on more than one SAP order, use the SAP order number that contains the main serving vehice to create the system record. Then use the subsequent SAP order numbers and foow the process for each SAP order. In this situation, you first create and then modify the system record. You can use a singe SAP order number mutipe times, as ong as you appy the number to different product famiies. For exampe, when you insta a Converged Communications Server and a Communication Manager server, you can use a singe SAP order number to generate both icense fies for the Communication Manager server and the Converged Communications Server. If the SAP order number is vaid, the system dispays the SAP Order Data screen. If the SAP order number is not vaid, or if other probems exist with the order number, the system dispays an error message. See Tabe 10 for information on SAP error messages. Tabe 10: SAP error messages Error Messages Description Action The SAP order number is invaid. The SAP order number does not contain any software materia codes. The SAP order number does not contain the materia codes for the icensing of the product famiy for which you are buiding the icense. The SAP order number does not contain the materia codes needed to icense the product. Ensure that you have ogged in to the right product famiy and vaidate that you have the right materia codes. If the product famiy and materia codes are correct, contact the RFA Hepdesk. Contact the ordering team. 1 of 2 82 Avaya Remote Feature Activation (RFA) User Guide

83 Addition procedure to add a feature or a modue Tabe 10: SAP error messages (continued) Error Messages Description Action You do not have permission to access the SAP order information. The SAP order number that you entered is aready in use for this product famiy. You can continue to work on the transaction record but cannot use this SAP order number to generate a new icense fie. This error message might appear to BusinessPartners trying to access a system record that does not contain their GUI. The SAP order number is aready in use in RFA to generate a icense fie for this product famiy. For information see Group Authorization Identification (GAI) on page 26. Ensure that you are ogged in to the right product famiy for the materia codes on your SAP order. If the product famiy is correct, a new SAP order number must be created to generate a icense. Contact the ordering team. 2 of 2 Issue 5.0 September

84 Additions Step 3: Verify that the SAP order data is correct After you cick Retrieve, the system dispays the SAP Order Data screen. The product you are working on may rey on features that must be enabed on other product famiies. For a ist of product feature dependencies, cick the Licensing Dependency Tabe ink at the top of the screen. It is recommended that you use the information in this chart to ensure that you have a the features enabed that integrate with the product famiy you are working on. Review the SAP order data to ensure that the foowing information is correct: Sod To Customer Information The quantity, the materia code, and the description Information The information in the SAP Order screen shows ony the materia codes for the items that must be incuded in the icense fie such as the reease, the category, the features, and the capacities. This screen might not show everything that was ordered. If a the SAP Order Data is correct, cick Accept. Cick Back if the SAP order data on this screen is for the wrong customer, or does not incude the software RTU materia codes and the hardware materia codes for dupication.! Important: Important: If the SAP Order Data shows the information for the correct customer, but either the customer information or the materia code is incorrect, do not continue. Contact the account team immediatey. The SAP order information must be correct before you create and deiver the icense fie. The system dispays the transaction number (Figure 29). Figure 29: Transaction Number screen 84 Avaya Remote Feature Activation (RFA) User Guide

85 Addition procedure to add a feature or a modue Step 4: Record the transaction number Record the transaction number that appears in the screen. You wi need this number ater. After you record the transaction number, cick Continue. The system dispays the Customer and Genera System Information screen. Step 5: Enter the SID Enter the SID for this Avaya system and cick Retrieve. After cicking Retrieve, the system dispays the SID Information screen (Figure 30). Figure 30: System Information (SID) screen Step 6: Verify the SID information Ensure that the information on the System Information screen is correct. Cick Accept if the information on the screen is correct. Cick Back to enter another SID. After you cick Accept, the system dispays the SID Accept Resuts screen. Cick Continue to continue with the transaction and activate the feature tabs. Issue 5.0 September

86 Additions Step 7: Compete the Assign Patforms, Reeases, and Add Modues screen Use step 7 if you are adding a modue. If you are adding new feature functionaity or increasing existing feature functionaity ony, the Assign Patforms, Reeases, and Add Modues screen does not appear. Skip step 7 and continue with step 8. For a modue addition, the Assign Patforms, Reeases, and Add Modues screen dispays after you accept the SID. The Assign Patforms, Reeases, and Add Modues screen dispays the SAP Order Detais information. RFA automaticay assigns the new modue(s) on an add modue ony operation. You cannot make any changes to this screen. Review the information and cick Finish. For more information on the Assign Patforms, Reeases, and Add Modues screen, see The Assign Patforms, Reeases, and Add Modues screen on page 266. Step 8: Compete the Customer and Genera System information Step 8 has two parts: Step 8a Compete the GAI tabe on page 86 Step 8b: Compete the BusinessPartner and End User Customer information on page 87 Step 8a Compete the GAI tabe Compete the GAI fieds as appropriate: If you are an Avaya associate, do not add a GAI in the ist uness you are starting a transaction that a BusinessPartner wi compete. You must add the GAI for any BusinessPartner who needs access to this record. If you are a Tier I BusinessPartner, your GAI is aready on this ist from the SAP order. You must add the GAI for any Tier II BusinessPartner who needs access to this record. 86 Avaya Remote Feature Activation (RFA) User Guide

87 Addition procedure to add a feature or a modue! CAUTION: CAUTION: If you make changes on this screen you must cick Submit before you go to another screen. If you do not cick Submit your changes are ost. Figure 31: Customer and Genera System Information Step 8b: Compete the BusinessPartner and End User Customer information Compete the Tier I BusinessPartner Information, Tier II BusinessPartner Information, and End User Customer Information fieds as appropriate: If this is a direct order, compete ony the End User Customer Information fieds. Cick Same As Sod To above the End User Customer Information fieds to copy the SAP Sod to Customer Information from the top of the screen. Then compete any empty fieds. If this is a BusinessPartner order, compete a three coumns. Since the Tier I BusinessPartner is probaby aso the Sod To Customer, cick Same As Sod To above that coumn to copy the SAP Sod To Customer Information. Then manuay enter the necessary information for the Tier II BusinessPartner and the customer. Issue 5.0 September

88 Additions Figure 32: Customer Information Screen Tier I, Tier II and End User Information You must enter a name in the Point of Contact s Name fied before you can compete the transaction. On the bottom of the Customer Information screen: Cick Submit if you have correcty fied out a the necessary fieds Cick Cear Form to cear the fieds and start again Cick SAP Order Data to view the SAP data that is associated with this icense fie After you cick Submit, the system dispays a window and asks if you want to continue. Cick OK to continue. The system dispays a Customer and Genera System Information screen with a message containing the status of your updates. 88 Avaya Remote Feature Activation (RFA) User Guide

89 Addition procedure to add a feature or a modue Step 9: Compete the Modue and Appication Detais information Cick the Modue/App Detais tab. The system dispays the Modue and Appications Detais screen (Figure 33). See Figure 34 for an exampe of the Host ID Information tabe. Figure 33: Modue/Apps Detais screen for Communication Manager Figure 34: Host ID Information Tabe on the Modue/Apps Detais screen Step 9 has two parts: Step 9a: Review and change (if needed) the tabe information on page 90 Step 9b: Seect any additiona modues from the drop-down menu on page 92 Issue 5.0 September

90 Additions Step 9a: Review and change (if needed) the tabe information If needed, change or update the appropriate tabes in the Modue and Appications Detais screen. Fieds in the Modue Information tabe change sighty depending on the product famiy. The foowing ist describes each fied in the Modue Information tabe: Modue ID - This fied contains the modue ID number for this product or appication. The Modue ID is aways 1 if: - This is the Main server for Communication Manager. - This order does not contain mutipe modues. - The product famiy does not support mutipe modues. Modue Type - This fied contains a description of the modue type. Patform Type - The patform type identifies the type of hardware that this product uses. Modue Description (optiona but recommended) - Enter a name or a description to hep identify this modue such as "South Campus". Modue Location (optiona but recommended) - Enter a ocation to hep identify this modue such as "Room B2H10". IP Address (Communication Manager ony) - Enter the Internet Protoco (IP) Address for this modue if you want RFA to deiver the icense fie over a oca area network (LAN). Dia-in Teephone Number (Avaya DEFINITY servers ony) - Enter the teephone number for this modue if you want to use the RFA Direct Connection option over the INADS port to deiver the icense fie. Information that you enter in this fied automaticay appears in the dia-in teephone fied when you request deivery of a fie by way of the Direct Connection option. You must enter the teephone numbers in one of the foowing formats: - For the United States and Canada; +1 XXX XXX XXXX - For a other countries; +Country Code CityCode LocaPhoneNumber, Extension. Commas and extensions are optiona. Athough you cannot use the Direct Connection option with the Avaya S8000 series servers, you can enter the S8000 series dia-in teephone number in this fied. You can use the S8000 series dia-in teephone number with the search functionaity to find transaction or system records. E-mai Address - Enter the e-mai address if you want RFA to use e-mai to deiver the icense fie. Information that you enter in this fied automaticay appears in the e-mai address fied when you request the downoad of a fie by way of e-mai. 90 Avaya Remote Feature Activation (RFA) User Guide

91 Addition procedure to add a feature or a modue Deivery Instructions - Enter notes on how you want the icense fie for this modue to be deivered. RFA does not use this information. This information is for the use of peope who compete the transaction or deiver the fie. For more information on how to deiver a icense fie see Chapter 6: Deivering A Fie From RFA on page 153. Cick Submit to save the information. If you enter information without competing the seria number or Host ID Information tabe, the system dispays a message that the non Host ID (or seria number) updates are successfu. Seria Number or Host ID Information Tabe - Depending on the product famiy, a Seria Number Information tabe or a Host ID Information tabe appears in the Modue/Appications screen. You must enter the correct seria number or Host ID for the Avaya server where the icense fie is to be instaed. The icense fie can t operate on a system that does not contain the correct seria number or Host ID. Type the foowing data in either the Seria Number Information tabe or the Host ID Information tabe: Enter the seria number or the Host ID. Confirm the seria number or Host ID: The seria number or the Host ID must match the data that you entered in the seria number or Host ID fieds. When you use dupication for DEFINITY, the system prompts for seria numbers of both the A and the B SPE. Retrieve SN - If you are working on an Avaya DEFINITY server you have the option to have RFA retrieve the seria number from the processor board. To use this option, the software on the DEFINITY server must be Reease 9 or ater, and you must have dia-up connectivity. Use the foowing steps to enter data in the Retrieve SN fied: 1. Next to the seria number fied, cick Retrieve SN. 2. In the Dia-in Teephone Number fied, enter the dia-in teephone for the system. If a dia-in teephone number exists in the Modue Information tabe, that number automaticay appears in the Dia-in Teephone Number fied. 3. Cick Submit to connect to the system and retrieve the seria number. WARNING:! WARNING: The retrieve seria number process can take up to six minutes to compete. You can cick Cance this Request at any time to return to the Modue/Appication Detais screen from where you can enter the seria number manuay. 4. Once approved, the seria number is entered in the Seria Number fied in the Seria Number tabe. Issue 5.0 September

92 Additions Appication Information Tabe - You do not need to compete the fieds in the Appication Information tabe. Appication - Contains the name of the product or appication that you are instaing. This fied is pre popuated using the information on the SAP order. Expiration Date - This fied is reserved for future enhancements. Appication PID (Communication Manager ony) - This number is assigned when registering the system for aarming. This fied is not required to create a icense fie. Reease Version - This fied identifies the version of the software. This fied is pre popuated with the information on the SAP order. To enter any changes that you made on this screen, cick Submit. The system dispays the Modue/Appication Detais screen with the status of the updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. Step 9b: Seect any additiona modues from the drop-down menu Some Avaya systems contain more than one modue or appication. Use the drop-down menu that is beow the tab bar to view and seect additiona modues or appications. If this is a Communication Manager instaation with mutipe modues, you must enter a seria number for each new modue that you seect. For Unified Communications Center (UCC), you do not need to enter any additiona information. The information that you submit for one appication is automaticay copied to the other appication screens. Review, and if necessary, change or update the tabe information as instructed in Step 9a. Cick Submit to enter any changes made on this screen.the system dispays the Modue/ Appication Detais screen with a message about the status of your updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. 92 Avaya Remote Feature Activation (RFA) User Guide

93 Addition procedure to add a feature or a modue Step 10: Compete the feature information Starting in RFA Reease 9.0, the Features screen wi contain a Shared Features coumn for muti-modue Communication Manager systems. The Shared Features coumn does not exist on transactions prior to RFA Reease 9.0. Cick the Features tab. The system dispays the Features Information screen (Figure 35). The Keyword Description coumn and the Keyword coumn can now be sorted aphabeticay by cicking on the individua coumn heading. After cicking the coumn heading, the coor changes from bue to purpe. A hep screen is provided by cicking the Changing the Feature Sort ink on the top of each tabe type. Cicking on the coumn heading sorts the information in a the tabes on the Feature screen. Figure 35: RFA Reease 9 Feature Information screen for Communication Manager If you are unfamiiar with the Features Information screen see Understanding the Features tab on page 30. If you are aready famiiar with the tabes, continue with step 10a. Step 10 has two parts: Issue 5.0 September

94 Additions Step 10a: Make any necessary changes for the first modue on page 94 Step 10b: Make any necessary changes for the next modue on page 94 Step 10a: Make any necessary changes for the first modue Verify that the tabes in the Feature Information screen are correct. If not, make the necessary changes to the information. You must cick Submit if you make any changes to the feature information. Cicking Submit ony saves the changes for the main modue. It does not save the changes for other modues in the system. To make changes on other modues in the system, see Step 10b: Make any necessary changes for the next modue on page 94. After you cick Submit the system dispays the Feature Information screen with the status of the updates. Feature dependency is vaidated when a change is made on the feature screen and before a transaction is competed. Vaidation ensures that the features are set correcty before you insta a icense fie. Step 10b: Make any necessary changes for the next modue If this system contains more than one modue, use the drop-down menu under the Feature Information heading to seect another modue. Then make any necessary changes to the feature information for the next modue in the ist. Cick Submit after you make any changes. Cicking Submit ony saves the changes you made on the modue you are viewing. Repeat these steps unti you change and submit the feature information for a the modues in this system. After you enter the information for each modue and cick Submit, the system dispays the Feature Information screen with information on the status of the updates. 94 Avaya Remote Feature Activation (RFA) User Guide

95 Addition procedure to add a feature or a modue Step 11: Compete the transaction Cick the Compete Transaction tab. The system dispays the Compete Transaction screen (Figure 36). Figure 36: Compete Transaction screen Before you can compete the transaction, you must verify that you reviewed the feature settings on a the modues and that you agree that the settings are correct. Verify that you reviewed the feature settings, seect the box next to the statement and cick Submit to compete the transaction. If you are not ready to compete the transaction you can eave the screen by cicking on one of the foowing: A different tab A different item on the RFA Appication Main Menu Important:! Important: Unti you compete the transaction, you have the option to deete the transaction. Once you compete the transaction the transaction becomes a permanent system record. You cannot deete a system record from RFA. Issue 5.0 September

96 Additions Step 12: Record the SID and version number After you cick Submit on the Compete Transaction screen, the system dispays a window asking if you want to compete the transaction. If you want to continue, cick Ok. The system dispays the System Identification screen (Figure 37). Figure 37: System Identification screen Record the SID and the version number. The SID is a pointer to the system record in the RFA database.you need the SID to obtain the icense fie from RFA. Cick OK to cose the window or cick Print to print the window. After you cick OK, the system dispays the RFA Appication Main Menu. Step 13: Deiver the icense fie You must deiver the icense fie from RFA to the Avaya server or to a computer. For more information on deivering a icense fie see Chapter 6: Deivering A Fie From RFA on page Avaya Remote Feature Activation (RFA) User Guide

97 Chapter 5: Updates and Upgrades About this chapter For instructions on Upgrade from R10+, see Additions, Upgrades R10+, and Migrations R10+ on page 197 of the Communication Manager chapter. This chapter contains the foowing information: Procedure for a Support Upgrade from a pre Reease 10 and upgrade from a pre Reease 10 on page 98) Switch Updates from a pre R10 on page 112 Support Upgrade from R10+ on page 125 Switch update from R10+ on page 141 Tip: Updates and upgrades do not appy to the Security Gateway, Contact Center, and Enterprise Communication Manager product famiies. Tip: This chapter contains steps that were in previous chapters. The steps are repeated so that the updates and upgrades procedure is compete and can be downoaded or printed separatey from the rest of this document. Introduction This section contains information that you wi need to know before you create a icense fie for an update or an upgrade. What is the difference between an update and an upgrade? Perform an update as part of a maintenance soution for a customer that is under warranty or has a Avaya maintenance contract. Perform an upgrade when a customer purchases a new reease with new or enhanced capabiities. Issue 5.0 September

98 Updates and Upgrades What is a Support Upgrade? A Support Upgrade provides protection for systems that are under warranty, or for customers who purchased an Avaya maintenance contract. A Support Upgrade is issued when product functionay deviates in any materia respect from Avaya product documentation. Deviations fa in to three different severity eves. Severity eves are used to determine appropriate action and to guide service providers, re-seers, and customers with appropriate impementation pans. Procedure for a Support Upgrade from a pre Reease 10 and upgrade from a pre Reease 10 Ensure that you are ogged in to the correct product famiy before you start. If you do not seect the correct product famiy, you receive unexpected errors and cannot compete the transaction This section expains how to perform a update or an upgrade from a pre Reease 10 system to another reease of Communication Manager. There is a difference between performing an upgrade and performing an update. Updates are performed as part of a maintenance soution for customers who are under warranty or have a Avaya maintenance contract. Upgrades are performed if the customer purchases a new Communication Manager reease with new or enhanced capabiities. Support Upgrade from a pre R10 and upgrade from a pre R10 procedure The Support Upgrade and upgrade procedure creates a icense fie that is being updated or upgraded from a software reease that does not use an RFA icense fie (pre Reease 10) to a software reease that does use an RFA icense fie (Reease 10 or ater). S8100 Servers that are running pre Reease 10 Communication Manager software have a icense fie, but the icense fie was not obtained from RFA. You must obtain an RFA icense fie for updates or upgrades of an S8100 Server to Reease 10 or ater. 98 Avaya Remote Feature Activation (RFA) User Guide

99 Procedure for a Support Upgrade from a pre Reease 10 and upgrade from a pre Reease 10 To create a icense fie for a Support Upgrade from pre Reease 10 or an upgrade from pre Reease 10, you must combine the information from the new SAP order with the information about what reease, category, features, and capacities are aready instaed on the Avaya system. Because a pre Reease 10 system does not have a icense fie, you cannot retrieve information about the current configuration from an RFA system record. To obtain the current configuration you can use the FET or upoad the configuration using the upoad Direct Connection option (DEFINITY reease 8 or ater ony). If the FET is used you must manuay upoad the FET fie to RFA. Before you start You need the foowing information before you start the Support Upgrade or the upgrade: The SAP order number that contains the materia codes that update the system from one reease to another. The GAI for any BusinessPartner who needs access to the system record. The name, the address, the teephone number, and the contact name for the Tier I BusinessPartner, the Tier II BusinessPartner, and the Customer. The IP address or the teephone number for the Avaya system or the e-mai address of the person who deivers the icense fie. The switch configuration: - For the Direct Connection option, you need the dia-in teephone number. - For the FET option, you need the most current FET software and the FET documentation. For the FET software and the FET documentation, see the RFA Information page at Before you use the FET, check the RFA Information page for the atest version. High-eve steps The foowing ist is a summary of the steps that you must perform to create a icense fie for a Support Upgrade pre R10 or an upgrade pre R10: Step 1: Start from the RFA Appication Main Menu on page 100 Step 2: Enter the SAP order number on page 100 Step 3: Verify that the SAP order data is correct on page 102 Step 4: Record the transaction number on page 102 Step 5: Compete the Customer and Genera System Information on page 103 Issue 5.0 September

100 Updates and Upgrades Step 6: Compete the Modue and Appication Detais information on page 105 Step 7: Compete the feature information on page 108 Step 8: Compete the transaction on page 110 Step 9: Record the SID and version number on page 111 Step 10: Deiver the icense fie on page 111 The foowing section provides the detaied instructions for each of these steps. Detaied steps Use the foowing detaied steps to create the icense fie for the Support Upgrade from Pre R10. Step 1: Start from the RFA Appication Main Menu To create a icense fie for a Support Upgrade, start from the RFA Appication Main Menu: 1. From the RFA Appication Main Menu: For a Support Upgrade: Cick Maintenance and then cick Support Upgrade from pre R10 The system dispays the SAP order number screen (Figure 38). Figure 38: SAP order number screen Step 2: Enter the SAP order number Type the SAP order number in the text fied and cick Retrieve. The SAP order number must be between 1 and 10 digits. Important:! Important: Use the SAP order number that incudes the software right to use (RTU) materia codes and the hardware materia codes that are used for dupication. Do not use the SAP order number that incudes hardware materia codes ony. If software codes exist on more than one SAP order, use the SAP order number that contains the main serving vehice to create the system record. Then use the subsequent SAP order numbers and foow the process for each SAP order. In this situation, you first create and then modify the system record. 100 Avaya Remote Feature Activation (RFA) User Guide

101 Procedure for a Support Upgrade from a pre Reease 10 and upgrade from a pre Reease 10 You can use a singe SAP order number mutipe times, as ong as you appy the number to different product famiies. For exampe, when you insta a Converged Communications Server and a Communication Manager server, you can use a singe SAP order number to generate both icense fies for the Communication Manager server and the Converged Communications Server. If the SAP order number is vaid, the system dispays the SAP Order Data screen. If the SAP order number is not vaid or if other probems exists, the system dispays an error message. See Tabe 11 for information on SAP error messages. Tabe 11: SAP error messages Error messages Description Action The SAP order number is invaid. The SAP order number does not contain any software materia codes. You do not have permission to access the SAP order information. The SAP order number that you enter is aready in use for this product famiy. You can continue to work on the transaction record but cannot use this SAP order number to generate a new icense fie. The SAP order number does not contain the materia codes for the icensing of the product famiy for which you are buiding the icense. The SAP order number does not contain the materia codes that you need to icense the product. This error message might appear to BusinessPartners who try to access a system record that does not contain their GUI. The SAP order number is aready in use in RFA to generate a icense for this product famiy. Ensure that you have ogged in to the correct product famiy and that you have the correct materia codes. If the product famiy and the materia codes are correct, contact the RFA Hepdesk. Contact the ordering team. For more information see Group Authorization Identification (GAI) on page 26. Ensure that you are ogged in to the right product famiy for the materia codes on your SAP order. If the product famiy is correct, a new SAP order number must be created to generate a icense. Contact the ordering team. Issue 5.0 September

102 Updates and Upgrades Step 3: Verify that the SAP order data is correct After you cick Retrieve, the system dispays the SAP Order Data screen. The product you are working on may rey on features that must be enabed on other product famiies. For a ist of product feature dependencies, cick the Licensing Dependency Tabe ink at the top of the screen. It is recommended that you use the information in this chart to ensure that you have a the features enabed that integrate with the product famiy you are working on. Review the SAP order data to ensure that the foowing information is correct: Sod To Customer Information The quantity, the materia code, and the description Information The information in the SAP Order screen ony shows the materia codes for the items that must be incuded in the icense fie such as the reease, the category, the features, and the capacities. This screen might not show everything that was ordered. If a the SAP Order Data is correct, cick Accept. Cick Back if the SAP order data on this screen is for the wrong customer, or does not incude the software RTU materia codes and the hardware materia codes for dupication.! Important: Important: If the SAP Order Data shows the information for the correct customer, but either the customer information or the materia code is incorrect, do not continue. Contact the account team immediatey. The SAP order information must be correct before you create and deiver the icense fie. After you cick Accept, the system dispays a transaction number (Figure 39). Figure 39: Transaction Number screen Step 4: Record the transaction number Record the transaction number that appears in the screen. You wi need this number ater. After you record the transaction number, cick Continue. 102 Avaya Remote Feature Activation (RFA) User Guide

103 Procedure for a Support Upgrade from a pre Reease 10 and upgrade from a pre Reease 10 Step 5: Compete the Customer and Genera System Information Step 5 has two parts: Step 5a Compete the GAI tabe on page 103 Step 5b: Compete the BusinessPartner and Customer information on page 104 Step 5a Compete the GAI tabe Compete the GAI fieds as appropriate: If you are an Avaya associate, do not add a GAI in the ist uness you are starting a transaction that wi be competed by a BusinessPartner. You must add the GAI for any BusinessPartners who needs access to this record. If you are a Tier I BusinessPartner, your GAI is aready on this ist from the SAP order. You must add the GAI for any Tier II BusinessPartner who needs access to this record.! CAUTION: CAUTION: If you make changes on this screen you must cick Submit before you go to another screen. If you do not cick Submit your changes are ost. Figure 40: Customer and Genera System Information screen Issue 5.0 September

104 Updates and Upgrades Step 5b: Compete the BusinessPartner and Customer information Compete the Tier I BusinessPartner Information, Tier II BusinessPartner Information, and End User Customer Information fieds as appropriate: If this is a direct order, you ony need to compete the End User Customer Information fieds. Cick Same As Sod To above the End User Customer Information fieds to copy the SAP Sod to Customer Information from the top of the screen. Then compete any empty fieds. If this is a BusinessPartner order, compete a three coumns. Since the Tier I BusinessPartner is probaby aso the Sod To Customer, cick Same As Sod To above that coumn to copy the SAP Sod To Customer Information. Then manuay enter the necessary information for the Tier II BusinessPartner and the Customer. Figure 41: Customer Information Screen Tier I, Tier II and Customer information You must enter a name in the Point of Contact s Name fied before you can compete the transaction. On the bottom of the Customer Information screen: Cick Submit if you have correcty fied out a the necessary fieds Cick Cear Form to cear the fieds and start again Cick SAP Order Data to view the SAP data that is associated with this icense fie After you cick Submit, the system dispays a window and asks if you want to continue. Cick OK to continue. The system dispays the Customer and Genera System Information screen with a message containing the status of your updates. 104 Avaya Remote Feature Activation (RFA) User Guide

105 Procedure for a Support Upgrade from a pre Reease 10 and upgrade from a pre Reease 10 Step 6: Compete the Modue and Appication Detais information Cick the Modue/App Detais tab. The system dispays the Modue and Appications Detais screen (Figure 42). See Figure 43 for an exampe of the Host ID Information tabe. Figure 42: Modue/Apps Detais screen for Communication Manager Figure 43: Modue/Apps Detais screen: Host ID Information tabe Step 6 has two parts: Step 6a: Review and change (if needed) the tabe information on page 106 Step 6b: Seect any additiona modues from the drop-down menu on page 107 Issue 5.0 September

106 Updates and Upgrades Step 6a: Review and change (if needed) the tabe information If needed, change or update the appropriate tabes in the Modue and Appications Detais screen. Fieds in the Modue Information Tabe change sighty depending on the product famiy. The Modue Information tabe: - The foowing ist describes each fied in the Modue Information tabe: Modue ID - This fied contains the modue ID number for this product or appication. The Modue ID is aways 1 if: - This is the main server for Communication Manager. - This order does not contain mutipe modues. - The product famiy does not support mutipe modues. Modue Type - This fied contains a description of the modue type. Patform Type - The patform type identifies the type of hardware that this product uses. Modue Description (optiona but recommended) - Enter a name or a description to hep identify this modue such as "South Campus". Modue Location (optiona but recommended) - Enter a ocation to hep identify this modue such as "Room B2H10". IP Address (Communication Manager ony) - Enter the Internet Protoco (IP) Address for this modue if you want RFA to deiver the icense fie over a oca area network (LAN). Dia-in Teephone Number (Avaya DEFINITY servers ony) - Enter the teephone number for this modue if you want to use the RFA Direct Connection option over the INADS port to deiver the icense fie. Information that you enter in this fied automaticay appears in the dia-in teephone fied when you request deivery of a fie by way of the Direct Connection option. You must enter the teephone numbers in one of the foowing formats: - For the United States and Canada; +1 XXX XXX XXXX - For a other countries; +Country Code CityCode LocaPhoneNumber, Extension. Commas and extensions are optiona. Athough you cannot use the Direct Connection option with the Avaya S8000 series servers, you can enter the S8000 series dia-in teephone number in this fied. You can use the S8000 series dia-in teephone number with the search functionaity to find transaction or system records. E-mai Address - Enter the e-mai address if you want RFA to use e-mai to deiver the icense fie. Information that you enter in this fied automaticay appears in the e-mai address fied when you request the downoad of a fie by way of e-mai. 106 Avaya Remote Feature Activation (RFA) User Guide

107 Procedure for a Support Upgrade from a pre Reease 10 and upgrade from a pre Reease 10 Deivery Instructions - Enter notes on how you want the icense fie for this modue to be deivered. RFA does not use this information. This information is for the use of peope who compete the transaction or deiver the fie. For more information on how to deiver a icense fie see Chapter 6: Deivering A Fie From RFA on page 153. Seria Number or Host ID Information tabe: - The Seria Number or Host ID Information Tabe contains the seria number or Host ID for the hardware for this Avaya system. This data is pre-popuated and cannot be changed. Appication Information Tabe - You do not need to compete the fieds in the Appication Information Tabe. Appication: Contains the name of the product or appication you are instaing. This fied is pre-popuated using the information on the SAP order. Expiration Date: This fied is reserved for future enhancements and is not being used at this time. Appication PID (Communication Manager ony): This number is assigned when registering the system for aarming. This fied is not required to create a icense fie. Reease Version (Communication Manager ony): Identifies the Communication Manager reease. This fied is pre-popuated using the information on the SAP order. To enter any changes that you made on this screen, cick Submit. The system dispays the Modue/Appication Detais screen with the status of the updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. Step 6b: Seect any additiona modues from the drop-down menu Some Avaya systems contain more than one modue or appication. Use the drop-down menu that is beow the tab bar to view and seect additiona modues or appications. If this is a Communication Manager instaation with mutipe modues, you must enter the seria number information for each modue that you seect. For Unified Communications Center (UCC), the information that you submit for one appication is automaticay copied to the other appication screens. You do not need to enter any additiona information. Review, and if necessary, change or update the tabe information as instructed in 8a. Cick Submit to enter any changes made on this screen.the system dispays the Modue/ Appication Detais screen. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. Issue 5.0 September

108 Updates and Upgrades Step 7: Compete the feature information Starting in RFA Reease 9, the Features screen wi contain a Shared Features coumn for muti-modue Communication Manager systems. You wi not see the Shared Features coumn on transactions prior to RFA Reease 9. Cick the Features tab. The system dispays the Features Information screen (Figure 44). The Keyword Description coumn and the Keyword coumn can now be sorted aphabeticay by cicking on the individua coumn heading. After cicking the coumn heading, the coor changes from bue to purpe. A hep screen is provided by cicking the Changing the Feature Sort ink on the top of each tabe type. Cicking on the coumn heading sorts the information in a the tabes on the Feature screen. Figure 44: Feature Information screen If you are unfamiiar with the Features Information screen see Understanding the Features tab on page 30. If you are aready famiiar with the tabes, continue with step 7a. Step 7 has two parts: Step 7a: Make any necessary changes for the first modue on page Avaya Remote Feature Activation (RFA) User Guide

109 Procedure for a Support Upgrade from a pre Reease 10 and upgrade from a pre Reease 10 Step 7b: Make any necessary changes for the next modue on page 110 Issue 5.0 September

110 Updates and Upgrades Step 7a: Make any necessary changes for the first modue Verify that the tabes in the Feature Information screen are correct. If not, make the necessary changes to the information. You must cick Submit if you make any changes to the feature information. Cicking Submit ony saves the changes for the main modue. It does not save the changes for other modues in the system. To make changes on other modues in the system, see Step 7b: Make any necessary changes for the next modue on page 110. After you cick Submit the system dispays the Feature Information screen with the status of the updates. Feature dependency is vaidated when a change is made on the feature screen and before a transaction is competed. Vaidation ensures that the features are set correcty before you insta a icense fie. Step 7b: Make any necessary changes for the next modue If this system contains more than one modue, use the drop-down menu under the Feature Information heading to seect another modue. Then make any necessary changes to the feature information for the next modue in the ist. Cick Submit after you make any changes. Cicking Submit ony saves the changes you made on the modue you are viewing. Repeat these steps unti you change and submit the feature information for a the modues in this system. Step 8: Compete the transaction Cick the Compete Transaction tab. The system dispays the Compete Transaction screen (Figure 45). Figure 45: Compete Transaction screen 110 Avaya Remote Feature Activation (RFA) User Guide

111 Procedure for a Support Upgrade from a pre Reease 10 and upgrade from a pre Reease 10 Before you can compete the transaction, you must verify that you reviewed the feature settings on a the modues and agree that the settings are correct. Verify that you reviewed the feature settings by seecting the box next to the statement. Cick Submit to compete the transaction. If you are not ready to compete the transaction you can eave the screen by cicking either of the foowing: A different tab A different item on the RFA Appication Main Menu Important:! Important: Unti you compete the transaction, you have the option to deete the transaction. Once you compete the transaction the transaction becomes a permanent system record. You cannot deete a system record from RFA. Step 9: Record the SID and version number After you cick Submit on the Compete Transaction screen, the system dispays a window asking if you want to compete the transaction. If you want to continue, cick Ok. The system dispays a System Identification screen (Figure 46). Figure 46: System Identification screen Record the SID and the version number. The SID is a pointer to the system record in the RFA database.you need the SID to obtain the icense fie from RFA. Cick OK to cose the window or cick Print to print the window. After you cick OK, the system dispays the RFA Appication Main Menu. Step 10: Deiver the icense fie You must deiver the icense fie from RFA to the Avaya server or to a computer. For more information on deivering a icense fie see Chapter 6: Deivering A Fie From RFA on page 153. Issue 5.0 September

112 Updates and Upgrades Switch Updates from a pre R10 This section ony pertains to the Communication Manager product famiy. Use this procedure to create a icense fie for pre Reease 10 system update or upgrade that does not use an RFA icense fie, to a software reease that does use RFA icense fies. To create a icense fie for a Switch Update from pre Reease 10, you must obtain the feature information from the switch and upoad the configuration fie in to RFA. Before you start You need the foowing information before you start the switch update from pre Reease 10: The Maestro troube ticket number. The GAI for any BusinessPartner who might need access to the system record. The name, address, teephone number, and contact name for the Tier I BusinessPartner, the Tier II BusinessPartner, and the Customer. The IP address or the teephone number for the Avaya system or the e-mai address of the person who wi deiver the icense fie. The switch configuration: - For the upoad Direct Connection option, you need the dia-in teephone number. - For the FET option, you need the most current FET software and the FET documentation. Both the FET software and the FET documentation can found on the RFA Information page at Aways check the RFA Information page for the atest version before you use the FET. High-eve steps The foowing ist summarizes the steps that you must perform to update a switch from a pre Reease 10 system: Step 1: Identify the switch on page 113 Step 2: Record the transaction number on page 114 Step 3: Obtain the switch configuration fie on page 114 Step 4: Assign the sub-modues on page 115 Step 5: Compete the Customer and Genera System information on page Avaya Remote Feature Activation (RFA) User Guide

113 Switch Updates from a pre R10 Step 6: Compete the Modue and Appication Detais information on page 118 Step 7: Compete the feature information on page 122 Step 8: Compete the transaction on page 123 The foowing section provides the detaied instructions for each of these steps. Detaied steps This section contains the detaied steps that you need to perform a switch update from a pre Reease 10 system. Step 1: Identify the switch Use the foowing steps to perform a Switch Update from pre Reease 10: 1. On the RFA Appication Main Menu, cick Additions, Upgrades and Migrations > Upgrade from Pre R10. The system dispays the Identify Switch screen (Figure 47). Figure 47: Switch Update Pre R10 Issue 5.0 September

114 Updates and Upgrades 2. Enter the foowing required customer information and cick Submit. Maestro troube ticket number Customer name Street address City State or region Posta code Country For each modue enter: - Modue type - Patform type - Appication - Software reease Step 2: Record the transaction number After you cick Submit the system dispays the RFA transaction number. Record the transaction number. You must enter the transaction number in the FET before you can extract the switch information. Step 3: Obtain the switch configuration fie Use the foowing steps to obtain a switch configuration fie: Use the FET and foow the procedure in the FET documentation. You might want to exit RFA whie you obtain the fie. You can restart RFA after you successfuy upoad the fie to your computer. The FET appication and the FET documentation can be found at Use the Direct Connection option: a. Cick Continue. The system dispays the Upoad Switch Configuration Fie (Figure 48). 114 Avaya Remote Feature Activation (RFA) User Guide

115 Switch Updates from a pre R10 Figure 48: Upoad Switch Configuration screen b. Cick Upoad Using Direct Connection. The system dispays the Upoad Using Direct Connection screen (Figure 49). Figure 49: Upoad Using Direct Connection screen c. If the switch meets the requirement that is specified on the window, enter the dia-in teephone number and cick Yes. To begin the upoad, cick Upoad Using Direct Connection. Step 4: Assign the sub-modues In the Assign Subs screen, enter the information for a sub-modues that wi be updated and cick Submit. Issue 5.0 September

116 Updates and Upgrades Step 5: Compete the Customer and Genera System information Step 5 has two parts: Step 5a Compete the GAI tabe on page 116 Step 5b: Compete the BusinessPartner and End User Customer information on page 117 Step 5a Compete the GAI tabe Compete the GAI fieds as appropriate: If you are an Avaya associate, do not add a GAI in the ist uness you are starting a transaction that a BusinessPartner wi compete. You must add the GAI for any BusinessPartner who needs access to this record. If you are a Tier I BusinessPartner, your GAI is aready on this ist from the SAP order. You must add the GAI for any Tier II BusinessPartner who needs access to this record.! CAUTION: CAUTION: If you make changes on this screen you must cick Submit before you go to another screen. If you do not cick Submit your changes are ost. Figure 50: Customer and Genera System Information 116 Avaya Remote Feature Activation (RFA) User Guide

117 Switch Updates from a pre R10 Step 5b: Compete the BusinessPartner and End User Customer information Compete the Tier I BusinessPartner Information, Tier II BusinessPartner Information, and End User Customer Information fieds as appropriate: If this is a direct order, compete ony the End User Customer Information fieds. Cick Same As Sod To above the End User Customer Information fieds to copy the SAP Sod to Customer Information from the top of the screen. Then compete any empty fieds. If this is a BusinessPartner order, compete a three coumns. Since the Tier I BusinessPartner is probaby aso the Sod To Customer, cick Same As Sod To above that coumn to copy the SAP Sod To Customer Information. Then manuay enter the necessary information for the Tier II BusinessPartner and the customer. Figure 51: Customer Information Screen Tier I, Tier II and End User Information You must enter a name in the Point of Contact s Name fied before you can compete the transaction. On the bottom of the Customer Information screen: Cick Submit if you have correcty fied out a the necessary fieds Cick Cear Form to cear the fieds and start again Cick SAP Order Data to view the SAP data that is associated with this icense fie After you cick Submit, the system dispays a window and asks if you want to continue. Cick OK to continue. The system dispays a Customer and Genera System Information screen with a message containing the status of your updates. Issue 5.0 September

118 Updates and Upgrades Step 6: Compete the Modue and Appication Detais information Cick the Modue/App Detais tab. The system dispays the Modue and Appications Detais screen (Figure 52). See Figure 53 for an exampe of the Host ID Information tabe. Figure 52: Modue/Apps Detais screen for Communication Manager Figure 53: Host ID Information Tabe on the Modue/Apps Detais screen Step 6 has two parts: Step 6a: Review and change (if needed) the tabe information on page 119 Step 6b: Seect any additiona modues from the drop-down menu on page Avaya Remote Feature Activation (RFA) User Guide

119 Switch Updates from a pre R10 Step 6a: Review and change (if needed) the tabe information If needed, change or update the appropriate tabes in the Modue and Appications Detais screen. Fieds in the Modue Information tabe change sighty depending on the product famiy. The foowing ist describes each fied in the Modue Information tabe: Modue ID - This fied contains the modue ID number for this product or appication. The Modue ID is aways 1 if: - This is the Main server for Communication Manager. - This order does not contain mutipe modues. - The product famiy does not support mutipe modues. Modue Type - This fied contains a description of the modue type. Patform Type - The patform type identifies the type of hardware that this product uses. Modue Description (optiona but recommended) - Enter a name or a description to hep identify this modue such as "South Campus". Modue Location (optiona but recommended) - Enter a ocation to hep identify this modue such as "Room B2H10". IP Address (Communication Manager ony) - Enter the Internet Protoco (IP) Address for this modue if you want RFA to deiver the icense fie over a oca area network (LAN). Dia-in Teephone Number (Avaya DEFINITY servers ony) - Enter the teephone number for this modue if you want to use the RFA Direct Connection option over the INADS port to deiver the icense fie. Information that you enter in this fied automaticay appears in the dia-in teephone fied when you request deivery of a fie by way of the Direct Connection option. You must enter the teephone numbers in one of the foowing formats: - For the United States and Canada; +1 XXX XXX XXXX - For a other countries; +Country Code CityCode LocaPhoneNumber, Extension. Commas and extensions are optiona. Athough you cannot use the Direct Connection option with the Avaya S8000 series servers, you can enter the S8000 series dia-in teephone number in this fied. You can use the S8000 series dia-in teephone number with the search functionaity to find transaction or system records. E-mai Address - Enter the e-mai address if you want RFA to use e-mai to deiver the icense fie. Information that you enter in this fied automaticay appears in the e-mai address fied when you request the downoad of a fie by way of e-mai. Issue 5.0 September

120 Updates and Upgrades Deivery Instructions - Enter notes on how you want the icense fie for this modue to be deivered. RFA does not use this information. This information is for the use of peope who compete the transaction or deiver the fie. For more information on how to deiver a icense fie see Chapter 6: Deivering A Fie From RFA on page 153. Cick Submit to save the information. If you enter information without competing the seria number or Host ID Information tabe, the system dispays a message that the non Host ID (or seria number) updates are successfu. Seria Number or Host ID Information Tabe - Depending on the product famiy, a Seria Number Information tabe or a Host ID Information tabe appears in the Modue/Appications screen. You must enter the correct seria number or Host ID for the Avaya server where the icense fie is to be instaed. The icense fie can t operate on a system that does not contain the correct seria number or Host ID. Type the foowing data in either the Seria Number Information tabe or the Host ID Information tabe: Enter the seria number or the Host ID. Confirm the seria number or Host ID: The seria number or the Host ID must match the data that you entered in the seria number or Host ID fieds. When you use dupication for DEFINITY, the system prompts for seria numbers of both the A and the B SPE. Retrieve SN - If you are working on an Avaya DEFINITY server you have the option to have RFA retrieve the seria number from the processor board. To use this option, the software on the DEFINITY server must be Reease 9 or ater, and you must have dia-up connectivity. Use the foowing steps to enter data in the Retrieve SN fied: 1. Next to the seria number fied, cick Retrieve SN. 2. In the Dia-in Teephone Number fied, enter the dia-in teephone for the system. If a dia-in teephone number exists in the Modue Information tabe, that number automaticay appears in the Dia-in Teephone Number fied. 3. Cick Submit to connect to the system and retrieve the seria number. WARNING:! WARNING: The retrieve seria number process can take up to six minutes to compete. You can cick Cance this Request at any time to return to the Modue/Appication Detais screen from where you can enter the seria number manuay. 4. Once approved, the seria number is entered in the Seria Number fied in the Seria Number tabe. 120 Avaya Remote Feature Activation (RFA) User Guide

121 Switch Updates from a pre R10 Appication Information Tabe - You do not need to compete the fieds in the Appication Information tabe. Appication - Contains the name of the product or appication that you are instaing. This fied is pre popuated using the information on the SAP order. Expiration Date - This fied is reserved for future enhancements. Appication PID (Communication Manager ony) - This number is assigned when registering the system for aarming. This fied is not required to create a icense fie. Reease Version - This fied identifies the version of the software. This fied is pre popuated with the information on the SAP order. To enter any changes that you made on this screen, cick Submit. The system dispays the Modue/Appication Detais screen with the status of the updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. Step 6b: Seect any additiona modues from the drop-down menu Some Avaya systems contain more than one modue or appication. Use the drop-down menu that is beow the tab bar to view and seect additiona modues or appications. If this is a Communication Manager instaation with mutipe modues, you must enter a seria number for each new modue that you seect. For Unified Communications Center (UCC), you do not need to enter any additiona information. The information that you submit for one appication is automaticay copied to the other appication screens. Review, and if necessary, change or update the tabe information as instructed in Step 9a. Cick Submit to enter any changes made on this screen.the system dispays the Modue/ Appication Detais screen with a message about the status of your updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. Issue 5.0 September

122 Updates and Upgrades Step 7: Compete the feature information Cick the Features tab. The system dispays the Features Information screen (Figure 54). Figure 54: Feature Information screen If you are unfamiiar with the Features Information screen see Understanding the Features tab on page 30. If you are aready famiiar with the tabes, continue with step 7a. Step 7 has two parts: Step 7a: Make any necessary changes for the first modue on page 122 Step 7b: Make any necessary changes for the next modue on page 123 Step 7a: Make any necessary changes for the first modue Verify that the tabes in the Feature Information screen are correct. If not, make the necessary changes to the information. You must cick Submit if you make any changes to the feature information. Cicking Submit ony saves the changes for the main modue. It does not save the changes for other modues in the system. To make changes on other modues in the system, see Step 7b: Make any necessary changes for the next modue on page 123. After you cick Submit the system dispays the Feature Information screen with the status of the updates. Feature dependency is vaidated when a change is made on the feature screen and before a transaction is competed. Vaidation ensures that the features are set correcty before you insta a icense fie. 122 Avaya Remote Feature Activation (RFA) User Guide

123 Switch Updates from a pre R10 Step 7b: Make any necessary changes for the next modue If this system contains more than one modue, use the drop-down menu under the Feature Information heading to seect another modue. Then make any necessary changes to the feature information for the next modue in the ist. Cick Submit after you make any changes. Cicking Submit ony saves the changes you made on the modue you are viewing. Repeat these steps unti you change and submit the feature information for a the modues in this system. After you enter the information for each modue and cick Submit, the system dispays the Feature Information screen with information on the status of the updates. Step 8: Compete the transaction Cick the Compete Transaction tab. The system dispays the Compete Transaction screen (Figure 55). Figure 55: Compete Transaction screen Before you can compete the transaction, you must verify that you reviewed the feature settings on a the modues and that you agree that the settings are correct. Verify that you reviewed the feature settings, seect the box next to the statement and cick Submit to compete the transaction. If you are not ready to compete the transaction you can eave the screen by cicking on one of the foowing: A different tab A different item on the RFA Appication Main Menu Issue 5.0 September

124 Updates and Upgrades Important:! Important: Unti you compete the transaction, you have the option to deete the transaction. Once you compete the transaction the transaction becomes a permanent system record. You cannot deete a system record from RFA. Step 9: Record the SID and version number After you cick Submit on the Compete Transaction screen, the system dispays a window asking if you want to compete the transaction. If you want to continue, cick Ok. The system dispays the System Identification screen (Figure 56). Figure 56: System Identification screen Record the SID and the version number. The SID is a pointer to the system record in the RFA database.you need the SID to obtain the icense fie from RFA. Cick OK to cose the window or cick Print to print the window. After you cick OK, the system dispays the RFA Appication Main Menu. Step 10: Deiver the icense fie You must deiver the icense fie from RFA to the Avaya server or to a computer. For more information on deivering a icense fie see Chapter 6: Deivering A Fie From RFA on page Avaya Remote Feature Activation (RFA) User Guide

125 Support Upgrade from R10+ Support Upgrade from R10+ This section expains how to obtain a icense fie for a Support Upgrade from a Reease 10 or ater system. High-eve steps The foowing ist summarizes the steps that you must preform to create a icense fie for a Support Upgrade from a R10+ system. Step 1: Enter the SAP order number on page 125 Step 2: Verify that the SAP order data is correct on page 127 Step 3: Record the transaction number on page 127 Step 4: Enter the SID on page 127 Step 5: Verify the SID information on page 128 Step 6: Compete the Assign Patforms, Reeases, and Add Modues screen on page 128 Step 7: Compete the Customer and Genera System information on page 131 Step 8: Compete the Modue and Appication Detais information on page 133 Step 9: Compete the feature information on page 138 Step 10: Compete the transaction on page 139 Step 11: Record the SID and version number on page 140 Step 12: Deiver the icense fie on page 140 The foowing section provides detaied instructions for each of these steps. Detaied steps Use the foowing detaied steps to preform an update for a R10+ system. Step 1: Enter the SAP order number Type the SAP order number in the text fied and cick Retrieve. The SAP order number must be between 1 and 10 digits. Issue 5.0 September

126 Updates and Upgrades! Important: Important: Use the SAP order number that incudes the software right to use (RTU) materia codes and the hardware materia codes that are used for dupication. Do not use the SAP order number that incudes hardware materia codes ony. If software codes exist on more than one SAP order, use the SAP order number that contains the main serving vehice to create the system record. Then use the subsequent SAP order numbers and foow the process for each SAP order. In this situation, you first create and then modify the system record. You can use a singe SAP order number mutipe times, as ong as you appy the number to different product famiies. For exampe, when you insta a Converged Communications Server and a Communication Manager server, you can use a singe SAP order number to generate both icense fies for the Communication Manager server and the Converged Communications Server. If the SAP order number is vaid, the system dispays the SAP Order Data screen. If the SAP order number is not vaid or if other probems exists, the system dispays an error message. See Tabe 12 for information on SAP error messages. Tabe 12: SAP error messages Error messages Description Action The SAP order number is invaid. The SAP order number does not contain any software materia codes. You do not have permission to access the SAP order information. The SAP order number that you enter is aready in use for this product famiy. You can continue to work on the transaction record but cannot use this SAP order number to generate a new icense fie. The SAP order number does not contain the materia codes for the icensing of the product famiy for which you are buiding the icense. The SAP order number does not contain the materia codes that you need to icense the product. This error message might appear to BusinessPartners who try to access a system record that does not contain their GUI. The SAP order number is aready in use in RFA to generate a icense for this product famiy. Ensure that you have ogged in to the correct product famiy and that you have the correct materia codes. If the product famiy and the materia codes are correct, contact the RFA Hepdesk. Contact the ordering team. For more information see Group Authorization Identification (GAI) on page 26. Ensure that you are ogged in to the right product famiy for the materia codes on your SAP order. If the product famiy is correct, a new SAP order number must be created to generate a icense. Contact the ordering team. 126 Avaya Remote Feature Activation (RFA) User Guide

127 Support Upgrade from R10+ Step 2: Verify that the SAP order data is correct After you cick Retrieve, the system dispays the SAP Order Data screen. The product you are working on may rey on features that must be enabed on other product famiies. For a ist of product feature dependencies, cick the Licensing Dependency Tabe ink at the top of the screen. It is recommended that you use the information in this chart to ensure that you have a the features enabed that integrate with the product famiy you are working on. Review the SAP order data to ensure that the foowing information is correct: Sod To Customer Information The quantity, the materia code, and the description Information The information in the SAP Order screen ony shows the materia codes for the items that must be incuded in the icense fie such as the reease, the category, the features, and the capacities. This screen might not show everything that was ordered. If a the SAP Order Data is correct, cick Accept. Cick Back if the SAP order data on this screen is for the wrong customer, or does not incude the software RTU materia codes and the hardware materia codes for dupication. Important:! Important: If the SAP Order Data shows the information for the correct customer, but either the customer information or the materia code is incorrect, do not continue. Contact the account team immediatey. The SAP order information must be correct before you create and deiver the icense fie. Step 3: Record the transaction number Record the transaction number that appears in the screen. You wi need this number ater. After you record the transaction number, cick Continue. The system dispays the Customer and Genera System Information screen. Step 4: Enter the SID Enter the SID for this Avaya system and cick Retrieve. After cicking Retrieve, the system dispays the SID Information screen (Figure 57). Issue 5.0 September

128 Updates and Upgrades Figure 57: System Information (SID) screen Step 5: Verify the SID information Ensure that the information on the System Information screen is correct. Cick Accept if the information on the screen is correct. Cick Back to enter another SID. After you cick Accept, the system dispays the SID Accept Resuts screen. Cick Continue to continue with the transaction. Step 6: Compete the Assign Patforms, Reeases, and Add Modues screen Assign Patforms, Reeases, and Add Modues screen overview RFA considers an upgrade to be a change in the reease version of appications for modues. An upgrade can be partia or fu. In a partia upgrade ony some of the modues within a system are upgraded. In a fu upgrade a modues within a system are upgraded. 128 Avaya Remote Feature Activation (RFA) User Guide

129 Support Upgrade from R10+ For a partia upgrade where there is ony one possibe seection, RFA automaticay assigns the operation to the modue. For operations where there is more than one possibe seection, RFA aows the user to seect the modue or appications that wi be upgraded using the Assign Patforms, Reeases, and Add Modues screen. For a fu upgrade, RFA tries to determine the modues to upgrade and the reeases to use for the upgrade. If RFA cannot make an absoute determination of the modues to upgrade based on the SAP order, RFA aows the user to seect the modue and appications for the upgrade using the Assign Patforms, Reeases, and Add Modues screen. RFA vaidates the upgrade based on the foowing rues: The Communication Manager reease for an LSP must be equa to or greater than the main modue. The Communication Manager reease for an ESS server must be equa to or greater than the main modue. When a upgrade operation is seected from the SAP Order Detais section, the system dispays a New Reease check box in each of the modues in the Existing Order Detais section that meets the foowing criteria: The Modue Type fied for the operation in the SAP Order Detais section contains the same modue type as the modue in the Existing Modue Detais section. The Reease fied for the modue in the Existing Modue Detais section is different than the reease in the SAP Order Detais section for the operation. The New Reease fied for the modue has not aready been popuated by a different operation. If RFA automaticay assigned a the operations to the appropriate modues, you cannot make any seections in the Existing Modue Detais section. Cick Finish to save the information and continue the transaction. Issue 5.0 September

130 Updates and Upgrades Figure 58: The Assign Patforms, Reeases, and Add Modues for upgrades The foowing occurs when you mark a check in the New Reease check box: A red New Reease fied appears dispaying the reease from the seected operation. A red sequence number appears. The Quantity Remaining fied in the SAP Order Detais section is decremented for the seected operation. High-eve steps Use the foowing high-eve steps to assign an upgrade operation to a modue: 1. In the SAP Order Detais section, seect the radio button next to the SAP segment number for the operation you want to assign. 2. In the Existing Modue Detais section, cick the New Reease check box for the modue that you want to associate with the operation. The sequence number and new reease appears in red in the modue box. 130 Avaya Remote Feature Activation (RFA) User Guide

131 Support Upgrade from R If the quantity remaining for the operation is zero and there are additiona operations on the order, seect another operation by cicking the radio button next to the segment number for that operation. If a the operations have been assigned, and the quantity for the operations are zero, a Finish button appears at the bottom of the screen. Cick Finish to submit the data and continue the transaction. For more information on how to use the Assign Patform, Reeases, and Add Modues screen, see The Assign Patforms, Reeases, and Add Modues screen on page 266. Step 7: Compete the Customer and Genera System information Step 7 has two parts: Step 7a Compete the GAI tabe on page 131 Step 7b: Compete the BusinessPartner and End User Customer information on page 132 Step 7a Compete the GAI tabe Compete the GAI fieds as appropriate: If you are an Avaya associate, do not add a GAI in the ist uness you are starting a transaction that a BusinessPartner wi compete. You must add the GAI for any BusinessPartner who needs access to this record. If you are a Tier I BusinessPartner, your GAI is aready on this ist from the SAP order. You must add the GAI for any Tier II BusinessPartner who needs access to this record. Issue 5.0 September

132 Updates and Upgrades! CAUTION: CAUTION: If you make changes on this screen you must cick Submit before you go to another screen. If you do not cick Submit your changes are ost. Figure 59: Customer and Genera System Information Step 7b: Compete the BusinessPartner and End User Customer information Compete the Tier I BusinessPartner Information, Tier II BusinessPartner Information, and End User Customer Information fieds as appropriate: If this is a direct order, compete ony the End User Customer Information fieds. Cick Same As Sod To above the End User Customer Information fieds to copy the SAP Sod to Customer Information from the top of the screen. Then compete any empty fieds. If this is a BusinessPartner order, compete a three coumns. Since the Tier I BusinessPartner is probaby aso the Sod To Customer, cick Same As Sod To above that coumn to copy the SAP Sod To Customer Information. Then manuay enter the necessary information for the Tier II BusinessPartner and the customer. 132 Avaya Remote Feature Activation (RFA) User Guide

133 Support Upgrade from R10+ Figure 60: Customer Information Screen Tier I, Tier II and End User Information You must enter a name in the Point of Contact s Name fied before you can compete the transaction. On the bottom of the Customer Information screen: Cick Submit if you have correcty fied out a the necessary fieds Cick Cear Form to cear the fieds and start again Cick SAP Order Data to view the SAP data that is associated with this icense fie After you cick Submit, the system dispays a window and asks if you want to continue. Cick OK to continue. The system dispays a Customer and Genera System Information screen with a message containing the status of your updates. Step 8: Compete the Modue and Appication Detais information Cick the Modue/App Detais tab. The system dispays the Modue and Appications Detais screen (Figure 61). See Figure 62 for an exampe of the Host ID Information tabe. Issue 5.0 September

134 Updates and Upgrades Figure 61: Modue/Apps Detais screen for Communication Manager Figure 62: Host ID Information Tabe on the Modue/Apps Detais screen Step 8 has two parts: Step 8a: Review and change (if needed) the tabe information on page 135 Step 8b: Seect any additiona modues from the drop-down menu on page Avaya Remote Feature Activation (RFA) User Guide

135 Support Upgrade from R10+ Step 8a: Review and change (if needed) the tabe information If needed, change or update the appropriate tabes in the Modue and Appications Detais screen. Fieds in the Modue Information tabe change sighty depending on the product famiy. The foowing ist describes each fied in the Modue Information tabe: Modue ID - This fied contains the modue ID number for this product or appication. The Modue ID is aways 1 if: - This is the Main server for Communication Manager. - This order does not contain mutipe modues. - The product famiy does not support mutipe modues. Modue Type - This fied contains a description of the modue type. Patform Type - The patform type identifies the type of hardware that this product uses. Modue Description (optiona but recommended) - Enter a name or a description to hep identify this modue such as "South Campus". Modue Location (optiona but recommended) - Enter a ocation to hep identify this modue such as "Room B2H10". IP Address (Communication Manager ony) - Enter the Internet Protoco (IP) Address for this modue if you want RFA to deiver the icense fie over a oca area network (LAN). Dia-in Teephone Number (Avaya DEFINITY servers ony) - Enter the teephone number for this modue if you want to use the RFA Direct Connection option over the INADS port to deiver the icense fie. Information that you enter in this fied automaticay appears in the dia-in teephone fied when you request deivery of a fie by way of the Direct Connection option. You must enter the teephone numbers in one of the foowing formats: - For the United States and Canada; +1 XXX XXX XXXX - For a other countries; +Country Code CityCode LocaPhoneNumber, Extension. Commas and extensions are optiona. Athough you cannot use the Direct Connection option with the Avaya S8000 series servers, you can enter the S8000 series dia-in teephone number in this fied. You can use the S8000 series dia-in teephone number with the search functionaity to find transaction or system records. E-mai Address - Enter the e-mai address if you want RFA to use e-mai to deiver the icense fie. Information that you enter in this fied automaticay appears in the e-mai address fied when you request the downoad of a fie by way of e-mai. Issue 5.0 September

136 Updates and Upgrades Deivery Instructions - Enter notes on how you want the icense fie for this modue to be deivered. RFA does not use this information. This information is for the use of peope who compete the transaction or deiver the fie. For more information on how to deiver a icense fie see Chapter 6: Deivering A Fie From RFA on page 153. Cick Submit to save the information. If you enter information without competing the seria number or Host ID Information tabe, the system dispays a message that the non Host ID (or seria number) updates are successfu. Seria Number or Host ID Information Tabe - Depending on the product famiy, a Seria Number Information tabe or a Host ID Information tabe appears in the Modue/Appications screen. You must enter the correct seria number or Host ID for the Avaya server where the icense fie is to be instaed. The icense fie can t operate on a system that does not contain the correct seria number or Host ID. Type the foowing data in either the Seria Number Information tabe or the Host ID Information tabe: Enter the seria number or the Host ID. Confirm the seria number or Host ID: The seria number or the Host ID must match the data that you entered in the seria number or Host ID fieds. When you use dupication for DEFINITY, the system prompts for seria numbers of both the A and the B SPE. Retrieve SN - If you are working on an Avaya DEFINITY server you have the option to have RFA retrieve the seria number from the processor board. To use this option, the software on the DEFINITY server must be Reease 9 or ater, and you must have dia-up connectivity. Use the foowing steps to enter data in the Retrieve SN fied: 1. Next to the seria number fied, cick Retrieve SN. 2. In the Dia-in Teephone Number fied, enter the dia-in teephone for the system. If a dia-in teephone number exists in the Modue Information tabe, that number automaticay appears in the Dia-in Teephone Number fied. 3. Cick Submit to connect to the system and retrieve the seria number. WARNING:! WARNING: The retrieve seria number process can take up to six minutes to compete. You can cick Cance this Request at any time to return to the Modue/Appication Detais screen from where you can enter the seria number manuay. 4. Once approved, the seria number is entered in the Seria Number fied in the Seria Number tabe. 136 Avaya Remote Feature Activation (RFA) User Guide

137 Support Upgrade from R10+ Appication Information Tabe - You do not need to compete the fieds in the Appication Information tabe. Appication - Contains the name of the product or appication that you are instaing. This fied is pre popuated using the information on the SAP order. Expiration Date - This fied is reserved for future enhancements. Appication PID (Communication Manager ony) - This number is assigned when registering the system for aarming. This fied is not required to create a icense fie. Reease Version - This fied identifies the version of the software. This fied is pre popuated with the information on the SAP order. To enter any changes that you made on this screen, cick Submit. The system dispays the Modue/Appication Detais screen with the status of the updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. Step 8b: Seect any additiona modues from the drop-down menu Some Avaya systems contain more than one modue or appication. Use the drop-down menu that is beow the tab bar to view and seect additiona modues or appications. If this is a Communication Manager instaation with mutipe modues, you must enter a seria number for each new modue that you seect. For Unified Communications Center (UCC), you do not need to enter any additiona information. The information that you submit for one appication is automaticay copied to the other appication screens. Review, and if necessary, change or update the tabe information as instructed in Step 9a. Cick Submit to enter any changes made on this screen.the system dispays the Modue/ Appication Detais screen with a message about the status of your updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. Issue 5.0 September

138 Updates and Upgrades Step 9: Compete the feature information Cick the Features tab. The system dispays the Features Information screen (Figure 63). Figure 63: Feature Information screen If you are unfamiiar with the Features Information screen see Understanding the Features tab on page 30. If you are aready famiiar with the tabes, continue with step 9a. Step 9 has two parts: Step 9a: Make any necessary changes for the first modue on page 138 Step 9b: Make any necessary changes for the next modue on page 139 Step 9a: Make any necessary changes for the first modue Verify that the tabes in the Feature Information screen are correct. If not, make the necessary changes to the information. You must cick Submit if you make any changes to the feature information. Cicking Submit ony saves the changes for the main modue. It does not save the changes for other modues in the system. To make changes on other modues in the system, see Step 9b: Make any necessary changes for the next modue on page 139. After you cick Submit the system dispays the Feature Information screen with the status of the updates. 138 Avaya Remote Feature Activation (RFA) User Guide

139 Support Upgrade from R10+ Feature dependency is vaidated when a change is made on the feature screen and before a transaction is competed. Vaidation ensures that the features are set correcty before you insta a icense fie. Step 9b: Make any necessary changes for the next modue If this system contains more than one modue, use the drop-down menu under the Feature Information heading to seect another modue. Then make any necessary changes to the feature information for the next modue in the ist. Cick Submit after you make any changes. Cicking Submit ony saves the changes you made on the modue you are viewing. Repeat these steps unti you change and submit the feature information for a the modues in this system. After you enter the information for each modue and cick Submit, the system dispays the Feature Information screen with information on the status of the updates. Step 10: Compete the transaction Cick the Compete Transaction tab. The system dispays the Compete Transaction screen (Figure 64). Figure 64: Compete Transaction screen Before you can compete the transaction, you must verify that you reviewed the feature settings on a the modues and that you agree that the settings are correct. Verify that you reviewed the feature settings, seect the box next to the statement and cick Submit to compete the transaction. Issue 5.0 September

140 Updates and Upgrades If you are not ready to compete the transaction you can eave the screen by cicking on one of the foowing: A different tab A different item on the RFA Appication Main Menu Important:! Important: Unti you compete the transaction, you have the option to deete the transaction. Once you compete the transaction the transaction becomes a permanent system record. You cannot deete a system record from RFA. Step 11: Record the SID and version number After you cick Submit on the Compete Transaction screen, the system dispays a window asking if you want to compete the transaction. If you want to continue, cick Ok. The system dispays the System Identification screen (Figure 65). Figure 65: System Identification screen Record the SID and the version number. The SID is a pointer to the system record in the RFA database.you need the SID to obtain the icense fie from RFA. Cick OK to cose the window or cick Print to print the window. After you cick OK, the system dispays the RFA Appication Main Menu. Step 12: Deiver the icense fie You must deiver the icense fie from RFA to the Avaya server or to a computer. For more information on deivering a icense fie see Chapter 6: Deivering A Fie From RFA on page Avaya Remote Feature Activation (RFA) User Guide

141 Switch update from R10+ Switch update from R10+ This section expains how to create a icense fie for a switch update from R10+. High-eve steps The foowing ist summarizes the steps you must preform to obtain a icense fie for a switch update from R10+. Step 1: Enter the SID and the Maestro troube ticket number on page 141 Step 2: Verify the SID information on page 142 Step 3: Enter the software reease on page 142 Step 4: Compete the Customer and Genera System information on page 142 Step 5: Compete the Modue and Appication Detais information on page 144 Step 6: Compete the feature information on page 149 Step 7: Compete the transaction on page 150 Step 8: Record the SID and version number on page 151 Step 9: Deiver the icense fie on page 151 The foowing section provides detaied instructions for each step. Detaied steps Use the foowing steps to create a icense fie for a switch update R10+. Step 1: Enter the SID and the Maestro troube ticket number Enter the SID for this Avaya system and cick Retrieve. After cicking Retrieve, the system dispays the SID Information screen (Figure 66). Issue 5.0 September

142 Updates and Upgrades Figure 66: System Information (SID) screen Step 2: Verify the SID information Verify that the information in the System Information screen is correct. Cick Accept if the information on the screen is correct. Cick Back to enter another SID. After you cick Accept, the system dispays the SID Accept Resuts screen.cick Continue to proceed with the transaction. Step 3: Enter the software reease Enter the software reease for this system and cick Submit. Step 4: Compete the Customer and Genera System information Step 4 has two parts: Step 4a Compete the GAI tabe on page 142 Step 4b: Compete the BusinessPartner and End User Customer information on page 143 Step 4a Compete the GAI tabe Compete the GAI fieds as appropriate: If you are an Avaya associate, do not add a GAI in the ist uness you are starting a transaction that a BusinessPartner wi compete. You must add the GAI for any BusinessPartner who needs access to this record. If you are a Tier I BusinessPartner, your GAI is aready on this ist from the SAP order. You must add the GAI for any Tier II BusinessPartner who needs access to this record. 142 Avaya Remote Feature Activation (RFA) User Guide

143 Switch update from R10+! CAUTION: CAUTION: If you make changes on this screen you must cick Submit before you go to another screen. If you do not cick Submit your changes are ost. Figure 67: Customer and Genera System Information Step 4b: Compete the BusinessPartner and End User Customer information Compete the Tier I BusinessPartner Information, Tier II BusinessPartner Information, and End User Customer Information fieds as appropriate: If this is a direct order, compete ony the End User Customer Information fieds. Cick Same As Sod To above the End User Customer Information fieds to copy the SAP Sod to Customer Information from the top of the screen. Then compete any empty fieds. If this is a BusinessPartner order, compete a three coumns. Since the Tier I BusinessPartner is probaby aso the Sod To Customer, cick Same As Sod To above that coumn to copy the SAP Sod To Customer Information. Then manuay enter the necessary information for the Tier II BusinessPartner and the customer. Issue 5.0 September

144 Updates and Upgrades Figure 68: Customer Information Screen Tier I, Tier II and End User Information You must enter a name in the Point of Contact s Name fied before you can compete the transaction. On the bottom of the Customer Information screen: Cick Submit if you have correcty fied out a the necessary fieds Cick Cear Form to cear the fieds and start again Cick SAP Order Data to view the SAP data that is associated with this icense fie After you cick Submit, the system dispays a window and asks if you want to continue. Cick OK to continue. The system dispays a Customer and Genera System Information screen with a message containing the status of your updates. Step 5: Compete the Modue and Appication Detais information Cick the Modue/App Detais tab. The system dispays the Modue and Appications Detais screen (Figure 69). See Figure 70 for an exampe of the Host ID Information tabe. 144 Avaya Remote Feature Activation (RFA) User Guide

145 Switch update from R10+ Figure 69: Modue/Apps Detais screen for Communication Manager Figure 70: Host ID Information Tabe on the Modue/Apps Detais screen Step 5 has two parts: Step 5a: Review and change (if needed) the tabe information on page 146 Step 5b: Seect any additiona modues from the drop-down menu on page 148 Issue 5.0 September

146 Updates and Upgrades Step 5a: Review and change (if needed) the tabe information If needed, change or update the appropriate tabes in the Modue and Appications Detais screen. Fieds in the Modue Information tabe change sighty depending on the product famiy. The foowing ist describes each fied in the Modue Information tabe: Modue ID - This fied contains the modue ID number for this product or appication. The Modue ID is aways 1 if: - This is the Main server for Communication Manager. - This order does not contain mutipe modues. - The product famiy does not support mutipe modues. Modue Type - This fied contains a description of the modue type. Patform Type - The patform type identifies the type of hardware that this product uses. Modue Description (optiona but recommended) - Enter a name or a description to hep identify this modue such as "South Campus". Modue Location (optiona but recommended) - Enter a ocation to hep identify this modue such as "Room B2H10". IP Address (Communication Manager ony) - Enter the Internet Protoco (IP) Address for this modue if you want RFA to deiver the icense fie over a oca area network (LAN). Dia-in Teephone Number (Avaya DEFINITY servers ony) - Enter the teephone number for this modue if you want to use the RFA Direct Connection option over the INADS port to deiver the icense fie. Information that you enter in this fied automaticay appears in the dia-in teephone fied when you request deivery of a fie by way of the Direct Connection option. You must enter the teephone numbers in one of the foowing formats: - For the United States and Canada; +1 XXX XXX XXXX - For a other countries; +Country Code CityCode LocaPhoneNumber, Extension. Commas and extensions are optiona. Athough you cannot use the Direct Connection option with the Avaya S8000 series servers, you can enter the S8000 series dia-in teephone number in this fied. You can use the S8000 series dia-in teephone number with the search functionaity to find transaction or system records. E-mai Address - Enter the e-mai address if you want RFA to use e-mai to deiver the icense fie. Information that you enter in this fied automaticay appears in the e-mai address fied when you request the downoad of a fie by way of e-mai. 146 Avaya Remote Feature Activation (RFA) User Guide

147 Switch update from R10+ Deivery Instructions - Enter notes on how you want the icense fie for this modue to be deivered. RFA does not use this information. This information is for the use of peope who compete the transaction or deiver the fie. For more information on how to deiver a icense fie see Chapter 6: Deivering A Fie From RFA on page 153. Cick Submit to save the information. If you enter information without competing the seria number or Host ID Information tabe, the system dispays a message that the non Host ID (or seria number) updates are successfu. Seria Number or Host ID Information Tabe - Depending on the product famiy, a Seria Number Information tabe or a Host ID Information tabe appears in the Modue/Appications screen. You must enter the correct seria number or Host ID for the Avaya server where the icense fie is to be instaed. The icense fie can t operate on a system that does not contain the correct seria number or Host ID. Type the foowing data in either the Seria Number Information tabe or the Host ID Information tabe: Enter the seria number or the Host ID. Confirm the seria number or Host ID: The seria number or the Host ID must match the data that you entered in the seria number or Host ID fieds. When you use dupication for DEFINITY, the system prompts for seria numbers of both the A and the B SPE. Retrieve SN - If you are working on an Avaya DEFINITY server you have the option to have RFA retrieve the seria number from the processor board. To use this option, the software on the DEFINITY server must be Reease 9 or ater, and you must have dia-up connectivity. Use the foowing steps to enter data in the Retrieve SN fied: 1. Next to the seria number fied, cick Retrieve SN. 2. In the Dia-in Teephone Number fied, enter the dia-in teephone for the system. If a dia-in teephone number exists in the Modue Information tabe, that number automaticay appears in the Dia-in Teephone Number fied. 3. Cick Submit to connect to the system and retrieve the seria number. WARNING:! WARNING: The retrieve seria number process can take up to six minutes to compete. You can cick Cance this Request at any time to return to the Modue/Appication Detais screen from where you can enter the seria number manuay. 4. Once approved, the seria number is entered in the Seria Number fied in the Seria Number tabe. Issue 5.0 September

148 Updates and Upgrades Appication Information Tabe - You do not need to compete the fieds in the Appication Information tabe. Appication - Contains the name of the product or appication that you are instaing. This fied is pre popuated using the information on the SAP order. Expiration Date - This fied is reserved for future enhancements. Appication PID (Communication Manager ony) - This number is assigned when registering the system for aarming. This fied is not required to create a icense fie. Reease Version - This fied identifies the version of the software. This fied is pre popuated with the information on the SAP order. To enter any changes that you made on this screen, cick Submit. The system dispays the Modue/Appication Detais screen with the status of the updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. Step 5b: Seect any additiona modues from the drop-down menu Some Avaya systems contain more than one modue or appication. Use the drop-down menu that is beow the tab bar to view and seect additiona modues or appications. If this is a Communication Manager instaation with mutipe modues, you must enter a seria number for each new modue that you seect. For Unified Communications Center (UCC), you do not need to enter any additiona information. The information that you submit for one appication is automaticay copied to the other appication screens. Review, and if necessary, change or update the tabe information as instructed in Step 9a. Cick Submit to enter any changes made on this screen.the system dispays the Modue/ Appication Detais screen with a message about the status of your updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. 148 Avaya Remote Feature Activation (RFA) User Guide

149 Switch update from R10+ Step 6: Compete the feature information Cick the Features tab. The system dispays the Features Information screen (Figure 71). Figure 71: Feature Information screen If you are unfamiiar with the Features Information screen see Understanding the Features tab on page 30. If you are aready famiiar with the tabes, continue with step 6a. Step 6 has two parts: Step 6a: Make any necessary changes for the first modue on page 149 Step 6b: Make any necessary changes for the next modue on page 150 Step 6a: Make any necessary changes for the first modue Verify that the tabes in the Feature Information screen are correct. If not, make the necessary changes to the information. You must cick Submit if you make any changes to the feature information. Cicking Submit ony saves the changes for the main modue. It does not save the changes for other modues in the system. To make changes on other modues in the system, see Step 6b: Make any necessary changes for the next modue on page 150. After you cick Submit the system dispays the Feature Information screen with the status of the updates. Issue 5.0 September

150 Updates and Upgrades Feature dependency is vaidated when a change is made on the feature screen and before a transaction is competed. Vaidation ensures that the features are set correcty before you insta a icense fie. Step 6b: Make any necessary changes for the next modue If this system contains more than one modue, use the drop-down menu under the Feature Information heading to seect another modue. Then make any necessary changes to the feature information for the next modue in the ist. Cick Submit after you make any changes. Cicking Submit ony saves the changes you made on the modue you are viewing. Repeat these steps unti you change and submit the feature information for a the modues in this system. After you enter the information for each modue and cick Submit, the system dispays the Feature Information screen with information on the status of the updates. Step 7: Compete the transaction Cick the Compete Transaction tab. The system dispays the Compete Transaction screen (Figure 72). Figure 72: Compete Transaction screen Before you can compete the transaction, you must verify that you reviewed the feature settings on a the modues and that you agree that the settings are correct. Verify that you reviewed the feature settings, seect the box next to the statement and cick Submit to compete the transaction. 150 Avaya Remote Feature Activation (RFA) User Guide

151 Switch update from R10+ If you are not ready to compete the transaction you can eave the screen by cicking on one of the foowing: A different tab A different item on the RFA Appication Main Menu Important:! Important: Unti you compete the transaction, you have the option to deete the transaction. Once you compete the transaction the transaction becomes a permanent system record. You cannot deete a system record from RFA. Step 8: Record the SID and version number After you cick Submit on the Compete Transaction screen, the system dispays a window asking if you want to compete the transaction. If you want to continue, cick Ok. The system dispays the System Identification screen (Figure 73). Figure 73: System Identification screen Record the SID and the version number. The SID is a pointer to the system record in the RFA database.you need the SID to obtain the icense fie from RFA. Cick OK to cose the window or cick Print to print the window. After you cick OK, the system dispays the RFA Appication Main Menu. Step 9: Deiver the icense fie You must deiver the icense fie from RFA to the Avaya server or to a computer. For more information on deivering a icense fie see Chapter 6: Deivering A Fie From RFA on page 153. Issue 5.0 September

152 Updates and Upgrades 152 Avaya Remote Feature Activation (RFA) User Guide

153 Chapter 6: Deivering A Fie From RFA About this chapter This chapter expains how to deiver a fie from RFA. This procedure is the same for a the RFA product famiies. Introduction This section contains information that is important to know when deivering a icense and authentication fie from RFA. Before you start You wi need the foowing information, computer, and dia-in teephone numbers to deiver a icense fie from RFA: The SID number for the competed system record A computer to downoad the icense fie to, or an address where RFA can send the fie by way of e-mai. The dia-in teephone number or the IP address for the DEFINITY servers that use the Direct Connection option. Options for deivering a fie from RFA For a servers: Downoad to your computer E-mai deivery For DEFINITY servers ony: Direct Connection Issue 5.0 September

154 Deivering A Fie From RFA License fie simpification for LSP and ESS servers Starting in RFA 10.9, text appears on the Deivery screen that instructs the user when to deiver a icense fie for the sub-modues. Hepfu information appears in the Detaied Deivery screen as shown in Tabe 13. Tabe 13: Information contained in the Detaied Deivery screen Action If you are instaing a new system If the main server icense fie is modified (by an SAP Order or by using the Features screen) in one or more of the foowing ways: An upgrade to the Communication Manager software A patform migration Changes to or additions of shared features If the main server icense fie is modified by a icense fie seria number swap out. If you change an un-shared feature on the main server icense fie using the Feature screen and you seect to appy changes to a modues. If you change an un-shared feature on the main server icense fie using the Feature screen and you seect to appy changes to this modue ony. If a sub-modue is added to the system You wi need to deiver a icense for: The main server and a the sub-modues The main server and a sub-modues that are at a reease ess than R014. In this case you do not need to deiver a icense fie for any sub-modues that are at R014 or greater. However, if one or more of the foowing features are added or changed on the main modue, you must re-deiver the icense fies for the LSPs and the ESS servers that are at R014: FEAT_DS1MSP FEAT_STTRKMSP FEAT_SYCCMSP The main server The main server and a sub-modues The main server The sub-modue 1 of Avaya Remote Feature Activation (RFA) User Guide

155 Deivering a fie from RFA procedure Tabe 13: Information contained in the Detaied Deivery screen (continued) Action If a sub-modue s icense fie is modified by a icense fie seria number swap-out You wi need to deiver a icense for: The sub-modue If a sub-modue icense fie is modified using an SAP order or by the Features screen in one or more of the foowing ways: Upgrade to the Communication Manager software Patform migration Changes to features or additions of features The sub-modue 2 of 2 Deivering a fie from RFA procedure Ensure that you are ogged in to the correct product famiy before you start. If you do not seect the correct product famiy, you receive unexpected errors and cannot compete the transaction. High-eve steps The foowing ist summarizes the steps that you must perform to deiver a fie from RFA: 1. From the RFA Appication Main Menu, cick Deiver Fies. 2. Enter the SID and cick Retrieve 3. Verify the SID detaied information and cick Accept 4. Cose the confirmation window 5. Seect a deivery option: Downoad to my PC Downoad fies using e-mai Direct Connection (DEFINITY ony) The foowing section provides instructions for each of these steps. Issue 5.0 September

156 Deivering A Fie From RFA Detaied steps Use the steps that are detaied in this section to deiver a fie from RFA. Step 1: Start with the RFA Appication Main Menu From the RFA Appication Main Menu, cick Deiver Fies. The system dispays the System Information screen. 156 Avaya Remote Feature Activation (RFA) User Guide

157 Deivering a fie from RFA procedure Step 2: Enter the SID Enter the SID and cick Retrieve. If you do not remember the SID, see Search/View Menu on page 61 for information on how to search for a SID. The system dispays a window that contains the SID data. Step 3: Verify the SID data Verify that the information for this SID is correct: If the information is correct, cick Accept. If the information is not correct, cick Back to enter a new SID number. The system dispays a confirmation window. Step 4: Cose the confirmation window In the confirmation window, cick OK to continue. The system dispays a Request to Deiver Fies Detai screen (Figure 74). Figure 74: Request to Deiver Fies Detai screen Issue 5.0 September

158 Deivering A Fie From RFA Step 5: Seect a deivery option On the Request to Deiver Fies Detai screen, seect one of the three deivery options: 1. Step 5a - Option one: Downoad Fies to My PC on page Step 5b - Option two: Downoad fies using e-mai on page Step 5c - Option three: Direct Connection on page 161 Step 5a - Option one: Downoad Fies to My PC To downoad RFA fies to your PC: 1. Cick Downoad Fies to My PC. The system dispays the Downoad Fies to My PC screen (Figure 75). Figure 75: Downoad Fies to My PC Screen 2. To downoad the fie, use one of the foowing options: Cick on the fie name: Use this option to send each fie separatey. After you cick on the fie name, the system dispays a fie downoad window (Figure 76). 158 Avaya Remote Feature Activation (RFA) User Guide

159 Deivering a fie from RFA procedure Figure 76: Fie Downoad Pop-up Window a. Cick Save in the Fie Downoad window. The system dispays a Save As window. b. In the Save in fied, enter the ocation on your computer to store the fie and cick Save. The fie downoads to your computer. The system dispays a confirmation window. Use Express Deivery: For a muti-modue system, use this option to request deivery of mutipe icense fies at one time. Express Deivery zips mutipe fies and sends them to the same e-mai address or computer. The system dispays a window that asks you to seect a singe ocation for a the fies (Figure 77). Figure 77: Express Deivery Pop-up Window Cick OK in the window. The system dispays a Save As window. Enter the ocation on your computer that you wi use to store the fie and cick Save. The zip fie downoads to your PC. The system dispays a confirmation window. For information on how to check the deivery status of your fie, see Chapter 7: Viewing The Deivery Status Of A Fie on page 163. Issue 5.0 September

160 Deivering A Fie From RFA Step 5b - Option two: Downoad fies using e-mai To downoad a fie using e-mai: 1. Cick Downoad Fies via E-mai. The system dispays a Downoad Fies via E-mai screen (Figure 78). Figure 78: Downoad Fies via E-mai screen The e-mai address that you entered in the Mod/Apps Detais screen automaticay appears in the E-mai Address fied. You can enter a new e-mai address, modify the e-mai address, or accept the e-mai address as it appears. An e-mai address that you enter or modify on this screen wi not automaticay appear in the Mod/Apps Detais screen. 2. Perform one of the foowing actions: Cick Submit to deiver a singe fie to a specified e-mai address. Cick Express Deivery to e-mai mutipe fies to a singe e-mai address. The system dispays a confirmation window when the e-mai is sent. For information on how to check the deivery status of your fie, see Chapter 7: Viewing The Deivery Status Of A Fie on page Avaya Remote Feature Activation (RFA) User Guide

161 Deivering a fie from RFA procedure Step 5c - Option three: Direct Connection With the Direct Connection option, RFA uses the dia-in teephone number or the IP address that is administered in the Modue/Appications Detais screen to oad the icense fie on the DEFINITY server. The Direct Connection option is avaiabe for DEFINITY servers ony. This option does not appear if you are working with any other Communication Manager systems. To downoad a icense fie using Direct Connect: 1. Cick Insta Fies on Product via Direct Connection. The system dispays the Insta Fies on Product via Direct Connection screen (Figure 79). Figure 79: Insta Fies on Product via Direct Connection screen The dia-in teephone number entered in the Mod/Apps Detais screen automaticay appears in the dia-in teephone number fied. You can enter a new dia-in teephone number, modify the teephone number, or accept the teephone number as it appears. Dia-in teephone numbers you enter or modify in this screen wi not automaticay appear in the Mod/Apps Detais screen. 2. Verify that the dia-in teephone number or the IP address is correct and cick Submit. The system dispays a confirmation window. For information on how to check the deivery status of your fie, see Chapter 7: Viewing The Deivery Status Of A Fie on page 163. Issue 5.0 September

162 Deivering A Fie From RFA 162 Avaya Remote Feature Activation (RFA) User Guide

163 Chapter 7: Viewing The Deivery Status Of A Fie About this chapter This chapter expains how to view the deivery status of a fie. This procedure is the same for a RFA product famiies. View My Fie Deivery Status procedure Use the procedure in this section to view the deivery status of your RFA fie. Be sure to og in to RFA and seect the appropriate product famiy for which you are going to create, modify, or deiver a icense fie. High-eve steps The foowing ist summarizes the steps that you must perform to view the deivery status of a fie: 1. Step 1: Seect a date range and a status on page Step 2: Seect a singe record to see a detaied status report on page Step 3: Review the detaied status report on page 166 The foowing section provides instructions for each of these steps. Issue 5.0 September

164 Viewing The Deivery Status Of A Fie Detaied steps Use the foowing detaied steps to view the deivery status of a fie. Step 1: Seect a date range and a status To view the deivery status of your RFA fies: 1. Seect the appropriate date range for the icense fies that you want to check. 2. Seect the appropriate status for the icense fie status that you want to check. Seect Show Ony Un-Checked Statuses uness you previousy marked this deivery request as Don t Show Again. 3. Cick Retrieve. The system dispays a summary deivery status ist (Figure 80). Figure 80: View My Fie Deivery Status search resuts 164 Avaya Remote Feature Activation (RFA) User Guide

165 View My Fie Deivery Status procedure Step 2: Seect a singe record to see a detaied status report From the deivery status summary ist, cick Request Number for the deivery status you want to view. The system dispays the View My Fie Deivery Status screen (Figure 81). Figure 81: View My Fie Deivery Status detai screen Issue 5.0 September

166 Viewing The Deivery Status Of A Fie Step 3: Review the detaied status report Review the information on the View My Deivery Status Report screen. If the Deivery Status shows DELIVERED, the fie was successfuy deivered. If the Deivery Status does not show deivered, check the error message fieds. If the error information does not hep resove the probem, contact the RFA HepDesk. If the status shows in progress, cick Back to refresh the screen and then cick Request. You can refresh the screen as many times as necessary to check the status. When you finish, cick Cose to return to the RFA Appication Main Menu. To check the status on another fie deivery, cick Back. CAUTION:! CAUTION: If you requested that the icense fie be deivered using the Direct Connection option, then a Deivery Status of DELIVERED means that the fie was successfuy deivered from RFA to the DEFINITY system. If you requested that the fie be deivered using the fie downoad or the e-mai option, then a Deivery Status of DELIVERED means that RFA successfuy sent the fie. It does not guarantee that the fie was received. When you request that RFA deiver the fie using the Direct Connection option, RFA makes up to five attempts to connect to the DEFINITY server. What do you do next? After you verify that the fie was successfuy deivered to your aptop or an e-mai address, exit from RFA. Use the procedures in the product documentation to insta the icense fie on the product. 166 Avaya Remote Feature Activation (RFA) User Guide

167 Chapter 8: Viewing And Changing Your RFA Authorization Information About this chapter This chapter expains how to view and change your RFA authorization information. This procedure is the same for a the RFA product famiies. You might need to change your RFA authorization information for two reasons: If you are an Avaya associate and your job function changes, you must request a change to your registration information. If you are a BusinessPartner, your RFA registration information incudes one or more GAIs. As a BusinessPartner, you are ony aowed to access certain system records. Those records must incude one of the GAIs that are in your RFA registration information. If you change empoyers, you must request a change to your registration information to have access to the proper system records. If you do not request a change to your registration information and your previous empoyer reports your departure, you are ocked out of RFA. Procedures to View and change your authorization information Use the information in this section to view and change your authorization information. High-eve steps To change your RFA authorization information: 1. Step 1: Cick My RFA Authorization Information on the RFA Appication Main Menu on page Step 2: Request the appropriate change on page 169 The foowing section provides instructions for each of these steps. Issue 5.0 September 2007

168 Viewing And Changing Your RFA Authorization Information Detaied steps Use the foowing detaied steps to view or change your authorization information. Step 1: Cick My RFA Authorization Information on the RFA Appication Main Menu On the RFA Appication Main Menu, cick My RFA Authorization Information. The system dispays the My RFA Authorization Information screen (Figure 82). Figure 82: My RFA Authorization Information screen 168 Avaya Remote Feature Activation (RFA) User Guide

169 Procedures to View and change your authorization information Step 2: Request the appropriate change For Avaya Associates If you are an Avaya associate, you can request a change ony to your job function. Seect the appropriate job function from the ist and then cick Submit. Your request to change your job function is sent to a RFA administrator for review and approva. For BusinessPartners If you are a BusinessPartner, you can request ony the addition of one or more GAIs by cicking Add GAI then Submit. Your request to add one or more GAIs is sent to the BusinessPartner s administrator for review and approva. Requests to change your RFA registration information can take two or three days to process. Issue 5.0 September

170 Viewing And Changing Your RFA Authorization Information 170 Avaya Remote Feature Activation (RFA) User Guide

171 Chapter 9: Working With Transaction Records About this chapter This chapter expains how to: Find and continue work on a transaction record on page 171 Deeting a transaction record on page 174 The procedures in this chapter are the same for a the RFA product famiies. If you ony want to view a SID or a transaction number do not use Modify RFA Record, Work with My Pending Transactions, or Work with system record. Use the search functions to ocate these records. Find and continue work on a transaction record Previous chapters expain how to create or modify a icense fie from start to finish. However, on some occasions you might aso want to start a process and then stop and restart the process again ater. The foowing ist shows some exampes: The same person does not have to compete a the steps that are necessary to create or modify a icense fie. A project manager might start the transaction and compete the customer and feature screens, but might not have the seria number information. The project manager might ask the technician to add the seria number or Host ID to compete the transaction. An upgrade or an update from a pre Reease 10 Avaya processor requires a switch configuration fie. To obtain a switch configuration fie use the Feature Extraction Too (FET). To use the FET, you must have the RFA transaction number. After you obtain the transaction number, you might not want to eave RFA running whie you use FET. You can exit and then return to RFA to compete the transaction after you obtain the FET fie. Issue 5.0 September

172 Working With Transaction Records Working with transaction records procedure RFA provides two methods to find and continue work on a transaction record: 1. Method one: Using the RFA Appication Main Menu on page Method two: Using the Search/View Menu on page 172 Use method 1 if you created the transaction and you know the transaction number. You must have created the transaction, or you must have been the ast person who modified the transaction for the number to appear in your pending transaction ist. Use method 2 if you did not create the transaction but want to continue working on it. Method one: Using the RFA Appication Main Menu To use the RFA Appication Main Menu to find a transaction record: 1. On the RFA Appication Main Menu, cick Work With My Pending Transaction Records. The system dispays a ist of a the open transactions that you created or modified. 2. Locate the desired transaction from the transactions in the ist and then cick on the associated number in the transaction number coumn. Method two: Using the Search/View Menu If you know the transaction number and you are the person who created the transaction or the ast person who modified the transaction, use the Work With My Pending Transaction Records option. To use the Search/View Menu to find a transaction record: 1. If you know the transaction number, cick Search/View Menu. Enter the transaction number in the Edit Transaction ID fied and cick GO. 2. If you do not know the transaction number, cick Search/View Menu > Advanced Search. Cick the down arrow on in the Seect a fied coumn to use one of the foowing options: Transaction Number (Fu vaue) SID (Fu vaue) Seria Number or Host ID (Fu vaue) Dia-in Teephone Number (Fu vaue) IP Address (Fu vaue) 172 Avaya Remote Feature Activation (RFA) User Guide

173 Working with transaction records procedure Sod to Customer Name (Partia or fu vaue) Tier I BusinessPartner Name (Partia or fu vaue) Tier II BusinessPartner Name (Partia or fu vaue) End Customer Name (Partia or fu vaue) Patform Type (fu vaue) SAP order # (Fu Vaue) Maintenance Troube Ticket # (Fu vaue) Appication PID (Fu vaue) Patform PID (Fu vaue) 3. Enter an associated vaue for the option that you seect in the Enter a vaue coumn. For exampe, if you seected Sod to Customer Name in the search fied, you coud enter a or part of the customer name in the Enter a vaue coumn. 4. Cick Search To use the search parameter to find the transaction, data for that parameter must exist in the transaction record. For some parameters RFA uses information from the SAP order. For other parameters, the person who creates and/or modifies the transaction record must enter the data. Which screen do you see when you find the transaction record? The screen that appears when you find the transaction record depends on where you were in the process when you stopped. If there are Type 3 warnings or informationa messages associated with the transaction, you see a message on the top of in the Genera Customer Info tab (Figure 83). Issue 5.0 September

174 Working With Transaction Records Figure 83: Genera Customer Info tab with warning You can find more information on the Type 3 Features warnings associated with this transaction by cicking the Features tab. For more information on Type III Feature warning and informationa messages, see Understanding the Features tab on page 30. Do you have to compete the transaction now? You can start, stop, and restart the process to create a system record as many times as necessary. However, after you enter a the information you must compete the transaction before you deiver the fie. Deeting a transaction record The SAP order number, the seria number or the Host ID and the transaction number can ony be used once in RFA. If you use the wrong SAP order number, seria number, or Host ID in a transaction record, you must deete the record and start over again. 174 Avaya Remote Feature Activation (RFA) User Guide

175 Deeting a transaction record! CAUTION: CAUTION: You can deete a transaction record ony before you compete it. A competed transaction record becomes a system record. You cannot deete a system record. You can deete a transaction from any screen within the transaction record. There are four steps to deete a transaction record: 1. Cick the Deete Transaction tab. The system dispays the deete warning screen (Figure 84). Figure 84: Deete Transaction screen You cannot cance out of the Deete Transaction screen. If you want to cance the transaction, perform one of the foowing actions to eave this screen: Cick a different tab Cick a different seection on the main menu 2. On the first warning screen, cick Submit. The system dispays the second warning screen. 3. On the second warning screen, cick OK. The system dispays the deete confirmation screen. 4. Cick OK on the confirmation message. The system dispays the RFA Appication Main Menu. Issue 5.0 September

176 Working With Transaction Records 176 Avaya Remote Feature Activation (RFA) User Guide

177 Chapter 10: Working With System Records About this chapter This chapter expains how you work with system records. To find and view, or find and change a system record you can: 1. Use Search/View menu 2. Modify the RFA record 3. Compete a pending system record The procedures in this section are the same for a the RFA product famiies with the exception of the competing a pending system record procedure. This procedure is avaiabe ony for the Communication Manger product famiy. If you want to view a SID or a transaction, do not use Modify RFA Record, Work with My Pending Transactions, or Work with system record. Use the search functions to ocate these records. Introduction The first time that you compete a transaction record, RFA creates a system record. A system record is a permanent record that contains the: Sod-to customer information Reease Category Features Capacities Seria number or Host ID SAP order information and previousy acquired entitements that are being carried forward Once RFA creates a system record, the record cannot be deeted. However, you can make changes to specific fieds within a system record. Instead of repacing the od information with the new information, RFA creates a new version of the system record. Issue 5.0 September

178 Working With System Records RFA uses the newest version of the system record to create the icense fie. The oder versions of the system record are stored in the RFA database and are no onger accessibe. Once the new version is created you can deiver the modified icense fie. Using the Search/View menu You might want to ook at a system record and not make any changes to: Verify the SID before you deiver a icense fie See what has changed from one version of the system record to another See what features are turned on or off How to find a system record when you do not know the SID To find a system record when you do not know the SID: 1. On the RFA Appication Main Menu, cick Search/View. The system dispays the Search/ View Menu (Figure 85). Figure 85: Search/View Menu 2. Cick Advanced Search, then in the Seect a fied coumn cick the arrow to use one of the foowing options: Transaction Number (Fu vaue) SID (Fu vaue) Seria Number or Host ID (Fu vaue) Dia-in Teephone Number (Fu vaue) IP Address (Fu vaue) Sod-to Customer Name (Partia or fu vaue) Tier I BusinessPartner Name (Partia or fu vaue) 178 Avaya Remote Feature Activation (RFA) User Guide

179 Using the Search/View menu Tier II BusinessPartner Name (Partia or fu vaue) End Customer Name (Partia or fu vaue) Patform Type (fu vaue) SAP order # (Fu Vaue) Maintenance Troube Ticket # (Fu vaue) Appication PID (Fu vaue) Patform PID (Fu vaue) 3. In the Enter a vaue coumn, enter an associated vaue for the option that you seect. For exampe, if you seect the Sod to Customer Name you coud enter a or part of the customer name in the Enter a vaue coumn. 4. Cick Search. 5. The search resuts shows the transactions or the system records for the option that you seected. Cick the bue SID number under the SID coumn to view the system record. Figure 86: Advanced Search for system records How to view a system record when you know the SID To use a SID to find a system record: 1. In the RFA Appication Main Menu, cick Search/View. The system dispays the Search/ View window (Figure 85). 2. In the View System ID (SID) fied, enter the SID. 3. Cick GO. 4. The system dispays information pertaining to the SID. This window contains any open transactions that are reated to the SID and a the SID versions. Issue 5.0 September

180 Working With System Records Modifying a system record You cannot make changes to the category, reease, features, or capacities, of a system record without a SAP order. However, even without a SAP order, you want to change the system record for the foowing reasons: 1. Additions or changes: If an additiona BusinessPartner needs access to this system record you can add their GAI to the Customer and Genera System Information screen. If the customer s teephone number or point of contact changes you can update the Customer and Genera System Information screen. If the IP address or dia-in teephone number of the Avaya system changes you can update the Modue/Apps Detais screen. You do not need to create and deiver a new icense fie after making any of the above changes. 2. You need to turn features on or off on the Feature Information screen. The most common reason to change this screen is to turn off a feature that conficts with another feature. A new icense fie must be generated and instaed on the Avaya system for the changes to be effective. 3. Because of an issue with the hardware, a seria number or a Host ID swap-out must be performed. A new icense fie with the new seria number or a Host ID must be generated and instaed on the Avaya system. Procedure to modify a system record To modify a RFA Record. 1. Choose one of the foowing actions: For Communication Manager, cick RFA Record Update then seect Modify RFA Record. For a other products, from the RFA Main Menu cick Modify RFA Record. 2. Enter the SID and cick Retrieve.The system dispays the SID detais screen. 3. You must read the Genera System Information and cick Accept for tabs to be active. The system dispays the SID Accept Resuts screen. 4. Cick Continue. The system dispays the Customer and Genera Information screen. A tabs are now active. Update the data in the Customer and Genera Information, Modue/ App Detais, or Features tab. Cick Submit to enter any changes. 180 Avaya Remote Feature Activation (RFA) User Guide

181 Modifying a system record 5. Make a the required changes and then cick the Compete Transaction tab. The system dispays the Compete Transaction screen. 6. If you are ready to compete the modification of the system record, cick Submit. The system dispays a window that asks if you are sure you want to continue. 7. Cick OK to continue.the system dispays the SID Status screen. Record the new version number of the SID. Cick OK to return to the RFA Appication Main Menu or Print to print the screen. If you modified any feature information you must insta the new version of the icense fie on the Avaya system. From the RFA Appication Main Menu, cick Deiver Fies to deiver the modified icense fie. For information on how to deiver the fie see Chapter 6: Deivering A Fie From RFA on page 153. Competing a pending system record (Communication Manager ony) Why you might need to find and continue work on a system record If your Avaya system is being instaed in an Avaya configuration with mutipe Avaya servers, you might want to create and deiver icense fies to each server or modue at separate times. For exampe, you might enter the seria number for modue one, compete the transaction, and deiver the icense fie on the first day. Then a few days ater, you might want to add the seria number for modue two and deiver the icense fie for that modue. You can repeat the process unti you have entered the seria number and deivered the icense fie for each modue. How you can find and continue work on a system record There are two ways to find and continue work on a system record: If you created the system record, cick Work With My Pending System Records. A system record appears in your pending ist ony if you created it. If you did not create the system record, cick Compete a Pending System Record. Use this method, for exampe, if a co-worker asks you to work on a system record that the co-worker created. Issue 5.0 September

182 Working With System Records Work with your pending system records To work with your pending system records: 1. From the RFA Appication Main Menu, cick Work With My Pending System Records. The system dispays a ist of a your pending system records. 2. Cick the appropriate SID on the ist. You must review and accept the data on the System Information screen before the Modue/Appication Detais screen is avaiabe. 3. Make the necessary changes to the Modue/Appication Detais information and cick Submit. Compete a pending system record To compete a pending system record: 1. From the RFA Appication Main Menu, cick RFA Record Updates > Compete a Pending System Record. 2. Enter the System Identification number (SID) and cick Retrieve. 3. You must review and accept the System Information screen before the Modue/ Appication Detais screen is avaiabe. 4. Make the necessary changes to the Modue/Appication Detais information and cick Submit. 182 Avaya Remote Feature Activation (RFA) User Guide

183 Chapter 11: The Communication Manager Product Famiy In RFA About this chapter This chapter contains the foowing information: Working with Communication Manager icense and authentication fies on page 184 Creating a icense fie for an ESS server, WSP, LSP, or SRP on page 186 The Shared Bade Server on page 196 Additions, Upgrades R10+, and Migrations R10+ on page 197 Maintenance procedures for: - License fie seria number swap-out on page 224 For procedures on switch updates, Support Upgrades, and pre Reease 10+ upgrades, see Chapter 5: Updates and Upgrades on page 97. For information on RFA procedures that Communication Manager shares with other product famiies, see: Create a icense fie for a Communication Manager new insta, see Chapter 3: New Insta on page 63. Deiver a icense fie from RFA, see Chapter 6: Deivering A Fie From RFA on page 153. View the deivery status of a fie, see Chapter 7: Viewing The Deivery Status Of A Fie on page 163. View and change your RFA authorization information, see Chapter 8: Viewing And Changing Your RFA Authorization Information on page 167. Work with your transaction records, see Chapter 9: Working With Transaction Records on page 171. Issue 5.0 September

184 The Communication Manager Product Famiy In RFA Working with Communication Manager icense and authentication fies You wi find the foowing information in this section: When is a icense fie required for Communication Manager? on page 185 Creating a icense fie for an ESS server, WSP, LSP, or SRP on page 186 License-Error and No-License modes on page 187 Working with authentication fies on page 187 Using the Feature Extraction Too (FET) on page 194 Using the License Instaation Too (LIT) on page 195 Communication Manager systems requiring a icense fie The foowing Communication Manager systems require an RFA icense fie: Avaya DEFINITY Server R, SI, and CSI, Reease 10 or ater. Avaya DEFINITY ONE or IP600, Reease 10 or ater. Avaya servers: - S S S S S8700 series - Loca survivabe processors (LSP) - Enterprise survivabe servers (ESS) 184 Avaya Remote Feature Activation (RFA) User Guide

185 Working with Communication Manager icense and authentication fies When is a icense fie required for Communication Manager? License fies are required for Communication Manager for: New instaations Upgrades and updates - Upgrades: From pre Reease 10 From Reease 10 and ater - Updates: Support switch updates from pre Reease 10 Support switch updates from Reease 10 and ater License fie seria number swap-outs Additions A separate icense fie is required for each Avaya DEFINITY server or Communication Manager system incuding: The server compex DEFINITY Server R, SI, and CSI WAN Spare Processor (WSP) Survivabe Remote Processor (SRP) Loca Survivabe Processor (LSP) Enterprise Survivabe Server (ESS)! CAUTION: CAUTION: Avaya systems that are equipped with dupicated processors require ony a singe icense fie that contains the seria number for both processors. A icense fie is not required for Communication Manager when: A Communication Manager system is upgraded or updated to a dot software reease. A icense fie might be required for a dot reease if the reease incudes additiona features or functionaity purchased by the customer. Hardware is changed that does not affect the seria number in the icense fie. Issue 5.0 September

186 The Communication Manager Product Famiy In RFA Appications under the Communication Manager product famiy The Communication Manager product famiy contains the foowing appications: Communication Manager Ca Center Audix Appications appear in the foowing RFA tabs: SAP Order tab: Appications are isted in the Detaied Feature Information. Assign Order Items tab Modue/App Detais tab Features tab To view the appications in the Modue/App Detais and the Features tab, use the drop-down menu to seect the appication. A screen appears with the information for that appication. IP connect to Muti-Connect migration changes RFA 10.3 contains the foowing enhancements for systems migrating from IP connect to Muti-Connect and upgrading to Communication 4.0 or ater: A migration from IP connect to Muti-Connect does not invove a hardware change, therefore a new seria number is not needed and wi not be aowed in RFA. The Patform Type changes in the modue record. The migration from IP to Muti-Connect and the upgrade to Communication Manager Reease 4.0 or ater, must be on the same materia code. Creating a icense fie for an ESS server, WSP, LSP, or SRP A separate icense fie is required for every Avaya processor. RFA refers to each Avaya processor within an Avaya system as a modue. Each modue is assigned a Modue Identification (MID) number. Each system is assigned a System Identification (SID) number. For exampe, an ESS server, a WSP, an LSP, or a SRP are a considered modues. You might have one SID and mutipe MIDs if a network incudes mutipe ESS servers, WSPs, LSPs or SRPs. Use the RFA Additions functionaity when you add an ESS server, a WSP, an LSP, or a SRP. Before you cick Additions ensure that you have the SAP order number for the new modue. 186 Avaya Remote Feature Activation (RFA) User Guide

187 Working with Communication Manager icense and authentication fies You can choose the modue type from a ist of modues ocated on the Modue and Appications Detais screen. License-Error and No-License modes Communication Manager enters into a License-Error mode or a No-License mode when a vaid icense fie is not instaed or a icense fie mismatch occurs. A icense fie mismatch occurs when the seria number or the Host ID of the Avaya system does not match the seria number or the Host ID in the icense fie. An Avaya system in a License-Error mode generates a major aarm and begins a 30-day countdown timer. When the countdown timer expires, the system enters in to a No-License mode. In a No-License mode: LICENSE ERROR is dispayed on a stations and consoes when the stations and consoes go off-hook, but disappears when the first digit is pressed. This dispay message does not interfere with the norma use of any station or consoe. A termina ogin sessions are terminated. Any subsequent termina ogin sessions are imited to: - Maintenance commands - License Fie instaation commands Working with authentication fies In addition to the icense fie, Avaya servers that use an open operating system require an authentication fie. The authentication fie contains non-defaut passwords and Access Security Gateway (ASG) keys for the Avaya services ogins. When you create an RFA system record for an Avaya system Reease 11 and ater, RFA automaticay creates an authentication fie. The Avaya DEFINITY servers do not run on an open operating system and therefore do not require an authentication fie. For the S8100 Server Reease 10 or earier, the Automatic Registration Too (ART) is used to generate the authentication fie. ART is avaiabe to Avaya associates or the regiona registration teams. Issue 5.0 September

188 The Communication Manager Product Famiy In RFA! CAUTION: CAUTION: If you are going to request a new authentication fie, you must be ogged in to the server before you request the new ASG key. If you are not ogged in to server you wi be ocked out and wi not have access to the server. You can use the same deivery methods for authentication fies as you do for icense fies. For information see Chapter 6: Deivering A Fie From RFA on page 153. CAUTION: You can request that the authentication and icense fie be deivered at the same time or different times.! CAUTION: Aways insta the icense fie before the authentication fie. You do not have to request a new deivery of an authentication fie each time that you request a icense fie uness you require a change in the ASG key. Type II Per User upgrades A new feature setting type caed Per User has been created to be used in materia codes associated with upgrades. Using the Per User upgrade functionaity ensures that the correct number of users, stations, etc., purchased with an upgrade are enabed in the RFA icense fie. The Per User upgrade functionaity is appicabe to a product famiies supported by RFA. When a SAP order is generated to upgrade Communication Manager to a 4.0 or ater reease, some feature upgrades are sod at a per user basis. An exampe of a Type II feature sod at a Per User basis is stations. When stations are being upgraded to Communication Manager 4.0 or ater, a Feature Keyword of VALUE_STA with a setting type of PER USER is appied to the icense. Care shoud be taken to ensure that the correct number of stations is ordered. The quantity to be upgraded shoud not exceed the amount of stations on the system as you can never upgrade more features than you have. Aso, any Per User features that were not upgraded during the upgrade transaction are not carried forward and cannot be recaimed in a future transaction. To view Type II features and their associated Setting Types, RFA provides a Detaied Feature Information button that appears on the bottom of the SAP Order screen as shown in Figure Avaya Remote Feature Activation (RFA) User Guide

189 Working with Communication Manager icense and authentication fies Figure 87: Detaied Feature Information button on SAP Order screen After cicking Detaied Feature Information, the Detaied Feature Information screen appears. The Detaied Feature Information screen dispays tabes that contain the Type I, Type II, and Type III feature information that are on the SAP order. The Type II Feature Information tabe contains Feature Keywords, settings, setting type, and materia codes. Figure 88 shows an exampe of a Type II Feature Information tabe. The materia codes shown in the exampes in this book may not be current or correct and shoud not be used as a reference when pacing an order in SAP. Figure 88: Type II Feature Information tabe Issue 5.0 September

190 The Communication Manager Product Famiy In RFA Per User feature enhancement exampes The foowing three exampes demonstrate how the Per User feature enhancement works. Exampe one: SAP upgrade order does not contain a the stations on the system In exampe one, Customer A has 30 stations. The SAP order contains a Feature Keyword in a Materia Code with a Setting Type of PER USER for the upgrade of 20 stations. The resuting RFA icense fie contains 20 stations at the reease specified on the order. The remaining 10 stations wi not be icensed in the RFA icense fie and wi not dispay in the RFA System Record for Customer A. Customer A can no onger use the unicensed stations and cannot incude the stations in another upgrade order. The remaining 10 stations are considered abandoned. Exampe two: SAP upgrade order contains more stations than on the system In exampe two, Customer B has 30 stations. The SAP order contains a Feature Keyword in a Materia Code with a Setting Type of PER USER for the upgrade of 40 stations. The resuting RFA icense fie contains 30 stations at the reease specified in the order. The remaining 10 stations wi not appear in the RFA icense fie or the RFA System Record for Customer B, therefore the purchased upgrade of the 10 stations cannot be used. You cannot upgrade more stations than you currenty have on the system. Exampe three: SAP upgrade order does not contain the correct Setting Type In exampe three, Customer C has 30 stations. The SAP order does not contain a Feature Keyword with a Setting Type of PER USER for the upgrade of the 30 stations. In this case, RFA dispays a warning message if VALUE_STA is equa to zero for Communication Manager Reease 3.0 and ater systems. RFA wi not aow the transaction to compete. Upgrade guideines Refer to the foowing guideines when pacing an order to upgrade Communication Manager to 4.0 or ater: A Feature Keyword with a PER USER setting is used in orders to upgrade Communication Manager from Reease 3.0 and ater. Upgrades from Communication Manager Reease 2.0 and earier reeases do not have the setting Per User associated with VALUE_STA. An RFA information or warning message appears if a PER USER setting type appears on one of the foowing orders for an upgrade from Reease 3.0 and ater: - New Insta - Upgrade Pre R10 - PCN Update Pre R10 - Support Upgrades 190 Avaya Remote Feature Activation (RFA) User Guide

191 Working with Communication Manager icense and authentication fies For Communication Manager 4.0 and ater, PCN Updates R10+ and PCN Updates are caed Support Upgrades. The name for PCN Updates Pre R10 has not changed. The Per User functionaity does not appy to Hosted Soutions and Support Upgrades. If the number of upgrades for a Per User feature is either beow or above the setting vaue on the current icense, a genera and/or detaied information warning message appears in RFA. RFA genera and detaied information/warning messages There are two categories of information/warning messages that appear in RFA for upgrades associated with features using a PER USER setting type. RFA uses genera messages to aert you that an issue has occurred. Some genera messages appear before the transaction is created whie others appear after the transaction is created but before the transaction is compete and the information on the order is appied to the RFA system record. Genera warning messages appear on the foowing screens: The SAP Order screen: The genera message appears before the order is accepted and once again after the order is accepted. The genera message appears for the foowing transaction types: - New Insta, Migrations Pre R10, and Support Upgrade: The message dispays after Accept is entered on the SAP Order tab. - Upgrade Pre R10 and PCN Updates Pre R10: The message dispays after the switch configuration fie has been upoaded. Order Items Assigned Screen: For an Upgrade R10+ transaction the message appears after cicking the Finish button on the Assign Order Items screen. Genera Customer Info: A message appears at the top of the Genera Customer Info screen. This message appears for the foowing transactions: - Upoad Switch Config tab - Upgrades Pre R10 - PCN Updates Pre R10 Detaied warning messages appear in the Features tab directy beow the Type II Feature information tabe. For information on the detaied warning messages, see Tabe 17. Exampes of the warning messages associated with each screen are expained in detai in the Job Aid for Per User Upgrade Warning Messages. The Job Aid can be found on the Features tab by cicking the More Information button and on the RFA Information page at, support.avaya.com. Issue 5.0 September

192 The Communication Manager Product Famiy In RFA! CAUTION: CAUTION: If you see information or warning messages on the RFA transaction, it is sti possibe to compete the transaction and deiver the icense fie. Be aware that if you do compete the transaction, the icense fie may not be correct. To avoid an incorrect icense fie, it is important that you understand the warning or informationa message and it is strongy recommended that you contact the Saes/Design team before competing the transaction. Feature screen enhancements for the PER USER upgrade functionaity Starting in March of 2007, RFA dispays warning messages when there is an issue with a Type II feature that has a PER USER setting type. The warning messages appear in a tabe directy after the Type II tabe on the Features screen. Figure 102 dispays an exampe of the Type II PER USER tabe. Figure 89: Type II PER USER Feature tabe The Type II Per User Feature tabe contains the foowing fieds: Per User Feature Keyword: Dispays the Feature Keyword contained on the order with the Setting Type of PER USER. Upgrade Setting Vaue from Order: Dispays the setting vaue associated with the Feature Keyword as it appears on the order. Setting Vaue on SID (Additions, Upgrades, Migrations) or Avaiabe to Upgrade (New Instas, Upgrade Pre R10 and PCN Updates Pre R10): Contains the current setting as it appears in the RFA system record and the RFA icense. A vaue of None appears for New Instas, Upgrades Pre R10, and PCN Updates Pre R10 transactions. 192 Avaya Remote Feature Activation (RFA) User Guide

193 Working with Communication Manager icense and authentication fies Warning Message: Contains detaied warning information describing the inconsistency between the setting vaue on the order and the setting vaue on the SID. Tabe 17 provides a ist of detaied warning messages that can appear in this fied. Tabe 14: Type II Per User warning messages Warning message RFA-239 RFA-240 RFA-241 RFA-242 RFA-243 Warning message description Per User Feature upgrades are not aowed on a New Insta transaction. RFA coud not compete this piece of the order. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. To view the Per User Feature upgrades on the order, seect the SAP Order tab, scro to the bottom of the screen, and cick on the Detaied Feature Information button. Look for features with a Setting Type of PER USER. Per User Feature upgrades are not aowed on an Upgrades Pre R10 transaction. RFA coud not compete this piece of the order. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. To view the Per User Feature upgrades on the order, seect the SAP Order tab, scro to the bottom of the screen, and cick on the Detaied Feature Information button. Look for features with a Setting Type of PER USER. Per User Feature upgrades are not aowed on a PCN Updates Pre R10 transaction. RFA coud not compete this piece of the order. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. To view the Per User Feature upgrades on the order, seect the SAP Order tab, scro to the bottom of the screen, and cick on the Detaied Feature Information button. Look for features with a Setting Type of PER USER. The upgrade setting vaue for feature VALUE_XYZ on the order exceeded the setting vaue for that feature on the SID. <Vaue> were upgraded, <Vaue> upgrades coud not take pace. You can compete the transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. The setting vaue for feature VALUE_STA on the SID exceeded the upgrade setting vaue for that feature on the order. <Vaue> were upgraded, the remaining <Vaue> on the SID were dropped. You can compete the transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. 1 of 2 Issue 5.0 September

194 The Communication Manager Product Famiy In RFA Tabe 14: Type II Per User warning messages (continued) Warning message RFA-244 RFA-245 Warning message description Feature <Feature Keyword> was on the SID with a setting vaue of <Vaue> but that feature was not on the order, therefore, the feature was dropped in the transaction and wi not appear in the new version of the SID. It is recommended that you consut with the Saes/Design team regarding this warning to correct the order. This order contains a materia code that indicates a Support Upgrade. If aso contains one or more Per User feature upgrades. Per User feature upgrades cannot be processed on orders that contain a Support Upgrade. RFA coud not compete this piece of the order. You can compete this transaction but it is recommended that you consut with the Saes/Design team regarding this warning before competion. To view the Per User feature upgrades on the order, seect the SAP Order tab, scro to the bottom of the screen, and cick on the Detaied Feature Information button. Look for features with a setting type of PER USER. 2 of 2 Support Upgrades The PCN Update R10+ and PCN Update RFA menu items have changed to Support Upgrades. Support Upgrades is an offer that entites a customer to appication upgrades for a specified period of time. SAP orders for Support Upgrades shoud not incude features with a Per User Setting types. The name change appears in the foowing RFA menu items: PCN Updates has changed to Additions, Upgrades, Support Upgrades Additions, Upgrades from R10+, PCN Updates from R10+, Migrations has changed to Additions, Upgrades from R10+, Support Upgrades, Migrations Using the Feature Extraction Too (FET) Use the Feature Extraction Too (FET) to capture the customer options and other data from Version 4 though Reease 9 Avaya systems. The FET reads the information from the DEFINITY server and saves the information to the configuration fie, aso known as the FET fie. You must have the RFA transaction number before you can use the FET to get the switch configuration fie. Use the FET if the system that you are upgrading or updating is: A DEFINITY Version 4 though Reease 9 upgrading to a Reease 10 or ater. Upgrading within the same patform such as the DEFINITY CSI, DEFINITY SI, DEFINITY R, or DEFINITY ONE/IP600 to S Avaya Remote Feature Activation (RFA) User Guide

195 Working with Communication Manager icense and authentication fies The FET captures features that are turned on in the existing system. The FET fie does not record features that are not turned on.! CAUTION: CAUTION: Run the FET to capture the existing system configuration before you upgrade the switch software. There are two ways to obtain the FET fie: Downoad the FET and the FET documentation from the RFA Information page at Execute the FET appication to obtain the FET fie from the switch and then upoad the FET fie to RFA. Run FET using the RFA appication by seecting the Upoad Using Direct Connection Option. RFA uses the FET appication to retrieve the FET fie from the server and then upoads the fie to RFA. To use the direct connection option, the DEFINITY server must be running Reease 8 or ater software and you must have dia-in connectivity to the server. Using the License Instaation Too (LIT) The License Instaation Too (LIT) is used to insta a icense fie from a computer to the foowing G3 Avaya servers running Communication Manager Reease 10 or higher: DEFINITY Server CSI with the TN2402 DEFINITY Server SI with the TN2404 DEFINITY Server R with the UN332C The LIT is not used with any other Avaya servers. Use the LIT if RFA cannot contact the G3 system directy. If you have a direct connect from RFA to the G3 system by way of Connect 2, RFA provides an option to deiver the fie directy onto the server. You can downoad the LIT and the LIT documentation from the RFA Information page at Issue 5.0 September

196 The Communication Manager Product Famiy In RFA The Shared Bade Server The Shared Bade Server (SBS3000) system uses virtua machines pus mutipe bades to aow mutipe instances of Communication Manager on one SBS3000 system. RFA contains a system record for each instance of Communication Manager running on an SBS3000 system. Each system record is popuated based on the specific instance of Communication Manger. RFA is aso used to generate additiona icenses over the ife of the system to support maintenance activities such as an IPSI or gateway repacement. Communication Manager software sets the icense mode accordingy at system initiaization and checks the icense fie at instaation and periodicay thereafter. RFA is not used to for registration to Avaya. You must manuay register the SBS3000 and the associated appications that run on the SBS3000 s virtua machines. For Communication Manager, RFA defauts to using CLAN registration to downoad a icense fie. If an aternate PCLAN configuration is used, the changes outined in Tabe 15 are required. Tabe 15: SBS icensing information Licensed Object FEAT_IP_PNC FEAT_PNS FEAT_ PRETH LSP SBS3000: Communication Manager in CLAN mode (defaut) SBS3000: Communication Manager in PCLAN mode SBS3000B: LSP Reference ISPI Seria number of the H.248 gateway Seria number of H.248 gateway Off On Off Off Off Off On Off Off Off On On For seria number information for the SBS3000, see RFA Reease 9.1 seria number enhancement on page Avaya Remote Feature Activation (RFA) User Guide

197 Additions, Upgrades R10+, and Migrations R10+ Additions, Upgrades R10+, and Migrations R10+ Use the procedure in this section to create a icense fie for a modue addition, an upgrade from a Reease 10+ system, and a patform migration from a Reease R10+ system. Before you start You wi need the foowing information before you create a icense fie for a patform migration: SAP order number SID of the existing system Seria number for the new patform. If are migrating to an S8500 Server without port networks, the seria number of a icense host gateway is used. The icense host gateway cannot contain an S8300 Server. Information and warning messages There are two categories of information/warning messages that appear in RFA for upgrades associated with features using a PER USER setting type. RFA uses genera messages to aert you that an issue has occurred when the information on the order was appied to the RFA system record. Genera warning messages appear on the foowing screens: The Continue screen: The genera message appears for the foowing transaction types: - New Insta, Migrations Pre R10, and Support Upgrade: The message dispays after Accept is entered on the SAP Order tab. - Upgrade Pre R10 and PCN Update Pre R10: The message dispays after the switch configuration fie has been upoaded. Order Items Assigned Screen: For an Upgrade R10+ transaction the message appears after cicking the Finish button on the Assign Order Items screen. Genera Customer Info: A message appears at the top of the Genera Customer Info screen. Detaied warning messages appear in the Features tab directy beow the Type II Feature information tabe. For information on the detaied warning messages, see Tabe 17. Exampes of the warning messages associated with each screen are expained in detai in the Job Aid for Per User Upgrade Warning Messages. The Job Aid can be found on the Features tab by cicking the More Information button or at the RFA Information page at Issue 5.0 September

198 The Communication Manager Product Famiy In RFA High-eve steps The foowing summarizes the steps that you must perform to modify the icense fie for a patform migration: Step 1: Cick Additions, Upgrades and Migrations on page 198 Step 2: Enter the SAP order number on page 199 Step 3: Verify that the SAP order data is correct on page 201 Step 4: Record the transaction number on page 204 Step 5: Enter the SID on page 204 Step 6: Verify the SID information on page 205 Step 7: Compete the Assign Patforms, Reeases, and Add Modues screen on page 205 Step 8: Compete the Customer and Genera System information on page 210 Step 9: Compete the Modue and Appication Detais information on page 213 Step 10: Compete the feature information on page 216 Step 11: Compete the transaction on page 222 Step 12: Record the SID and version number on page 223 Step 13: Deiver the icense fie on page 223 Detaied steps Step 1: Cick Additions, Upgrades and Migrations From the RFA Appication Main Menu, cick Additions, Upgrades and Migrations. From the drop-down menu seect Additions, Upgrades R10+ and Migrations. The system dispays the SAP Order Data screen (Figure 90). Figure 90: SAP Order Data 198 Avaya Remote Feature Activation (RFA) User Guide

199 Additions, Upgrades R10+, and Migrations R10+ Step 2: Enter the SAP order number Type the SAP order number in the text fied and cick Retrieve. The SAP order number must be between 1 and 10 digits.! Important: Important: Use the SAP order number that incudes the software right to use (RTU) materia codes and the hardware materia codes that are used for dupication. Do not use the SAP order number that incudes hardware materia codes ony. If software codes exist on more than one SAP order, use the SAP order number that contains the main serving vehice to create the system record. Then use the subsequent SAP order numbers and foow the process for each SAP order. In this situation, you first create and then modify the system record. You can use a singe SAP order number mutipe times, as ong as you appy the number to different product famiies. For exampe, when you insta a Converged Communications Server and a Communication Manager server, you can use a singe SAP order number to generate both icense fies for the Communication Manager server and the Converged Communications Server. If the SAP order number is vaid, the system dispays the SAP Order Data screen. If the SAP order number is not vaid, or if other probems exist with the order number, the system dispays an error message. See Tabe 16 for information on SAP error messages. Tabe 16: SAP error messages Error Messages Description Action The SAP order number is invaid. The SAP order number does not contain any software materia codes. The SAP order number does not contain the materia codes for the icensing of the product famiy for which you are buiding the icense. The SAP order number does not contain the materia codes needed to icense the product. Ensure that you have ogged in to the right product famiy and vaidate that you have the right materia codes. If the product famiy and materia codes are correct, contact the RFA Hepdesk. Contact the ordering team. 1 of 2 Issue 5.0 September

200 The Communication Manager Product Famiy In RFA Tabe 16: SAP error messages (continued) Error Messages Description Action You do not have permission to access the SAP order information. The SAP order number that you entered is aready in use for this product famiy. You can continue to work on the transaction record but cannot use this SAP order number to generate a new icense fie. This error message might appear to BusinessPartners trying to access a system record that does not contain their GUI. The SAP order number is aready in use in RFA to generate a icense fie for this product famiy. For information see Group Authorization Identification (GAI) on page 26. Ensure that you are ogged in to the right product famiy for the materia codes on your SAP order. If the product famiy is correct, a new SAP order number must be created to generate a icense. Contact the ordering team. 2 of Avaya Remote Feature Activation (RFA) User Guide

201 Additions, Upgrades R10+, and Migrations R10+ Step 3: Verify that the SAP order data is correct After you cick Retrieve, the system dispays the SAP Order Data screen (Figure 91). Figure 91: SAP Order Data screen Note the tab bar indicated by the arrow in Figure 91. Use the tab bar to move from one task to another. The product you are working on may rey on features that must be enabed on other product famiies. For a ist of product feature dependencies, cick the Licensing Dependency Tabe ink at the top of the screen. It is recommended that you use the information in this chart to ensure that you have a the features enabed that integrate with the product famiy you are working on. Review the SAP order data to ensure that the foowing information is correct: Sod To Customer Information The quantity, the materia code, and the description Information The information in the SAP Order screen shows ony the materia codes for the items that must be incuded in the icense fie such as the reease, the category, the features, and the capacities. This screen might not show everything that was ordered. Issue 5.0 September

202 The Communication Manager Product Famiy In RFA The SAP tab contains a Detaied Feature Information button as shown in Figure 92. Figure 92: SAP Order tab with the Detaied Feature Information button When seected, the Detaied Feature Information button dispays the foowing information: Tabes for the Type I, the Type II, and the Type III features that are contained on the SAP order (Figure 93). - The Type II Feature Information derived from the SAP Order tabe contains Feature Keywords, settings, setting types, and materia codes specified in the SAP order. This tabe can be used to verify features containing a PER USER setting type. - The Type III Feature Information derived from the SAP Order tabe dispays the reease the product ID is upgrading from and the targeted upgrade reease specified in the SAP order. An Understanding Type III Feature Information button that provides expanations and exampes about the Type III features. The Detaied Feature Information button is avaiabe in the SAP order tab anytime during the transaction. 202 Avaya Remote Feature Activation (RFA) User Guide

203 Additions, Upgrades R10+, and Migrations R10+ Figure 93: Detaied Feature Information screen Cick Back to return to the SAP Order Data screen. If a the SAP Order Data is correct, cick Accept. Cick Back if the SAP order data on this screen is for the wrong customer, or does not incude the software RTU materia codes and the hardware materia codes for dupication.! Important: Important: If the SAP Order Data shows the information for the correct customer, but either the customer information or the materia code is incorrect, do not continue. Contact the account team immediatey. The SAP order information must be correct before you create and deiver the icense fie. The system dispays the transaction number (Figure 94). Figure 94: Transaction Number screen Issue 5.0 September

204 The Communication Manager Product Famiy In RFA Step 4: Record the transaction number Record the transaction number that appears in the screen. You wi need this number ater. After you record the transaction number, cick Continue. The system dispays the SID Information (SID) screen. Step 5: Enter the SID Enter the SID for this Avaya system and cick Retrieve. After cicking Retrieve, the system dispays the SID Information screen (Figure 95). Figure 95: System Information (SID) screen 204 Avaya Remote Feature Activation (RFA) User Guide

205 Additions, Upgrades R10+, and Migrations R10+ Step 6: Verify the SID information Ensure that the information on the System Information screen is correct. Cick Accept if the information on the screen is correct. Cick Back to enter another SID. After you cick Accept, the system dispays the SID Accept Resuts screen. Cick Continue to continue with the transaction and dispay the Assign Patforms, Reeases, and Add Modues screen. Important:! Important: If this SAP order contains Type III Feature warnings or informationa messages, a message appears at the top of the SID Accept Resuts screen. The message aerts you to the warning or the informationa message and directs you to the Features tab for more information. Step 7: Compete the Assign Patforms, Reeases, and Add Modues screen There are three parts to Step 7: Step 7a: Patform migrations and Upgrades on page 205 Step 7b: Materia codes with mutipe operations on page 209 Step 7c: Adding a new modue on page 210 Important:! Important: If you are not famiiar with the Assign Patforms, Reeases, and Add Modues screen, see The Assign Patforms, Reeases, and Add Modues screen on page 266 before continuing this transaction. If RFA automaticay assigned a the operations to the appropriate modues, you cannot make any seections in the Existing Modue Detais section. To save the information and continue the transaction, cick Finish. Step 7a: Patform migrations and Upgrades Use the foowing high-eve steps to assign an upgrade or a patform migration operation to a modue: 1. In the SAP Order Detais section, seect the radio button next to the SAP segment number for the operation you want to assign. 2. In the Existing Modue Detais section, cick the check box for the modue that you want to associate with the operation. The sequence number and new patform type and/or reease appears in red in the modue box. Issue 5.0 September

206 The Communication Manager Product Famiy In RFA 3. If the quantity remaining for the operation is zero and there are additiona operations on the order, seect another operation by cicking the radio button next to the segment number for that operation. If a the operations have been assigned, and the quantity for the operations are zero, a Finish button appears at the bottom of the screen. Cick Finish to submit the data and continue the transaction. Patform Migrations For product famiies with ony one modue, RFA automaticay seects the modue for the patform migration. When RFA automaticay seects the modue, the Assign Patforms, Reeases, and Add Modues screen is dispay-ony. You can view and accept the seection by cicking Finish at the bottom of the screen. For muti-modue systems, RFA attempts to determine which modue to appy the patform migration to. If RFA cannot determine the modue to appy the migration to, you can seect the modue from a ist of existing modues. When a migration operation is seected, the system dispays a New Patform Type check box in each modue of the Existing Modue Detais section that meets the foowing criteria: The patform type for the existing modue is different than the patform type for the seected SAP order segment. The New Patform Type fied in the Existing Modue Detais section has not aready been popuated by a SAP segment number for a different patform migration operation. 206 Avaya Remote Feature Activation (RFA) User Guide

207 Additions, Upgrades R10+, and Migrations R10+ Figure 96: The Assign Patform, Reeases, and Add modues for a migration When you check the New Patform Type check box for a modue in the Existing Modue Detais section the foowing events occur: A red New Patform Type fied appears with the Patform Type of the seected operation. A red SAP Order Detais sequence number appears with the sequence number of the seected operation. The Quantity Remaining fied in the SAP Order Detais section is decremented by one for the seected operation. Upgrades RFA considers an upgrade to be a change in the reease version of appications for modues. An upgrade can be partia or fu. In a partia upgrade ony some of the modues within a system are upgraded. In a fu upgrade, a modues within a system are upgraded. For a partia upgrade where there is ony one possibe seection, RFA automaticay assigns the operation to the modue. For operations where there is more than one possibe seection, RFA aows the user to seect the modue or appications that wi be upgraded using the Assign Patforms, Reeases, and Add Modues screen. Issue 5.0 September

208 The Communication Manager Product Famiy In RFA For a fu upgrade, RFA tries to determine the modues to upgrade and the reeases to use for the upgrade. If RFA cannot make an absoute determination of the modues to upgrade based on the SAP order, RFA aows the user to seect the modue and appications for the upgrade using the Assign Patforms, Reeases, and Add Modues screen. RFA vaidates the upgrade based on the foowing rues: The Communication Manager reease for an LSP must be equa to or greater than the main modue. The Communication Manager reease for an ESS server must be equa to or greater than the main modue. When a upgrade operation is seected from the SAP Order Detais section, the system dispays a New Reease check box in each of the modues in the Existing Order Detais section that meets the foowing criteria: The Modue Type fied for the operation in the SAP Order Detais section contains the same modue type as the modue in the Existing Modue Detais section. The Reease fied for the modue in the Existing Modue Detais section is different than the reease in the SAP Order Detais section for the operation. The New Reease fied for the modue has not aready been popuated by a different operation. 208 Avaya Remote Feature Activation (RFA) User Guide

209 Additions, Upgrades R10+, and Migrations R10+ Figure 97: The Assign Patforms, Reeases, and Add Modues for upgrades The foowing events occurs when you mark a check in the New Reease check box: A red New Reease fied appears dispaying the reease from the seected operation. A red sequence number appears. The Quantity Remaining fied in the SAP Order Detais section is decremented for the seected operation. Step 7b: Materia codes with mutipe operations An SAP order can contain a materia code with just one operation such as adding a modue, or a combination of operations such as a patform migration and an upgrade. When this happens you wi see the combination of operations within the Operation fied of the Assign Patforms, Reeases, and Add Modues screen. If the operation contains the wording and/or you may seect to perform either operation. You may continue to perform one or both of the operations unti the Quantity Remaining fied is equa to zero. If the operation contains the wording and you must seect both of the isted operations on the same modue. Issue 5.0 September

210 The Communication Manager Product Famiy In RFA If there is an add operation in a materia code with mutipe operations, the Add Modue box appears under the SAP Order Detais section. When the Add Modues box appears, the quantity inside the box defauts to a zero. To add a modue, type the number of modues you want to add to the system in the box and hit the enter key on your keyboard. In the SAP Order Detais section, the Quantity Remaining fied for the seected operation decrements by the number that you entered in the Add Modues box. Step 7c: Adding a new modue When the add modue operation is not combined with any other operation, RFA automaticay assigns the number of modues on the order. In this case the SAP Order Detais section shows the operation with the instruction that no action is necessary by the user. The Quantity Remaining fied dispays zero. Cick Finish on the bottom of the screen to accept the data and continue with the transaction. Step 8: Compete the Customer and Genera System information Step 8 has two parts: Step 8a Compete the GAI tabe on page 210 Step 8b: Compete the BusinessPartner and End User Customer information on page 211 Important:! Important: If this SAP order contains Type III Feature warnings or informationa messages, a message appears at the top of the Genera System Information screen. The message aerts you to the warning or the informationa message and directs you to the Features tab for more information. Step 8a Compete the GAI tabe Compete the GAI fieds as appropriate: If you are an Avaya associate, do not add a GAI in the ist uness you are starting a transaction that a BusinessPartner wi compete. You must add the GAI for any BusinessPartner who needs access to this record. If you are a Tier I BusinessPartner, your GAI is aready on this ist from the SAP order. You must add the GAI for any Tier II BusinessPartner who needs access to this record. 210 Avaya Remote Feature Activation (RFA) User Guide

211 Additions, Upgrades R10+, and Migrations R10+! CAUTION: CAUTION: If you make changes on this screen you must cick Submit before you go to another screen. If you do not cick Submit your changes are ost. Figure 98: Customer and Genera System Information Step 8b: Compete the BusinessPartner and End User Customer information Compete the Tier I BusinessPartner Information, Tier II BusinessPartner Information, and End User Customer Information fieds as appropriate: If this is a direct order, compete ony the End User Customer Information fieds. Cick Same As Sod To above the End User Customer Information fieds to copy the SAP Sod to Customer Information from the top of the screen. Then compete any empty fieds. If this is a BusinessPartner order, compete a three coumns. Since the Tier I BusinessPartner is probaby aso the Sod To Customer, cick Same As Sod To above that coumn to copy the SAP Sod To Customer Information. Then manuay enter the necessary information for the Tier II BusinessPartner and the customer. Issue 5.0 September

212 The Communication Manager Product Famiy In RFA Figure 99: Customer Information Screen Tier I, Tier II and End User Information You must enter a name in the Point of Contact s Name fied before you can compete the transaction. On the bottom of the Customer Information screen: Cick Submit if you have correcty fied out a the necessary fieds Cick Cear Form to cear the fieds and start again Cick SAP Order Data to view the SAP data that is associated with this icense fie After you cick Submit, the system dispays a window and asks if you want to continue. Cick OK to continue. The system dispays a Customer and Genera System Information screen with a message containing the status of your updates. 212 Avaya Remote Feature Activation (RFA) User Guide

213 Additions, Upgrades R10+, and Migrations R10+ Step 9: Compete the Modue and Appication Detais information Cick the Modue/App Detais tab. The system dispays the Modue and Appications Detais screen (Figure 100). Figure 100: Modue/Apps Detais screen for Communication Manager Step 9 has two parts: Step 9a: Review and change (if needed) the tabe information on page 213 Step 9b: Seect any additiona modues from the drop-down menu on page 216 Step 9a: Review and change (if needed) the tabe information If needed, change or update the appropriate tabes in the Modue and Appications Detais screen. Fieds in the Modue Information tabe change sighty depending on the product famiy. Issue 5.0 September

214 The Communication Manager Product Famiy In RFA The foowing ist describes each fied in the Modue Information tabe: Modue ID - This fied contains the modue ID number for this product or appication. The Modue ID is aways 1 if: - This is the Main server for Communication Manager. - This order does not contain mutipe modues. - The product famiy does not support mutipe modues. Modue Type - This fied contains a description of the modue type. Patform Type - The patform type identifies the type of hardware that this product uses. Modue Description (optiona but recommended) - Enter a name or a description to hep identify this modue such as "South Campus". Modue Location (optiona but recommended) - Enter a ocation to hep identify this modue such as "Room B2H10". IP Address (Communication Manager ony) - Enter the Internet Protoco (IP) Address for this modue if you want RFA to deiver the icense fie over a oca area network (LAN). Dia-in Teephone Number (Avaya DEFINITY servers ony) - Enter the teephone number for this modue if you want to use the RFA Direct Connection option over the INADS port to deiver the icense fie. Information that you enter in this fied automaticay appears in the dia-in teephone fied when you request deivery of a fie by way of the Direct Connection option. You must enter the teephone numbers in one of the foowing formats: - For the United States and Canada; +1 XXX XXX XXXX - For a other countries; +Country Code CityCode LocaPhoneNumber, Extension. Commas and extensions are optiona. Athough you cannot use the Direct Connection option with the Avaya S8000 series servers, you can enter the S8000 series dia-in teephone number in this fied. You can use the S8000 series dia-in teephone number with the search functionaity to find transaction or system records. E-mai Address - Enter the e-mai address if you want RFA to use e-mai to deiver the icense fie. Information that you enter in this fied automaticay appears in the e-mai address fied when you request the downoad of a fie by way of e-mai. Deivery Instructions - Enter notes on how you want the icense fie for this modue to be deivered. RFA does not use this information. This information is for the use of peope who compete the transaction or deiver the fie. For more information on how to deiver a icense fie see Chapter 6: Deivering A Fie From RFA on page 153. Cick Submit to save the information. If you enter information without competing the seria number or Host ID Information tabe, the system dispays a message that the non Host ID (or seria number) updates are successfu. 214 Avaya Remote Feature Activation (RFA) User Guide

215 Additions, Upgrades R10+, and Migrations R10+ Modue Seria Number Information Tabe - The existing seria number appears in the Current Seria Number fied. If this is a patform migration, a New Seria Number fied appears. If you are migrating to a patform with a different seria number, you can enter the new seria number in the New Seria Number fied. if the seria number is staying the same, eave the New Seria Number fied bank. RFA confirms the new seria number and dispays the status with any error messages in the Status and Error Messages fieds. Retrieve SN - If you are working on an Avaya DEFINITY server you have the option to have RFA retrieve the seria number from the processor board. To use this option, the software on the DEFINITY server must be Reease 9 or ater, and you must have dia-up connectivity. Use the foowing steps to enter data in the Retrieve SN fied: 1. Next to the seria number fied, cick Retrieve SN. 2. In the Dia-in Teephone Number fied, enter the dia-in teephone for the system. If a dia-in teephone number exists in the Modue Information tabe, that number automaticay appears in the Dia-in Teephone Number fied. 3. Cick Submit to connect to the system and retrieve the seria number. WARNING:! WARNING: The retrieve seria number process can take up to six minutes to compete. You can cick Cance this Request at any time to return to the Modue/Appication Detais screen from where you can enter the seria number manuay. 4. Once approved, the seria number is entered in the Seria Number fied in the Seria Number tabe. Appication Information Tabe - You do not need to compete the fieds in the Appication Information tabe. Appication - Contains the name of the product or appication that you are instaing. This fied is pre popuated using the information on the SAP order. Expiration Date - This fied is reserved for future enhancements. Appication PID (Communication Manager ony) - This number is assigned when registering the system for aarming. This fied is not required to create a icense fie. Reease Version - This fied identifies the version of the software. This fied is pre popuated with the information on the SAP order. To enter any changes that you made on this screen, cick Submit. The system dispays the Modue/Appication Detais screen with the status of the updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. Issue 5.0 September

216 The Communication Manager Product Famiy In RFA Step 9b: Seect any additiona modues from the drop-down menu Some Avaya systems contain more than one modue or appication. Use the drop-down menu that is beow the tab bar to view and seect additiona modues or appications. If this is a Communication Manager instaation with mutipe modues, you must enter modue and seria number information for each modue that you seect. For Unified Communications Center (UCC), you do not need to enter any additiona information. The information that you submit for one appication is automaticay copied to the other appication screens. Review, and if necessary, change or update the tabe information as instructed in Step 8a. Cick Submit to enter any changes made on this screen.the system dispays the Modue/ Appication Detais screen with a message about the status of your updates. If you make a mistake and want to start over, cick Cear Form. The system cears a the fieds that you changed since the ast time you cicked Submit. Step 10: Compete the feature information Cick the Features tab. The system dispays the Features Information screen (Figure 101). Figure 101: Feature Information screen If you are unfamiiar with the Features Information screen see Understanding the Features tab on page 30. If you are aready famiiar with the tabes, continue with step 10a. Step 10 has two parts: Step 10a: Make any necessary changes to the main modue on page 217 Step 10b: Make any necessary changes for the next modue on page Avaya Remote Feature Activation (RFA) User Guide

217 Additions, Upgrades R10+, and Migrations R10+ Step 10a: Make any necessary changes to the main modue Verify that the tabes in the Feature Information screen are correct. If not, make the necessary changes to the information. Warning messages - When RFA warning messages exist on the Features screen, a tabe appears directy after the Type II or Type III tabes. If a Type II warning message tabe dispays then there is an issue with a Type II feature that has a PER USER setting. If a Type III warning message tabe dispays, then the Type III Feature upgrades on the SAP order do not precisey correspond to the feature information in the RFA system record. The Type II warning tabe (Figure 102) contains the foowing coumns of information: Per User Feature Keyword: Dispays the Feature Keyword contained on the order with the Setting Type of PER USER. Upgrade Setting Vaue from Order: Dispays the setting vaue associated with the Feature Keyword as it appears on the order. Setting Vaue on SID (Additions, Upgrades, Migrations) or Avaiabe to Upgrade (New Instas, Upgrade Pre R10 and PCN Updates Pre R10): Contains the current setting as it appears in the RFA system record and the RFA icense. A vaue of None appears for New Instas, Upgrades Pre R10, and PCN Updates Pre R10 transactions. Warning Message: Contains detaied warning information describing the inconsistency between the setting vaue on the order and the setting vaue on the SID. Tabe 17 provides a ist of detaied warning messages that can appear in this fied. Figure 102: Type II PER USER Feature tabe Issue 5.0 September

218 The Communication Manager Product Famiy In RFA See Tabe 17 for a description of Type II Per User warning messages. Tabe 17: Type II Per User warning messages RFA message number RFA-239 RFA-240 RFA-241 RFA-242 RFA-243 Per User warning message description Per User Feature upgrades are not aowed on a New Insta transaction. RFA coud not compete this piece of the order. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. To view the Per User Feature upgrades on the order, seect the SAP Order tab, scro to the bottom of the screen, and cick on the Detaied Feature Information button. Look for features with a Setting Type of PER USER. Per User Feature upgrades are not aowed on an Upgrades Pre R10 transaction. RFA coud not compete this piece of the order. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. To view the Per User Feature upgrades on the order, seect the SAP Order tab, scro to the bottom of the screen, and cick on the Detaied Feature Information button. Look for features with a Setting Type of PER USER. Per User Feature upgrades are not aowed on a PCN Updates Pre R10 transaction. RFA coud not compete this piece of the order. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. To view the Per User Feature upgrades on the order, seect the SAP Order tab, scro to the bottom of the screen, and cick on the Detaied Feature Information button. Look for features with a Setting Type of PER USER. The upgrade setting vaue for feature VALUE_XYZ on the order exceeded the setting vaue for that feature on the SID. <Vaue> were upgraded, <Vaue> upgrades coud not take pace. You can compete the transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. The setting vaue for feature VALUE_STA on the SID exceeded the upgrade setting vaue for that feature on the order. <Vaue> were upgraded, the remaining <Vaue> on the SID were dropped. You can compete the transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. 1 of Avaya Remote Feature Activation (RFA) User Guide

219 Additions, Upgrades R10+, and Migrations R10+ Tabe 17: Type II Per User warning messages (continued) RFA message number RFA-244 RFA-245 Per User warning message description Feature <Feature Keyword> was on the SID with a setting vaue of <Vaue> but that feature was not on the order, therefore, the feature was dropped in the transaction and wi not appear in the new version of the SID. It is recommended that you consut with the Saes/Design team regarding this warning to correct the order. This order contains a materia code that indicates a Support Upgrade. If aso contains one or more Per User feature upgrades. Per User feature upgrades cannot be processed on orders that contain a Support Upgrade. RFA coud not compete this piece of the order. You can compete this transaction but it is recommended that you consut with the Saes/Design team regarding this warning before competion. To view the Per User feature upgrades on the order, seect the SAP Order tab, scro to the bottom of the screen, and cick on the Detaied Feature Information button. Look for features with a setting type of PER USER. 2 of 2 The Type III warning tabe (Figure 103) contains the foowing coumns of information: Product ID: This coumn dispays the product ID associated with the warning message. From Reease Version: This coumn dispays the reease of software that the product ID is currenty running. An entry of Any aows the product ID to upgrade from the current reease to the new reease specified in the To Reease Version coumn. When Any is used, RFA first upgrades the product IDs that are running the owest reease. Limit on From Reease: This coumn dispays the current imit for this product ID in the RFA system record. To Reease Version: This coumn dispays the reease that the product ID is upgrading to as specified in the SAP order. Limit on Order: This coumn dispays the maximum number of product ID upgrades contained on the SAP order. Warning Messages: This coumn contains one of the warning messages shown in Tabe 18. The Warning Message tabe aso contains a ink to the Job Aid for Type 3 Feature Upgrade Warning Messages. The job aid provides information that heps you to understand the warning messages shown in Tabe 18. Issue 5.0 September

220 The Communication Manager Product Famiy In RFA Figure 103: Features tab with Type III Feature Warning See Tabe 18 for a description of Type III warning and informationa messages. Tabe 18: Type III Feature Warning and warning messages RFA message number RFA-229 RFA-230 RFA-231 RFA-232 Type III warning message description There are no entries for the product ID. RFA coud not compete this piece of the order. You can compete the transaction now, but it is recommended that you consut the Saes/Design team regarding this warning before competion. There were no entries for the product ID at the reease specified on the order. RFA coud not compete this piece of the order. You can compete this transaction now, but is recommended that you consut with the Saes/ Design team regarding this warning before competion. The imit on the order exceeded the imit on the From Reease. The warning shows the number of the product IDs that were upgraded and the number of the product IDs that were not upgraded. You can compete this transaction now, but it is recommended that you consut with the Saes/ Design team regarding this warning before competion. The imit on the From Reease exceeded the imit on the order. The message dispays the number of the product IDs that were upgraded and the number of the product IDs that remain. You can compete this transaction now, but it is recommended that you consut with the Saes/ Design team regarding this warning before competion. 1 of Avaya Remote Feature Activation (RFA) User Guide

221 Additions, Upgrades R10+, and Migrations R10+ Tabe 18: Type III Feature Warning and warning messages (continued) RFA message number RFA-233 RFA-234 RFA-235 Type III warning message description The imit on the order exceeded the imit on a the avaiabe From Reeases that are ess than the To Reeases. The warning dispays the number that were upgraded and the number that coud not be upgraded. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. There were no entries for the product ID at a reease ess than the To Reease on the order. RFA coud not compete this piece of the order. You may want to inform the Saes/Design team of this warning. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. The imit on the From Reease exceeded the imit on the order. The message dispays the number that were upgraded starting at the owest From Reease. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. 2 of 2! CAUTION: CAUTION: It is sti possibe to compete the transaction and deiver the icense fie when a transaction contains an RFA warning or informationa message. Be aware that if you do compete the transaction, the icense fie may not be correct. To avoid an incorrect icense fie, it is important that you understand the warning or information message and it is strongy recommended that you contact the Saes/ Design team before competing the transaction. If you make any changes to the feature information, you must cick Submit. Cicking Submit saves the changes for the main modue ony. It does not save the changes for other modues in the system. To make changes on other modues in the system, see Step 10b: Make any necessary changes for the next modue on page 221. After you cick Submit the system dispays the Feature Information screen with the status of the updates. Feature dependency is vaidated when a change is made on the feature screen and before a transaction is competed. Vaidation ensures that the features are set correcty before you insta a icense fie. Step 10b: Make any necessary changes for the next modue If this system contains more than one modue, use the drop-down menu under the Feature Information heading to seect another modue. Then make any necessary changes to the feature information for the next modue in the ist. Cick Submit after you make any changes. Issue 5.0 September

222 The Communication Manager Product Famiy In RFA Cicking Submit ony saves the changes you made on the modue you are viewing. Repeat these steps unti you change and submit the feature information for a the modues in this system. After you enter the information for each modue and cick Submit, the system dispays the Feature Information screen with information on the status of the updates. Step 11: Compete the transaction Cick the Compete Transaction tab. The system dispays the Compete Transaction screen (Figure 104). Figure 104: Compete Transaction screen Before you can compete the transaction, you must verify that you reviewed the feature settings on a the modues and that you agree that the settings are correct. Verify that you reviewed the feature settings, seect the box next to the statement and cick Submit to compete the transaction. If you are not ready to compete the transaction you can eave the screen by cicking on one of the foowing: A different tab A different item on the RFA Appication Main Menu Important:! Important: Unti you compete the transaction, you have the option to deete the transaction. Once you compete the transaction the transaction becomes a permanent system record. You cannot deete a system record from RFA. 222 Avaya Remote Feature Activation (RFA) User Guide

223 Additions, Upgrades R10+, and Migrations R10+ Step 12: Record the SID and version number After you cick Submit on the Compete Transaction screen, the system dispays a window asking if you want to compete the transaction. If you want to continue, cick Ok. The system dispays the System Identification screen (Figure 105). Figure 105: System Identification screen Record the SID and the version number. The SID is a pointer to the system record in the RFA database.you need the SID to obtain the icense fie from RFA. Cick OK to cose the window or cick Print to print the window. After you cick OK, the system dispays the RFA Appication Main Menu. Step 13: Deiver the icense fie You must deiver the icense fie from RFA to the Avaya server or to a computer. For more information on deivering a icense fie see Chapter 6: Deivering A Fie From RFA on page 153. Issue 5.0 September

224 The Communication Manager Product Famiy In RFA License fie seria number swap-out Use the Seria Number Swap-Out function when: You repace the processor, the IPSI, or the MSSNE board A patform migration requires a new seria number that was not entered during the patform migration transaction. This section expains how to use RFA to modify the icense fie for a Reease 10 or ater Communication Manager system because of a seria number swap-out. Tip: Tip: This chapter contains steps that were in previous chapters. The steps are repeated so that the swap-out procedure is compete and can be downoaded or printed separatey from the rest of this document. Before you start To modify a icense fie for a seria number swap-out, you need the foowing information: The maintenance troube ticket number Important: Avaya associates use the Maestro ticket number. BusinessPartners use the ticket number from your troube tracking system. The od seria number The new seria number For more information on how to obtain a seria number for a Communication Manager system see Understanding seria numbers on page 39.! Important: A seria number can ony be used once within the Communication Manger product famiy. 224 Avaya Remote Feature Activation (RFA) User Guide

225 License fie seria number swap-out Overview When you repace a processor or a reference IPSI, the seria number of the new processor or reference IPSI no onger matches the seria number in the icense fie. When the Avaya system detects this mismatch, the system enters in to a License-Error mode. For more information see License-Error and No-License modes on page 187. To cear the License-Error and return the system to a License-Norma Mode you can: Remove the new processor or IPSI and reinsta the od processor or IPSI. Modify the icense fie so that the fie contains the seria number of the new processor or IPSI. Before you modify the icense fie, determine if repacing the new processor or IPSI soves the probem: If the new processor or IPSI does not sove the probem, remove it and reinsta the od processor or IPSI. If the new processor or IPSI soves the probem, foow the steps in this section to update the icense fie with the number of the new processor or IPSI.! CAUTION: CAUTION: Do not modify the icense fie unti you are sure that the new processor or IPSI soves the reported probem. If you modify the icense fie to contain the seria number of the new processor or IPSI, you must return the od processor or IPSI to Avaya for repair. The processor or IPSI cannot be re-instaed even if they are working propery. RFA does not aow you to deiver a icense fie that contains an invaid seria number. High-eve steps The foowing summarizes the steps that you must perform to modify the icense fie for a Reease 10 or ater processor swap-out: 1. On the RFA Appication Main Menu, Cick Maintenance. From the maintenance ist, cick License Fie Seria Number Swap-Out (Step 1: Cick License Fie Seria Number Swap-Out from the Maintenance menu on page 226). 2. Enter the maintenance troube ticket number and the seria number of the existing processor (Step 2: Enter the troube ticket number and the seria number of the existing processor on page 227). 3. Verify that the information on the License Fie Seria Number Swap-Out Resuts screen is correct (Step 3: Verify that the information on the resuts screen is correct on page 228). 4. Record the SID and the new SID version number (Step 4: Record the SID and the new SID version number on page 229). Issue 5.0 September

226 The Communication Manager Product Famiy In RFA 5. Enter the seria number of the new processor (Step 5: Enter the seria number for the new processor on page 229). 6. Compete the transaction (Step 6: Compete the transaction on page 230). The foowing section provides detaied instructions for each of these steps. Detaied steps Use this section for detaied steps that expain how to perform a swap-out. Step 1: Cick License Fie Seria Number Swap-Out from the Maintenance menu To perform a seria number swap-out on a Avaya system that is running Communication Manager Reease 10 or ater, cick Maintenance on the RFA Appication Main Menu. On the maintenance menu, cick License Fie Seria Number Swap-Out. The system dispays the License Fie Seria Number Swap-Out (Figure 106). Figure 106: License Fie Seria Number Swap-Out screen 226 Avaya Remote Feature Activation (RFA) User Guide

227 License fie seria number swap-out Step 2: Enter the troube ticket number and the seria number of the existing processor Enter the maintenance troube ticket number in the Maintenance Troube Ticket Number fied. Type the seria number of the od Avaya processor in the Seria Number fied and cick Retrieve. If you enter a vaid seria number the system dispays the License Fie Seria Number Swap-Out Resuts screen (Figure 107). If you enter an invaid seria number or a seria number in a system record that you do not have access to, the system dispays an error message. Perform the foowing actions to correct the error: Verify that you have the correct seria number from the processor board or the IPSI circuit pack. Verify that you read the seria number correcty. Verify that you entered the seria number correcty in to RFA. If the seria number does not work the second time, contact the RFA Hepdesk. Figure 107: License Fie Seria Number Swap-Out Resuts screen Issue 5.0 September

228 The Communication Manager Product Famiy In RFA Step 3: Verify that the information on the resuts screen is correct Read and verify that the information on the License Fie Seria Number Swap-Out Resuts screen is correct. This screen is read ony. You cannot change the information on this screen. If the information in the resuts screen is correct cick Accept. If the information in the resuts screen shows information for the wrong customer, cick Back. Verify that you entered the correct troube ticket and seria number. If the screen sti shows the wrong information, contact the RFA Hepdesk. After you cick Accept, the system dispays the Accept SID Resuts screen (Figure 108). Figure 108: License Seria Number Swap-Out Accept SID Resuts screen 228 Avaya Remote Feature Activation (RFA) User Guide

229 License fie seria number swap-out Step 4: Record the SID and the new SID version number Record the SID and the new SID version number and cick OK to cose the screen. Cick the Swap-Out Detais tab. The system dispays the License Fie Seria Number Swap-Out Detais screen (Figure 109). Modifying an existing system record changes the version number for the SID. The SID itsef does not change. Figure 109: License Fie Seria Number Swap-Out Detais screen Step 5: Enter the seria number for the new processor Enter the seria number of the new Avaya processor or IPSI circuit board in both fieds and cick Submit. If you enter a vaid seria number, the system dispays the message Pending Competion in the status fied. A window opens to confirm that the swap-out was successfu and to instruct you to compete the transaction. If you enter an invaid seria number, or a seria number that has aready been used for another Avaya Communication Manager system, the system dispays an error message. Reenter the correct seria number and cick Submit. Check the seria number to verify that you entered it correcty. If you sti receive an error message contact the RFA Hepdesk. Issue 5.0 September

230 The Communication Manager Product Famiy In RFA Step 6: Compete the transaction To cose the message, cick OK and then cick the Compete Transaction tab. The system dispays the Compete Transaction screen. If you are ready to compete the transaction, cick Submit. The system dispays the SID and the associated version number. CAUTION:! CAUTION: Unti you compete the transaction you sti have the option to deete the transaction record. Once you compete the transaction, the transaction becomes a permanent system record. You cannot deete a system record from RFA. You cannot cance from this screen. If you are not ready to compete the transaction, do one of the foowing: Cick a different tab Cick a different item on the main menu Cick OK to cose the window and return to the RFA Appication Main Menu. For instructions on how to deiver a fie from RFA see Chapter 6: Deivering A Fie From RFA on page Avaya Remote Feature Activation (RFA) User Guide

231 Chapter 12: Product Famiies Supported in RFA This chapter expains how RFA interfaces with the foowing product famiies: Advanced IP Phone Features on page 232 Appication Assurance Networking on page 232 Appication Design Environment (ADE) on page 233 Appication Enabement Services on page 234 Avaya IQ on page 235 (formay CCR) Avaya Proactive Contact on page 236 Branch Gateways on page 236 Communications Process Manager on page 238 Contact Center on page 239 Customer Interaction Express on page 240 Directory Enabed Management on page 240 Enterprise Network Management Consoe on page 241 Event Processor on page 241 Integrated Management on page 243 Meeting Exchange on page 244 Moduar Messaging on page 244 one-x Mobie on page 244 one-x Porta on page 245 Security Gateway on page 245 Softcients on page 247 Unified Communications Center (UCC) on page 247 Voice Sef Service (VSS) on page 250 Voice Over IP (VoIP) stations on page 250 For information on Communication Manager, see The Communication Manager Product Famiy In RFA on page 183. Issue 5.0 September

232 Product Famiies Supported in RFA Advanced IP Phone Features Advanced IP Phone Features is firmware for the Avaya 4600 series IP phone consisting of the Avaya IP Phone appication and a VPN cient. The Avaya 4600 phone uses the VPN cient to estabish a secure IPSec tunne for a traffic incuding signaing, media, and appication. The use of the phone is controed by the number of concurrent user icenses that is managed by a WebLM appication residing on a WebLM server. After the VPN tunne is estabished, the phone obtains a icense from the WebLM server and is aowed to register with Communication Manager. IP Phone Features does not require an RFA icense fie in version 1. If a customer purchases version 2, or purchases an upgrade from version 1 to version 2, an RFA icense fie wi be required. Use the RFA New Insta procedure when you upgrade from version 2, or when you upgrade from version 1 to version 2. When you upgrade from version 1 to version 2, you wi aso need to perform the RFA Additions procedure. Performing both procedures wi ensure that the icense fie contains the tota quantity purchased by the customer. Advanced IP Phone Features requires a icense fie for new instaations and additions. When creating a icense fie for the Advanced IP Phone Features the Host ID is used. Appication Assurance Networking Appication Assurance Networking (AAN) monitors appications on the wide area network of the customer to ensure that required eves of network services are obtained. AAN performs the foowing: Discovers the appications that are running on the network Monitors the quaity of service (QOS) of the network for each appication session over a specific network path Determines an aternate network path with a better QOS and reroutes the appication sessions without affecting service An RFA icense fie is needed to activate the foowing AAN features for new instaations and additions: Appication Assurance Networking CNA (Converged Network Anayzer): Web appication mode with reporting ony mode enabed Appication Assurance Networking APC (Adaptive Path Controer): Route assert mode enabed Appication Assurance Networking VOIP (voice over IP): VoIP appication modue 232 Avaya Remote Feature Activation (RFA) User Guide

233 Appication Design Environment (ADE) Appication Assurance Networking ENT (enterprise): Enterprise appication modue Appication Assurance Networking MMED (muti-media): Rea-time mutimedia appication modue Appication Assurance Networking STRM (streaming audio and video) Appication Assurance Networking WCO (WAN Cost Optimizer) A icense fie is obtained from RFA and instaed on the server that is running Appication Assurance Networking. The server s Host ID is used to icense the server. Once the icense fie is instaed, AAN uses WebLM as a icensing server. For information on how to insta the icense fie on to the server, see AAN product documentation. Appication Design Environment (ADE) Currenty, Diaog Designer (DD) is the ony appication in the ADE product famiy that requires a RFA icense fie. There are two major components of DD: A Deveopment environment that runs on a PC. A run time component that runs on a Web container on a Web server. The run time component is the ony component of DD that is icensed in RFA. DD requires an RFA icense fie for the foowing features: The Diaog Designer standaone package The Computer Teephony Integration (CTI) ibrary enabement The Computer Teephony Integration (CTI) ibrary universa enabement The IC ibrary enabement The IC ibrary universa enabement An RFA icense fie is required for new DD instaations and DD additions. Issue 5.0 September

234 Product Famiies Supported in RFA Appication Enabement Services! Important: Important: CVLAN is caed Appication Enabement (CTI) in RFA. Appication Enabement (CTI) is the new product famiy name for the product famiy formery known as Computer Teephony Integration (CTI). Currenty, the foowing appications are icensed by RFA for the Appication Enabement Services product famiy: CaVisor LAN (CVLAN) DEFINITY LAN Gateway (DLG) Teephony Services API (TSAPI) MVAP Server (caed Appication Enabement Connections in RFA) RFA supports the foowing Appication Enabement Services procedures: New instaations Additions Support Upgrades Changing the Host ID Upgrades RFA-icensed Appication Enabement Services appications An RFA icense fie is needed for new instaations and additions for the Appication Enabement Services appications shown in Tabe 19. Tabe 19: Appication Enabement Services information Product Famiy Appication Description Appication Name in RFA What is being icensed MVAP Server Appication Enabement Connections Number of connections CaVisor LAN CVLAN Appication Number of connections Proprietary inks 1 of Avaya Remote Feature Activation (RFA) User Guide

235 Avaya IQ Tabe 19: Appication Enabement Services information (continued) Product Famiy Appication Description Appication Name in RFA What is being icensed DEFINITY LAN Gateway DLG Appication Teephony Services API TSAPI Appication Number of users Number of advanced users 2 of 2 Avaya IQ! Important: Important: Avaya IQ is formay CCR. Avaya IQ does not dispay in the ist of product famiies in RFA. Seect CCR from the product famiy ist to create or modify a icense fie for Avaya IQ. Avaya IQ combines the current capabiities of CMS with the foowing additiona feature functionaity: Web based reporting Patform Choice Extensibe Database Combination of features found in Proactive Contact and CMS Greater capacity A new or updated icense fie is needed for Avaya IQ when perform the foowing procedures: New instaations Additions Upgrades Changing out the server for maintenance purposes (swap-out) Support Upgrades The Authentication Fie System (AFS) is used to create an authentication fie for Avaya IQ instaations and upgrades. For more information on how to use AFS, see Authentication Fie System (AFS) User Guide ( ) at the web site. WebLM is used as a icensing appication for Avaya IQ. The MAC address or Host ID of the server hosting the WebLM appication is used in RFA to generate the icense fie. For more Issue 5.0 September

236 Product Famiies Supported in RFA information on how to obtain the Host ID for your server, see Understanding Host IDs on page 44 Avaya Proactive Contact Avaya Proactive Contact is both a software and hardware product that provides a high performance predictive diaing functionaity for ca centers with inbound ca and high voume outbound cas with bending. A new or updated icense fie is needed for Avaya IQ when perform the foowing procedures: New instaations Additions Upgrades Changing out the server for maintenance purposes (swap-out) Support Upgrades Licensed Features The foowing features are icensed for Avaya Proactive Contact: Number of agents Number of agents with predictive diaing Number of supervisor workstations Number of teephone ines Number of CTI agents Number of CTI agents with predictive diaing Branch Gateways The G250 and the G350 media gateways are the ony RFA supported gateways in the Branch Gateways product famiy. License fie requirements for the G250 and the G350 media gateway vary depending on the configuration. 236 Avaya Remote Feature Activation (RFA) User Guide

237 Branch Gateways Use the information in Tabe 20 to determine when a RFA icense fie is needed. Tabe 20: Branch Gateways information tabe G250/G350 Configuration A Standaone G250 or a G350 without Virtua Private Networking (VPN). A standaone G250 or a G350 with VPN. A standaone G250 or G350 with an S8300 Server. A standaone G250 or G350 is with an S8300 Server and VPN. The G250 or G350 is remotey controed by a server. The G250 or G350 does not have VPN. The G250 or the G350 is remotey controed by a server. The G250 or the G350 has an S8300 Server acting as an LSP. The G250 or the G350 is remotey controed by a server. The G250 or the G350 has an S8300 Server acting as an LSP and has VPN. RFA icense required? No. Yes. You need one RFA icense fie to activate VPN. Yes. You need one RFA icense fie for Communication Manager. Yes. You need two RFA icense fies: One for Communication Manger One to activate the VPN feature No. Yes. You need one RFA icense fie for the LSP. Yes. You need two RFA icense fies: 1 for the LSP 1 for the VPN The seria number for the G250 or G350 Media Gateway Each Branch Gateway has a icense fie that contains a unique seria number. The same seria number cannot be used more than once within the Branch Gateways product famiy. When the G250 or the G350 has a VPN and an S8300 Server, you need two icense fies. In this case, the seria number of the G250 or the G350 can be used for both icense fies because each icense fie is created in a different product group. In this exampe, the G250 or the G350 with VPN is icensed in the Branch Gateway product famiy whie the S8300 Server is icensed in the Communication Manager product famiy. To identify the G250 or the G350 seria number type, show sys from the command ine interface. Issue 5.0 September

238 Product Famiies Supported in RFA Post instaation verification If you attempt to oad a icense fie with a seria number that does not match the seria number of the new G250 or the G350 media gateway: The icense fie fais to insta A SNMP notification is sent A message is written in the Sysog Activating the VPN After you oad the icense fie, you must perform a reset on the G250 or the G350 media gateway to activate VPN. A feature setting of 1 indicates that VPN is turned on. A feature setting of 0 (zero) indicates VPN is turned off. Repacing a Branch Gateway Before you repace a G250 or a G350 media gateway, you must identify a the icense fies that are currenty in use. You must obtain the new RFA icense fie(s) with the seria number of the new G250 or the G350 Media Gateway. You must insta the new icense fie(s) on the new G250 or the G350 Media Gateway to activate a the gateway features and functionaity. Communications Process Manager An RFA icense fie is needed for Communications Process Manager when you perform one of the foowing actions: New instaations Additions Swap-out: A swap-out is performed when the hardware that was used for the Host ID in the RFA icense fie needs to be changed out for maintenance purposes. A swap-out aows the user to enter a new Host ID and obtain a repacement icense fie. Support Upgrades Upgrades Communications Process Manager uses WebLM as a icensing server. The Host ID of the WebLM server is used in RFA icense fie as a unique identifier. For information on how to obtain 238 Avaya Remote Feature Activation (RFA) User Guide

239 Contact Center the Host ID see, Understanding Host IDs on page 44. Once you have obtained the Host ID, foow the instructions in this manua for the type of procedure that you are performing. Contact Center Contact Center started to use RFA for icensing with Reease Currenty, RFA is not used to icense Contact Center in a cases. When RFA is not used, you use the E-mai License Request process ocated at [email protected]. Contact Center is the name of the product famiy within RFA. Within the Contact Center product famiy, there currenty is a singe RFA supported appication caed Interaction Center (IC). RFA icense fies are used for Contact Center when: Interaction Center (IC) is ordered and purchased with Reease or ater. IC is used in a production environment. If IC is being used for demonstration or evauating purposes, an RFA icense is not needed. A singe WebLM (one Host ID) environment is used. If your Avaya Contact Center system incudes mutipe sites or a redundant muti server soution, you need a series of segmented icenses. Each segmented icense is specific to a WebLM appication in your Avaya Contact Center system. In these situations, RFA is not used to generate a icense fie. A permanent icense is needed. A change in the Host ID is needed. In the case where you need a new server with a new Host ID, you must use the RFA Swap-Out functionaity to create a new icense fie. E-mai icense request and Contact Center Use the existing e-mai icense request process when: IC is used in a non production environment, in which case IC uses a deveopment and test icense. IC was purchased with Reease 6.0.X through Reease 6.1.2, or upgrades from an earier reease. Mutipe WebLM appications are in use running mutipe segment icenses. The customer is evauating IC. IC contains a temporary icense. Issue 5.0 September

240 Product Famiies Supported in RFA An Operationa Anayst (OA) icense shoud be requested when you use the e-mai License Request process. Customer Interaction Express Customer Interaction Express (CIE) is a Contact Center appication that resides on a Microsoft based appication server. CIE deivers a suite of Contact Center functionaity incuding the foowing features: Soft ACD E-mai Routing Graphica Vectors Ski Based Routing IVR Soft Diaer Rea-time and historica Contact Center reporting An RFA icense fie is required for each CIE server. The icense fie contains the unique Host ID of server on which the CIE appication is instaed. You must obtain the Host ID of the server prior to accessing RFA to generate the icense fie. For information on how to obtain the Host ID see, Understanding Host IDs on page 44. Once you have obtained the Host ID, foow the instructions in this manua for the type of procedure that you are performing. Important: Customers may migrate from Business Contact Center (BCC) to CIE. Migrating from BCC to CIE requires an RFA icense fie. The New Insta procedure in RFA is used to generate the icense fie for the migration.! Important: Currenty, orders for CIE that are paced in the Tenovis SAP (Atas) box are not visibe to RFA. Orders paced in Tenovis SAP require a manua RFA process to generate a icense fie. To kick off the manua process, the SAP order information shoud be provided to the KSPA group who handes most of the Tenovis icense requests. Directory Enabed Management Directory Enabed Management requires an RFA icense fie for the foowing actions: 240 Avaya Remote Feature Activation (RFA) User Guide

241 Enterprise Network Management Consoe A new insta Additions Upgrades Swap-outs WebLM is used as a icensing appication for Directory Enabed Management. The MAC address or Host ID of the server hosting the WebLM appication is used in RFA to generate the icense fie. For more information on how to obtain the Host ID for your server, see Understanding Host IDs on page 44. Enterprise Network Management Consoe Enterprise Network Management Consoe (NMC) is a faut management too that provides the foowing functionaity: IP discovery in a customer s network Dispays IP devices in varies views such as subnet, system, and device type Management toos such as software update manager and network configuration manager NMC uses a cient server architecture. The customer may have mutipe cients and a singe server. An RFA icense fie is needed for NMC when you perform one of the foowing actions: New instaations Swap-out: A swap-out is performed when the hardware that was used for the Host ID in the RFA icense fie needs to be changed out for maintenance purposes. A swap-out aows the user to enter a new Host ID and obtain a repacement icense fie. Upgrades Communications Process Manager uses WebLM as a icensing server. The Host ID of the WebLM server is used in RFA icense fie as a unique identifier. For information on how to obtain the Host ID see, Understanding Host IDs on page 44. Once you have obtained the Host ID, foow the instructions in this manua for the type of procedure that you are performing. Event Processor Event Processor is an appication running on a Windows or Linux system that monitors user defined event streams and generates aerts based on rues that a user defines for the event streams. Issue 5.0 September

242 Product Famiies Supported in RFA An RFA icense fie is needed for Event Processor when you perform one of the foowing actions: A new insta An addition An upgrade A swap-out The foowing Event Processor attributes are icensed in RFA: The Distributed Processing feature The icensed number of input data sources The icensed number of output data sources An RFA icense fie is required for each Event Processor appication. The icense fie contains the unique Host ID of server on which the Event Processor appication is instaed. You must obtain the Host ID of the server prior to accessing RFA to generate the icense fie. Event Processor does not use WebLM as its icensing server. 242 Avaya Remote Feature Activation (RFA) User Guide

243 Integrated Management Integrated Management RFA supports the foowing appications within the Integrated Management product famiy: VoIP Monitoring Manager (VMM). An RFA icense fie is required for VMM 3.0 or ater. VMM versions earier than 3.0 do not require a RFA icense fie. VMM 2.1 does not use a RFA icense fie thus an upgrade from VMM 2.1 to VMM 3.0 is considered to be a new insta. Converged Network Anayzer (CNA) Tabe 21 shows the appications that are icensed by RFA for Integrated Management.. Tabe 21: Appication information for Integrated Management Appication Name What is icensed? VMM Appication (3.0 or ater) Number of endpoints: - Up to Additiona 2000 Gateways: - Up to 40 - Additiona 40 CNA Appication Additiona test pugs and anayzers On new instaations of VMM, a SAP order is used to enabe the minimum quantities for both endpoints and gateway capacity. The minimum quantity for endpoints is 2000 whie the minimum quantity for gateways is 40. The RFA New Insta capabiity is used to create a system record and generate a icense fie. For additiona VMM endpoint and gateway capacity, a SAP order is required. Endpoints and gateways are bunded together in quantities of 2,000 endpoints and 40 gateways. The RFA Additions capabiity is used to add the new capacity and generate a new icense fie. The Host ID or MAC address of the first Network Interface Card (NIC) on the WebLM server to icense is used to icense Integrated Management. Issue 5.0 September

244 Product Famiies Supported in RFA Meeting Exchange The Meeting Exchange Groupware Edition (MX-GE) S6100 Reease 1.0 conferencing soution uses the Avaya On-Demand Conferencing (ODC) adaptor to integrate the IBM groupware appications with an audio conference bridge. RFA is used to icense the number of supported Meeting Exchange Groupware Edition G.711 CODEX and the number of Meeting Exchange Groupware Edition ports. An RFA icense fie is required for each Meeting Exchange server. A unique Host ID is used to icense Meeting Exchange in RFA. Moduar Messaging Moduar Message requires a RFA icense fie for: New instaations Additions Support Upgrades Upgrades A change in the Host ID An RFA icense is required for the foowing Moduar Messaging features: Seats - The number of voicemai-enabed maiboxes Text-to-Speech/engine type/anguage - The number and the type of concurrent sessions of test-to-speech conversion icensed Patform - The messaging patform icensed. Different versions of Moduar Messaging work with Avaya, Microsoft, and IBM/Lotus messaging stores. one-x Mobie You need an RFA icense fie for one-x Mobie if you are performing one of the foowing procedures. A new insta An upgrade or update An additions 244 Avaya Remote Feature Activation (RFA) User Guide

245 one-x Porta A swap-out One-X Mobie uses WebLM as a icensing server. The Host ID of the WebLM server is used in RFA icense fie as a unique identifier. An RFA icense fie is required for each one-x Mobie server. For information on how to obtain the Host ID see, Understanding Host IDs on page 44. Once you have obtained the Host ID, foow the instructions in this manua for the type of procedure that you are performing. Once the icense fie has been obtained from RFA, foow the one-x Mobie documentation to downoad the icense fie onto the WebLM server. one-x Porta You need an RFA icense fie for one-x Porta if you are performing one of the foowing procedures: A new instaation An addition An upgrade Repacing the server for maintenance purposes (swap-out) One-X Porta uses WebLM as a icensing server. The Host ID of the WebLM server is used in RFA icense fie as a unique identifier. An RFA icense fie is required for each one-x Porta server. For information on how to obtain the Host ID see, Understanding Host IDs on page 44. Once you have obtained the Host ID, foow the instructions in this manua for the type of procedure that you are performing. Security Gateway Avaya ships the Security Gateway product famiy with a defaut icense fie. An Avaya Security Gateway does not require an RFA icense fie uness additiona capabiities are added. Additiona capabiities incude increasing the number of site-to-site connections and remote users. Since the Security Gateway unit is shipped with a defaut icense fie the Security Gateway does not have a corresponding system record in RFA. When you add additiona capabiities for the first time, use the New Insta option in the RFA Appication Main Menu. After the system record is created in RFA, use the RFA Additions functionaity to create any future icense fies. Issue 5.0 September

246 Product Famiies Supported in RFA When you create a icense fie, the RFA system record refects ony the additiona capabiities contained in the SAP order. RFA does not refect the defaut settings. You can use the RFA Features screen to view the additiona capacities. The Security Gateway combines both the capabiities of the defaut settings and the capabiities in the icense fie. Tabe 22 shows an exampe of a Security Gateway with increased capabiities. Tabe 22: Security Gateway exampe Scenario Site-to-Site Connections Remote Users The defaut settings of the Security Gateway The additiona capabiities from the SAP order RFA system record refects this tota Security Gateway provides this tota capabiity Security Gateway modes that require a icense fie Avaya requires a RFA icense fie on the foowing Security Gateway Soutions modes: SG5 Security Gateway SG5X Security Gateway SG200 Security Gateway SG203 Security Gateway SG208 Security Gateway Repacing a Security Gateway If you must repace a Security Gateway that has a icense fie, you must obtain a new icense fie with the seria number of the new Security Gateway. To obtain a new RFA icense fie you must contact a Avaya ADS Tier III associate at: Within the United States ca Outside the United States see jappe?page=avaya.css.openpage&temp.tempate.name=escaations_goba 246 Avaya Remote Feature Activation (RFA) User Guide

247 Softcients Softcients Currenty, SIP Softphone is the ony appication in the Softcients product famiy that requires an RFA icense fie. The Avaya SIP Softphone is a PC-based endpoint that uses SIP to enabe users to: Initiate and receive cas Send and receive instant messages SIP softphone has three supported configurations: Avaya SIP Infrastructure (Converged Communications Server): When the Avaya SIP Softphone operates in a CCS environment, the SIP Softphone uses TLS to communicate with Avaya CCS Reease 2.x and ater. The SIP Softphone impements features as according to IETF RFC 3261, IETF drafts for message-waiting indication, and a subset of the SIPPING 19 features where appicabe. Non-Avaya SIP Proxy, registrar, and endpoints: When the Avaya SIP Softphone operates in a non-avaya SIP Proxy environment, it uses TCP and UDP to communicate with other vendor s SIP proxies, registrar, and endpoints. The SIP Softphone impements the SIPPING 19 where appicabe. No SIP Infrastructure (Peer-to-Peer): When the Avaya SIP Softphone is instaed in an environment where no proxies are used, SIP Softphone provides basic teephony and IM functionaity when the softphone communicates directy with another Avaya SIP Softphone. Softcients requires a icense fie for the foowing procedures A new instaation Additions A Host ID swap-out A icense for SIP Softphone contains the maximum number of SIP Softphones that can be running at one time. Once the maximum number is obtained, a user who attempts to start a new session receives an error message. A singe modue type SIPSP_Main, exists for Softcients. Unified Communications Center (UCC) UCC is a suite of software appications that runs on desktop computers or aptop computers, pam and pocket PCs, and wireess teephones. Each UCC appication checks with the UCC Issue 5.0 September

248 Product Famiies Supported in RFA icense server to obtain a icense that aows the appication to run. UCC incudes the foowing appications: Avaya Web Messaging Appication (WMA) Avaya Web Coaboration Appication (WCA) Avaya Advanced Speech Access (ASA) UCC icense server A UCC icense sever refers to: The computer software that contros access to the UCC appications. The UCC icense server software is a product caed Avaya License Manager, which uses the UCC icense fie that you generate with RFA. The computer hardware where the UCC icense server software or Avaya License Manager is instaed. - If the customer purchases WMA, the UCC icense server is the UCC base server. - If the customer purchases ony ASA, the UCC icense server is the ASA server or UCC speech server. The UCC License Server uses a singe icense fie that contros access to the UCC appications. The UCC icense fie contains three genera types of information: Feature settings UCC software reease number Host ID 248 Avaya Remote Feature Activation (RFA) User Guide

249 Unified Communications Center (UCC) UCC Feature settings The UCC icense fie contains feature settings for each of the icensed UCC appications. For the Web Messaging and the Web Coaboration appications, the UCC icense fie contains the foowing feature settings: The number of seats: The number of peope who can use each UCC appication at the same time. The expiration date: After the expiration date the number of seats effectivey becomes zero. If no expiration date exists, the appications do not expire. For the ASA appication, the UCC icense fie contains the number of seats, the expiration date, and the number of: Automatic Speech Recognition ports text-to-speech sessions UCC software reease number The UCC icense fie contains the software reease number. The software reease number is based on the SAP order. Instaing the icense fie See the foowing documents at to insta the icense fie on UCC: For Speech Access, see the Avaya Unified Communication Center Speech Access Instaation Guide For UCC see the Unified Communication Center Base Server Instaation Guide Issue 5.0 September

250 Product Famiies Supported in RFA Voice Sef Service (VSS) The VSS product famiy contains the foowing appications: Interactive Response Voice Porta VSS uses the Host ID of the WebLM server and the WebLM appication to icense VSS. The foowing VSS features require an RFA icense: Enterprise icensing Number of concurrent ports active at one time. This feature is avaiabe for both Interactive Response and Voice Porta. Maximum number of Natura Language Speech server icenses active at one time. For Interactive Response, the maximum number of ports is icensed. For Voice Porta, the maximum number of connections is icensed. Text to Speech. For IR, the maximum number of concurrent ports from IR to speech servers is icensed. For VP, the maximum number of connections from VP to speech server is icensed. SNMP cient running on the IR server. Important:! Important: For the Feature Keywords associated with the icensed features, see Getting Started With Remote Feature Activation (RFA) at Voice Over IP (VoIP) stations Both the Interactive Response and the Voice Porta require the foowing features be active in the icense fie for the VoIP stations instaed on Communication Manager: The correct number of IP stations with the Feature Keyword VALUE_IP_STA activated for the correct number of IP stations. The correct number of stations activated with the Feature Keyword VALUE_STA activated for the correct number of IP stations. Registration feature with the Feature Keyword IP_IR_A activated. 250 Avaya Remote Feature Activation (RFA) User Guide

251 Appendix A: RFA enhancements Reease 9 enhancements Reease 9.0, Reease 9.1, and Reease 9.6 provided the foowing enhancements: RFA Reease 9.6 Type III Feature enhancements on page 252 RFA Reease 9.1 seria number enhancement on page 256 Overview of RFA Reease 9.0 enhancements on page 257 Terminoogy for RFA Reease 9.0 on page 257 RFA Main Menu changes on page 260 SAP Order tab and SAP Order Data button changes on page 261 Patform migrations on page 263 Upgrades on page 264 Features screen changes on page 264 The Assign Patforms, Reeases, and Add Modues screen on page 266 Hepfu hints on page 284 Important:! Important: This chapter assumes that the reader has a basic understanding of RFA. If you do not understand RFA basics, skip this section and go to Chapter 1: Getting Started on page 25 in the RFA User Guide. New RFA supported product famiies Starting in January of 2007, an RFA icense fie wi be required for Customer Interaction Express. For more information on Customer Interaction Express, see Customer Interaction Express on page 240. Issue 5.0 September

252 RFA enhancements RFA Reease 9.6 Type III Feature enhancements RFA Reease 9.6 contains the foowing Type III Feature enhancements: Detaied Feature Information button: The SAP tab contains a Detaied Feature Information button (Figure 110). Figure 110: SAP Order tab with the Detaied Feature Information button When seected, the Detaied Feature Information button dispays tabes for the Type I, Type II, and Type III features that are contained on the SAP order (Figure 111). The Type III Feature tabe, Type III Feature Information derived from the SAP Order, dispays the reease the product ID is upgrading from and the targeted upgrade reease specified in the SAP order. The tabe aso contains an Understanding Type III Feature Information button that provides expanations and exampes about the Type III features. The Detaied Feature Information button is avaiabe in the SAP Order tab anytime during the transaction. 252 Avaya Remote Feature Activation (RFA) User Guide

253 RFA Reease 9.6 Type III Feature enhancements Figure 111: Detaied Feature Information screen Type III Features warning and informationa messages: RFA dispays warning and informationa messages when Type III Feature upgrades on the SAP order do not precisey correspond to the feature information in the RFA system record. The foowing exampes generated a Type III Feature warning and an informationa message: - The SAP order specifies an upgrade of IP_XYZ from a reease 4 to a reease 5. The RFA system record does not show IP_XYZ running on a reease 4. In this case, a warning message is generated that expains why the upgrade was not performed, instructs the user to inform the saes/design team about the warning, and expains that it is possibe to compete the transaction but the upgrades did not take pace. - The SAP order specifies a quantity of 10 upgrades of IP_XYZ from reease 4 to a reease 5. In the RFA system record, RFA shows a quantity of 50 IP_XYZ features on reease 4. In this case, an informationa message dispays that informs the user that ony 10 IP_XYZ features were upgraded and 40 were not. Issue 5.0 September

254 RFA enhancements See Tabe 23 for a description of the Type III Feature warning and informationa messages. Tabe 23: Type III Feature warning and informationa messages Message number RFA-229 RFA-230 RFA-231 Warning and informationa message description There are no entries for the product ID. RFA coud not compete this piece of the order. You can compete the transaction now, but it is recommended that you consut the Saes/Design team regarding this warning before competion. There were no entries for the product ID at the reease specified on the order. RFA coud not compete this piece of the order. You can compete this transaction now, but is recommended that you consut with the Saes/ Design team regarding this warning before competion. The imit on the order exceeded the imit on the From Reease. The warning shows the number of the product IDs that were upgraded and the number of the product IDs that were not upgraded. You can compete this transaction now, but it is recommended that you consut with the Saes/ Design team regarding this warning before competion. RFA-232 RFA-233 The imit on the From Reease exceeded the imit on the order. The message dispays the number of the product IDs that were upgraded and the number of the product IDs that remain. You can compete this transaction now, but it is recommended that you consut with the Saes/ Design team regarding this warning before competion. The imit on the order exceeded the imit on a the avaiabe From Reeases that are ess than the To Reeases. The warning dispays the number that were upgraded and the number that coud not be upgraded. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. 234 There were no entries for the product ID at a reease ess than the To Reease on the order. RFA coud not compete this piece of the order. You may want to inform the Saes/Design team of this warning. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. 235 The imit on the From Reease exceeded the imit on the order. The message dispays the number that were upgraded starting at the owest From Reease. You can compete this transaction now, but it is recommended that you consut with the Saes/Design team regarding this warning before competion. If there is a Type III Feature warning or informationa message associated with your transaction, a genera warning message appears in the foowing screens: 254 Avaya Remote Feature Activation (RFA) User Guide

255 RFA Reease 9.6 Type III Feature enhancements - SID Accept Resuts: A warning or informationa message appears on the SID Accept Resuts screen immediatey after the SID is accepted. The warning or informationa message directs you to the Features tab for more information. - Order Items Assigned: A warning or informationa message appears after you cick the Finish button on the Assign Order Items screen. The warning or informationa message directs you to the Features tab for more information. - Genera Customer Info: A warning or informationa message appears on the top of the screen and directs you to the Feature tab for more information. Detaied warning or informationa messages appear in a Warning Message tabe (Figure 112) in the Feature tab. The Warning Message tabe contains the foowing coumns: - Product ID: This coumn dispays the product ID associated with the warning or informationa message. - From Reease Version: This coumn dispays the reease of software that the product ID is currenty running. An entry of Any aows the product ID to upgrade from any current reease to the new reease specified in the To Reease Version coumn. When Any is used, RFA first upgrades the product IDs that are running the owest reease. - Limit on From Reease: This coumn dispays the current imit for this product ID in the RFA system record. - To Reease Version: This coumn dispays the reease that the product ID is upgrading to as specified in the SAP order. - Limit on Order: This coumn dispays the maximum number of product ID upgrades contained on the SAP order. - Warning Messages: This coumn contains the warning or informationa message shown in Tabe 23. The Warning Message tabe aso contains a ink to the Job Aid for Type 3 Feature Upgrade Warning Messages. The job aid provides information that heps you understand the warning and/or informationa messages isted in Tabe 23. Issue 5.0 September

256 RFA enhancements Figure 112: Features tab with Type III Feature Warning Important:! Important: The warning and informationa messages do not stop you from competing the transaction and deivering the icense fie. However, if you do not read and understand the warning message before you compete the transaction, you may not get the resuts you expected from the SAP order. RFA Reease 9.1 seria number enhancement Prior to Apri 2006, RFA did not aow dupicated seria numbers in the same product famiy associated with a singe end-user customer. Starting in Apri 2006, RFA aows a main server and its associated LSP to use the seria number of the same gateway. This change pertains to environments where Shared Bade Servers (SBS3000) or S8500 Servers use H.248 gateways with at east one LSP. The main server and the first LSP can use the seria number of the same gateway in the RFA system record and icense fies. The foowing format is used: The 12 digit format of a seria number for the main server is entered as it is today for icensing a Communication Manager patform. The seria number for the first LSP is entered using the same 12 digits foowed by an s. After the first LSP, a other LSPs use the standard icensing practices. 256 Avaya Remote Feature Activation (RFA) User Guide

257 Overview of RFA Reease 9.0 enhancements Overview of RFA Reease 9.0 enhancements With the introduction of RFA Reease 9.0 you wi be abe to: Dispay the SAP order information anytime during the RFA transaction (SAP Order tab and SAP Order Data button changes on page 261). This enhancement is avaiabe for a product famiies. See the operations aowed by the materia code on the SAP order. Re-use an existing RFA icense fie when you perform a patform migration. This enhancement is avaiabe for the Communication Manager product famiy ony. Upgrade one or more Loca Survivabe Servers (LSP) or Enterprise Survivabe Servers (ESS) with one SAP order. This enhancement is avaiabe for the Communication Manager product famiy ony. Perform a combination of additions, upgrades, and migrations on a singe SAP order. This enhancement is avaiabe for the Communication Manager product famiy ony. Unsupported Communication Manager operations The foowing Communication Manager icense operations are not supported in RFA Reease 9.0: License move: Moving Communication Manager 3.x users (VALUE_STA) from one server to another server within the same company. License Sub-modue move: For exampe, moving an LSP behind a Main S8700 series server to an S8700 series server of another company. License conversion: For exampe, converting an S8300 ICC to an LSP. License merge: Consoidation of one or more icenses from one or more servers to a main server. Pease refer to the Communication Manager offer definitions for specifics on offers and supported processes. Terminoogy for RFA Reease 9.0 Read this section to become famiiar with new and existing terminoogy associated with RFA Reease 9.0. Issue 5.0 September

258 RFA enhancements Modues For the purposes of this document, the term modues appies to both the main modues and the sub-modues. Operations An operation is an action that is performed on a modue such as: A new insta An addition An upgrade to Reease 10+ A Support update to Reease R10+ A pre Reease 10 upgrade A pre Reease 10 update A migration Some materia codes contain more than one operation. For exampe, a materia code can contain an operation for a modue addition as we as an upgrade. Materia codes that add features or increase capacities do not have operations. The Operation coumn on the new Assign Patforms, Reeases, and Add Modues screen dispays a the operations that are contained in the SAP order. For more information on the Operation coumn, see The Assign Patforms, Reeases, and Add Modues screen on page 266. SAP order detai sequence number A sequence number is assigned to each operation on the SAP order. The sequence number appears in the foowing ocations in the Assign Patforms, Reeases, and Add Modues screen: SAP Order Detais section: The sequence number appears in the Sequence Number coumn. Existing Modue Detais section: The sequence number appears in red in the modue box when the modue is seected for the operation. For more information on the Assign Patforms, Reeases, and Add Modues screen, see The Assign Patforms, Reeases, and Add Modues screen on page Avaya Remote Feature Activation (RFA) User Guide

259 Terminoogy for RFA Reease 9.0 Quaified modues To quaify for the patform migration specified on the SAP order, a modue must be on a different patform than that on the order. To quaify for the upgrade specified on the SAP order, a modue must be running a different reease than that on the order. Fu upgrade When you upgrade a the modues in a system on one SAP order, you are performing a fu upgrade. Partia upgrade Starting with RFA Reease 9.0, you can upgrade any number of modues within a system. You do not have to upgrade a modues on one SAP order. When an upgrade does not incude a the modues in a system it is considered a partia upgrade. Patform migration A patform migration is performed when you change your Avaya system from one patform type to another. For exampe, if you change from a G3r to an S8700 Server, you are performing a patform migration. In some cases an upgrade to the atest reease of Communication Manager software accompanies the patform migration. Issue 5.0 September

260 RFA enhancements RFA Main Menu changes This section describes the RFA main menu item changes for Reease 9.0. RFA main menu for Additions and Upgrades An Additions and Upgrades main menu item dispays for the foowing product famiies: Appication Assurance Networking Appication Design Environment Appication Enabement (CTI) Integrated Management Meeting Exchange Moduar Messaging Persona Work Space SIP Enabement Services Security Gateway Softcients Unified Communication Center Voice Sef Service When you seect the Additions and Upgrades menu item, you can choose to perform an addition, an upgrade, or both an addition and an upgrade. RFA main menu for the Communication Manager product famiy The foowing changes were made on the RFA main menu in RFA Reease 9.0 for the Communication Manager product famiy (Figure 113): Additions, Upgrades, and Migrations menu item: You can use Additions, Upgrades, and Migrations to perform an addition, an upgrade, a patform migration, or any combination of the three. When you cick Additions, Upgrades, and Migrations, you can seect Additions, Upgrades R10+, and Migrations R10+, or Upgrade from Pre R10. New Insta and Migrations Pre R10: A Migrations Pre R10 and a New Insta are now on the same main menu seection. Systems migrating from a pre R10 reease do not have any information in RFA and are seen by RFA as a new insta. 260 Avaya Remote Feature Activation (RFA) User Guide

261 SAP Order tab and SAP Order Data button changes Figure 113: RFA main menu in Reease 9.0 SAP Order tab and SAP Order Data button changes This section describes the Reease 9.0 changes for the SAP Order tab and the SAP Order Data button. SAP Order tab The foowing enhancements were made in RFA Reease 9.0 for the SAP Order tab: SAP Order tab enabed on page 261 Aowabe operations on page 262 SAP Order tab enabed Starting with RFA Reease 9.0, the SAP Order tab remains enabed for a product famiies after you accept the SAP order data. You cannot accept the SAP order data more than once but you can view the data in the SAP order by cicking the SAP Order tab anytime during the RFA transaction. As a resut of the SAP Order tab being enabed during the RFA transaction, the SAP Order button has been removed from the Genera Customer Info tab for the foowing transactions: New Insta Additions, Upgrades from R10+, Support Upgrade from R10+, Migration Support Upgrade from pre-r10 Update from pre-r10 Issue 5.0 September

262 RFA enhancements Aowabe operations A materia code can have one or more operations associated with it. The materia codes for a particuar order are isted in a tabe in the SAP Order tab. The SAP Order tab dispays after you enter the SAP order number. The operations associated with the materia code are isted in the Aowabe Operations coumn. If the Aowabe Operations coumn is bank, the materia code can be used for any operation aowed by the product famiy. Figure 114: SAP Order tab with Aowabe Operations coumn SAP Order Data button The SAP Order Data button that appeared on the System Info (SID) screen has been renamed to Appied SAP Order Data. If the previous system record was created using an SAP order, you can view the atest version of the system record by cicking on the Appied SAP Order Data button. 262 Avaya Remote Feature Activation (RFA) User Guide

263 Patform migrations Patform migrations! Important: Important: With the introduction of RFA Reease 9.0 on March the 5th 2006, the foowing migration scenarios appy: - For migration SAP orders where there are no existing RFA system records (icense fie) such as a G3R Reease 9.x migration to an S8700 Reease 3.x: Seect the New Insta and Migrations Pre R10 main menu option. - For a migration SAP order where there is an existing RFA system record (icense fie) such as a G3r Reease 11.x migrating to an S8700 Reease 3.x: If the SAP order was generated on or after March 5th 2006, seect the Additions, Upgrades, and Migrations main menu option. RFA Reease 9.0 contains the foowing enhancements for patform migrations: A new screen caed Assign Patforms, Reeases, and Add Modues was created. The Assign Patforms, Reeases, and Add Modues screen is under the Assign Order Items tab and dispays during a transaction after the SAP Order and the SID are accepted. The Assign Patforms, Reeases, and Add Modues screen aows you to seect the modue for the patform migration(s) or dispay a patform migration assignment automaticay seected by RFA. For more information on how to use the Assign Patforms, Reeases, and Add Modues screen for a patform migration, see The Assign Patforms, Reeases, and Add Modues screen on page 266. The Modue/Appication Detais screen has been enhanced to accept a new seria number if the seria number changed due to the patform migration (Figure 115). A New Seria Number fied as been added to the Modue Seria Number Information box. If the seria number remains the same you can accept the existing seria number by eaving the New Seria Number fied bank. An entry in the New Seria Number fied is required if a dua processor is migrating to a singe processor. The system dispays an error if the user does not enter the new seria number. If a patform migration required a seria number change and the transaction was competed without entering the new seria number in the New Seria Number fied, an RFA Swap-Out procedure must be performed. Converting a modue type such as an LSP to an ESS server is not considered a patform migration and is not supported in RFA Reease 9.0. Issue 5.0 September

264 RFA enhancements Figure 115: Modue/Appication Detais screen with New Seria Number fied You can view the SAP order during the patform migration transaction by cicking Previousy Appied SAP Order Data or cicking the SAP Order tab. Upgrades A software upgrade is a change from an oder reease of software to a newer reease of software. In RFA Reease 9.0, the Assign Patforms, Reeases, and Add Modues screen is used for product famiies that aow upgrades. For the Communication Manager product famiy this incudes Upgrades R10+ and Support Upgrades R10+. For more information on how to use the Assign Patforms, Reeases, and Add Modues screen for an upgrade operation, see The Assign Patforms, Reeases, and Add Modues screen on page 266. Features screen changes The foowing RFA Reease 9.0 enhancements have been made to the Feature screen for the Communication Manager systems that contain muti-modues: Shared Features: - A shared feature is a feature that is common for a modues in a muti-modue system. In RFA 9.0 a new Shared Feature coumn appears in the Features Information screen for the type I, the type II, and the type III tabes (Figure 116). The vaid entries for this coumn are yes if the feature is shared or no if the feature appies to this main modue ony. A type III features are shared with the Shared Feature coumn set to a yes. 264 Avaya Remote Feature Activation (RFA) User Guide

265 Features screen changes Figure 116: Shared Features coumn on the Feature Information screen A shared feature dispays on the main modue ony. You wi not see a shared feature when you seect a sub-modue. A shared features are incuded in the icense fie for each sub-modue even though they do not dispay when you dispay the features for the sub-modue. There are some features that appy to a sub-modue ony. These features can be on the main modue and on the sub-modue with different settings. If the feature is a sub-modue feature it cannot be a shared feature. Radio buttons for Appy Changes to this Modue Ony and Appy Changes to A Modues: - The Appy Changes to this Modue Ony radio button ony appies to features that are not shared. If a feature is shared it wi be appied to a modues. This is true even if the Appy Changes to this Modue Ony radio button is seected. - The radio buttons for Appy Changes to this Modue Ony and Appy Changes to A Modues have been removed from the sub-modues. The radio buttons sti appear on the main modue. When you view the feature information for a modue, the system dispays a message that this action appies to the dispayed modue ony. Important:! Important: You must deiver a icense fie to every sub-modue in the system when you change a shared feature on the main server. Issue 5.0 September

266 RFA enhancements The Assign Patforms, Reeases, and Add Modues screen This section contains the foowing information: Overview on page 266 On-ine Hep on page 268 Screen ayout on page 268 How to use this screen on page 273 Patform Migrations on page 274 Upgrades on page 276 Materia codes with mutipe operations on page 278 RFA Reease 9.0 Exampes on page 278 Overview The Assign Patforms, Reeases, and Add Modues screen gives you the abiity to assign new patform types (Patform Migrations) and new reease versions (Upgrades) to existing modues, and to add modues (Add Modues) to the system based on the contents of the SAP order. The Assign Patforms, Reeases, and Add Modues screen dispays after you accept the SID on the System Information screen when you are performing one of the foowing: For the Communication Manager product famiy: - An add modue operation If you are performing a feature addition ony, the Assign Patforms, Reeases, and Add Modues screen does not dispay. - A Support Upgrade from R10+ - An upgrade from R10+ - A patform migration An upgrade (dispays for a product famiies that support upgrades) The Assign Patforms, Reeases, and Add Modues screen does not appear for the foowing operations (Communication Manager product famiy ony): Switch update pre R10 Switch update R Avaya Remote Feature Activation (RFA) User Guide

267 The Assign Patforms, Reeases, and Add Modues screen Support Upgrade from pre R10 Upgrade from pre R10 For an exampe of the Assign Patforms, Reeases, and Add Modues screen, see Figure 117. Figure 117: Assign Patform, Reeases, and Add Modues screen Use the Assign Patforms, Reeases, and Add Modues screen when performing the foowing operations: Addition of a new modue Patform migration Upgrade Patform migrations and upgrade Upgrade and add modue Patform migration and/or add modue Patform migration and upgrade and/or add modue Issue 5.0 September

268 RFA enhancements On-ine Hep RFA provides on-ine hep for the Assign Patforms, Reeases, and Add Modues screen. You can access the on-ine hep by cicking on the Hep button ocated at the top right of the screen or directing your computer mouse to a word underined in bue. The Hep button contains step-by-step instructions on how to use the screen. For an exampe of the hep screen, see Figure 118. Figure 118: Hep screen exampe Screen ayout The Assign Patforms, Reeases, and Add Modues screen can contain up three sections: The SAP Order Detais section on page 269 The Add Modues box on page 271 The Existing Modue Detais section on page 271 The foowing section provides detaied information on the three sections. 268 Avaya Remote Feature Activation (RFA) User Guide

269 The Assign Patforms, Reeases, and Add Modues screen The SAP Order Detais section The top section of the Assign Patforms, Reeases, and Add Modues screen is tited SAP Order Detais (Figure 119). Figure 119: SAP Order Detais section The SAP Order Detais section contains a ist of operations and information from the contents of the SAP order. The foowing information is provided for each operation: Seect: If RFA is abe to automaticay assign the operation to the existing modues, this coumn wi be bank. If RFA is not abe to automaticay assign the operation, a radio button appears in this coumn. The radio button aows you to seect the operation that you want to appy to the existing modue. The system automaticay seects the first radio button that appears in the Seect coumn by defaut. When you cick on a radio button for an operation, check boxes appear in the Existing Modues Detais section for each modue that is quaified for that operation (see Quaified modues on page 259). When the radio button is unchecked, the check boxes disappear. You seect the check box within each modue that you want to appy to the operation. Sequence number: A sequence number is assigned to the operation. The sequence number heps you to identify the operation assigned to a modue by appearing in red in the modue s box. For information on the modue box, see The Add Modues box on page 271. Operation: The operation coumn contains a description of the operation. Instructions: This coumn contains instructions for the operation. If the operation contains and/or you may seect to perform either operation on quaified modues. You may continue to perform one or both of the operations unti the Quantity Remaining fied is equa to a zero. If the operation contains and, both operations wi be appied to the modue you seect. For exampe, you coud seect three modues for an upgrade and migration operation where the quantity for the operation is three. The upgrade and migration operation wi be appied to a three seected modues. Issue 5.0 September

270 RFA enhancements The foowing instructions can appear for an operation: - No Action Necessary by User: This instruction appears if RFA automaticay assigned the operation to the modue. A Finish button appears at the bottom of the screen if a the operations on the order were automaticay assigned by RFA. - You may seect a new reease for an appication: This instruction appears for an upgrade operation. This operation may contain a quantity of one or more upgrades. Seect a modue for the upgrade operation from the ist of modues that appear in the Existing Modue Detais section. - You may seect a new patform type for a modue: This instruction can appear for a patform migration operation. This operation may contain a quantity of one or more migrations. Seect a modue for the migration operation from the ist of modues that appear in the Existing Modue Detais section. - You may add modues and/or seect a new patform type for a modue: This instruction can appear during a patform migration and/or an add modue operation. This operation can contain a quantity of one or more migrations and/or modue additions. The tota quantity ordered for this operation can be appied to migrating modues, adding modues, or a combination of migrating and adding modues. - You may add modues and/or seect a new reease for an appication: This instruction can appear during an upgrade and/or an add modue operation.this operation can contain a quantity of one or more upgrades or modue additions. The tota quantity ordered for this operation can be appied to upgrading modues, adding modues, or a combination of upgrading and adding modues. - You may add modues and/or seect a new patform type and new reease: This instruction can appear during a patform migration and upgrade, and/or an add modue operation. This operation can contain a quantity of one or more patform migrations and upgrades and one or more modue additions. The tota quantity ordered for this operation can be appied to adding modues, patform migrations, or a combination of adding and migrating modues. - You may seect a new patform type and new reease: This instruction can appear during a patform migration and upgrade operation. In an and operation you must perform operations on the same modue. Modue Type: This fied contains the type of modue that can be appied to this operation. Patform Type: This fied indicates the type of patform that you are migrating to or the patform type of the modue you are adding or upgrading. Appications: This fied contains the name of the appication. Reease on Order: - For an upgrade or an add modue: This fied dispays the reease of the appication in the modue that is being added. - For a migration: This fied dispays the current reease of the appication. 270 Avaya Remote Feature Activation (RFA) User Guide

271 The Assign Patforms, Reeases, and Add Modues screen Quantity Ordered: This fied dispays the quantity ordered for the operation. Quantity Remaining: This vaue equas the number in the Quantity Ordered fied minus the number of modues seected in the Existing Modue Detais section and/or added in the Add Modues box. When the quantity remaining for a operations on the SAP order is equa to zero, a Finish button appears at the bottom of the screen. The Add Modues box The Add Modues box appears in the Assign Patforms, Reeases, and Add Modues screen when an and/or or an and add modue operation exists on the SAP order and RFA cannot automaticay make the add modue assignment (Figure 120). The add modue operation can be combined with another operation such as an upgrade. When the Add Modues box appears the vaue inside the box is set to zero. To add one or more modues, enter the quantity in the Add Modues box and hit the enter key on your keyboard. In the SAP Order Detais section, the Quantity Remaining fied for the seected operation, decrements by the number that you entered in the Add Modues box.! Important: Important: You must hit the enter key on your keyboard after you type a vaue in the Add Modues box. If there are no add modue operations on the SAP order that need to be assigned by a user, the Add Modues box does not appear. If the operation is an Add Modue ony operation or if RFA automaticay assigned the Add Modue operation, you do not see the new modues on the Assign Patforms, Reeases, and Add Modues screen. To verify the addition of the new modue, cick on the drop-down menu in the Modue/Appications Detais screen. The drop-down menu contains a ist of a new and existing modues. Figure 120: Add modues box The Existing Modue Detais section The Existing Modue Detais section contains the modues that exist in the RFA system record (Figure 121). When there are more modues that quaify for an operation than the quantity ordered for the operation, you must choose the modue to appy to the operation from the ist of modues in the Existing Modue Detais section. Issue 5.0 September

272 RFA enhancements Figure 121: Existing Modue Detais section Existing RFA data dispays in back. As you seect the check box within a modue, the upgrade or migration information appears in red. Red information represents what the modue is upgrading or migrating to. Ten modues dispay on the Assign Patforms, Reeases, and Add Modues screen at one time. Links for additiona modues are provided on the bottom of the page. When you cick on a ink for additiona modues, the changes that you made on the existing screen are automaticay saved. You must cick Submit to save the data anytime you eave the Assign Patforms, Reeases, and Add Modues screen. For exampe, you must cick Submit when you cick on another tab or when you quit the transaction without finishing it. The Existing Modue Detais section contains the foowing RFA system record information: Modue ID number: The fied dispays the Modue ID (MID) number for this modue. For more information on the MID, see The Modue Identification (MID) number on page 30. Modue Description: This fied contains the description of the modue that was entered in the Modue/Apps Detais screen. If the Modue Description fied was not popuated in the Modue/Apps Detais screen this fied wi be bank. Modue Location: This fied contains the modue ocation that was entered in the Modue/ Apps Detais screen. If the modue ocation information was not popuated in the Modue/ Apps Detais screen this fied wi be bank. Modue Type: The system dispays the type for this modue ID. 272 Avaya Remote Feature Activation (RFA) User Guide

273 The Assign Patforms, Reeases, and Add Modues screen Patform Type: The system dispays the patform type for this modue ID, Appication: The system dispays the appication(s) for this modue ID. IP Address: The system dispays the IP address of the server if previousy popuated on the Modue/Apps Detais screen. Seria number: The system dispays the seria number for this modue ID. Two seria numbers appear if this modue has dupex servers. Reease: The system dispays the reease of the appication(s) for this modue ID. How to use this screen This section contains instructions on how to use the Assign Patforms, Reeases, and Add Modues screen. High-eve steps to assign an operation to a modue If RFA automaticay assigned a the operations to the appropriate modues, you cannot make any seections in the Existing Modue Detais section. Cick Finish to save the information and continue the transaction. Use the foowing high-eve steps to assign an operation to a modue: 1. In the SAP Order Detais section, seect the radio button next to the SAP segment number for the operation you want to assign. 2. In the Existing Modue Detais section, cick the check box for the modue that you want to associate with the operation. The sequence number aong with the new patform type and/ or the new reease, appears in red in the modue box. 3. If the quantity remaining for the operation is zero and there are additiona operations on the order, seect another operation by cicking the radio button next to the segment number for that operation. If a the operations have been assigned, and the quantity for the operations is zero, a Finish button appears at the bottom of the screen. Cick Finish to submit the data and continue the transaction. For information on an add modue operation see The Add Modues box on page 271. Issue 5.0 September

274 RFA enhancements Patform Migrations For product famiies with ony one modue, RFA automaticay seects the modue for the patform migration. When RFA automaticay seects the modue, the Assign Patforms, Reeases, and Add Modues screen is dispay-ony. You can view and accept the seection by cicking Finish at the bottom of the screen. For muti-modue systems, RFA attempts to determine which modue to appy the patform migration to. If RFA cannot determine the modue to appy the migration to, you can seect the modue from a ist of existing modues. When a migration operation is seected, the system dispays a New Patform Type check box in each modue of the Existing Modue Detais section that meets the foowing criteria: The patform type for the existing modue is different than the patform type for the seected SAP order segment. The New Patform Type fied in the Existing Modue Detais section has not aready been popuated by a SAP segment number for a different patform migration operation. 274 Avaya Remote Feature Activation (RFA) User Guide

275 The Assign Patforms, Reeases, and Add Modues screen Figure 122: The Assign Patform, Reeases, and Add modues for a migration When you check the New Patform Type check box for a modue in the Existing Modue Detais section the foowing events occur: A red New Patform Type fied appears with the Patform Type of the seected operation. A red SAP Order Detais sequence number appears with the sequence number of the seected operation. The Quantity Remaining fied in the SAP Order Detais section is decremented by one for the seected operation. A patform migration operation does not incude the foowing changes: A modue type such as LSP, ESS, SRP, or WSP A sub-modue to a main modue A main modue to a sub-modue Issue 5.0 September

276 RFA enhancements Upgrades RFA considers an upgrade to be a change in the reease version of appications for modues. An upgrade can be partia or fu. In a partia upgrade ony some of the modues within a system are upgraded. In a fu upgrade a modues within a system are upgraded. For a partia upgrade where there is ony one possibe seection, RFA automaticay assigns the operation to the modue. For operations where there is more than one possibe seection, RFA aows the user to seect the modue or appications that wi be upgraded using the Assign Patforms, Reeases, and Add Modues screen. For a fu upgrade, RFA tries to determine the modues to upgrade and the reeases to use for the upgrade. If RFA cannot make an absoute determination of the modues to upgrade based on the SAP order, RFA aows the user to seect the modue and appications for the upgrade using the Assign Patforms, Reeases, and Add Modues screen. RFA vaidates the upgrade based on the foowing rues: The Communication Manager reease for an LSP must be equa to or greater than the main modue. The Communication Manager reease for an ESS server must be equa to or greater than the main modue. When a upgrade operation is seected from the SAP Order Detais section, the system dispays a New Reease check box in each of the modues in the Existing Order Detais section that meets the foowing criteria: The Modue Type fied for the operation in the SAP Order Detais section contains the same modue type as the modue in the Existing Modue Detais section. The Reease fied for the modue in the Existing Modue Detais section is different than the reease in the SAP Order Detais section for the operation. The New Reease fied for the modue has not aready been popuated by a different operation. 276 Avaya Remote Feature Activation (RFA) User Guide

277 The Assign Patforms, Reeases, and Add Modues screen Figure 123: The Assign Patforms, Reeases, and Add Modues for upgrades The foowing events occur when you mark a check in the New Reease check box: A red New Reease fied appears dispaying the reease from the seected operation. A red sequence number appears. The Quantity Remaining fied in the SAP Order Detais section is decremented for the seected operation. Issue 5.0 September

278 RFA enhancements Materia codes with mutipe operations An SAP order can contain a materia code with just one operation such as adding a modue, or a combination of operations such as a patform migration and an upgrade. When this happens you wi see the combination of operations within the Operation fied of the Assign Patforms, Reeases, and Add Modues screen. If the operation contains the wording and/or you may seect to perform either operation. You may continue to perform one or both of the operations unti the Quantity Remaining fied is equa to zero. If the operation contains the word and than you must seect both of the isted operations on the same modue. If there is an add operation in a materia code with mutipe operations, the Add Modue box appears under the SAP Order Detais section. When the Add Modues box appears, a zero appears inside the box. To add a modue, type the number of modues you want to add to the system in the box and hit the enter key on your keyboard. In the SAP Order Detais section, the Quantity Remaining fied for the seected operation decrements by the number that you entered in the Add Modues box. When the Quantity Remaining fied is zero for a the operations in the SAP Order Detais section, a Finish button appears on the bottom of the screen. Cick Finish to enter the data and continue with the transaction. RFA Reease 9.0 Exampes This section contains exampes of SAP orders and demonstrates how to use the Assign Patforms, Reeases, and Add Modues screen. Exampe one: Migrating and upgrading the main server and adding a modue In exampe one, an SAP order was paced that contained the foowing operations: A patform migration of a main server from DEFINITY Server R to an S8700 Server. An addition of an S8300 Server in a G700 Media Gateway Loca Survivabe Server (LSP). The foowing steps were performed for exampe one: 1. On the RFA main menu, Additions, Upgrades, and Migrations was seected foowed by Additions, Upgrades R10+, and Migrations R The SAP order number and the SID were submitted. 278 Avaya Remote Feature Activation (RFA) User Guide

279 The Assign Patforms, Reeases, and Add Modues screen 3. After submitting the SID, the Assign Patforms, Reeases, and Add Modues screen appears (Figure 124). In the SAP Order Detais section, segment 1 dispays for the patform migration and upgrade operation and segment 2 dispays for the add modue operation. Both segment 1 and segment 2 have been automaticay assigned by RFA. When RFA automaticay assigns the operations to modues: The words No Action Necessary by User appears in the Instructions coumn for the operation. The words RFA has automaticay assigned these vaues appears underined in bue within the modue box. The abiity to seect a modue for the operation is not avaiabe. If RFA automaticay seected a the operations on the order, the Seect coumn does not appear. If the SAP order contains mutipe operations where RFA was abe to seect some operations but not others, the Seect coumn on the RFA assigned operations wi be bank without a radio button. Figure 124: Exampe 1 SAP Order Detais section 4. Since RFA automaticay assigned the modue to the operation and the quantity remaining for both the operations is zero, the Finish button appears on the bottom of the screen. After cicking Finish a warning message appears (Figure 125). Issue 5.0 September

280 RFA enhancements Figure 125: Exampe 1 warning message after finish 5. After cicking OK, a status message appears at the top of the screen with green ights (Figure 126). Figure 126: Exampe 1 processing message A status message appears after the processing is compete. Exampe two: Upgrading and/or adding a modue In exampe two, an SAP order was paced to upgrade and/or add an S8300 Server in a G700 Media Gateway LSP. The SAP order was created to provide the customer with one new modue and upgrades for four existing modues. A modues are LSPs made up of S8300 Servers in G700 Media Modues. The foowing steps were performed for exampe two: 1. On the RFA main menu, Additions, Upgrades, and Migrations was seected foowed by Additions, Upgrades R10+, and Migrations R The SAP order number and the SID were submitted. 3. After the SID was submitted, the Assign Patforms, Reeases, and Add Modues screen appeared (Figure 127). In the SAP Order Detais section there is ony one operation and therefore ony one segment. The instructions in the Instruction coumn te the user to add modues and/or seect a New Reease for an appication. The modue type is LSP with a patform type of an S8300 Server in a G700 Media Gateway. The upgrade reease that was ordered is Reease 13. The quantity for this combination operation is five. 280 Avaya Remote Feature Activation (RFA) User Guide

281 The Assign Patforms, Reeases, and Add Modues screen Figure 127: Exampe 2 SAP Order Detais section 4. Because this order contains a combination operation with an add modue operation, the Add Modue box appears in the Assign Patforms, Reeases, and Add Modues screen (Figure 128). Figure 128: Exampe 2 Add Modues box The amount entered in the Add Modues box is decremented from the Quantity Remaining coumn in the SAP Order Detais section. For exampe two, a quantity of one is entered in the Add Modues box. The Quantity Remaining coumn changes from five to four. The remaining quantity of four wi be used for upgrades on existing modues. 5. The Existing Modue Detais section is used to seect the modues for the upgrade operation (Figure 129). The New Reease check box appears in each modue that is not running the same reease as the operation (R013). When a check box is checked for a modue, the new reease version and the segment number appears in red within the modue box whie the Quantity Remaining coumn in the SAP Order Detais section is decremented. For exampe two, we must seect four modues to compete the assignments. Issue 5.0 September

282 RFA enhancements Figure 129: Exampe 2 Existing Modue Detais section It is possibe that you may have to go to another screen on the Existing Modues Detais section to find the modue you want to seect. To go to another page, cick the number range in the bottom eft side of the screen. The RFA system automaticay saves any changes you have made on the first page before dispaying the next page. 6. When a four modues are seected and the Quantity Remaining fied in the SAP Order Detais section is zero, the Finish button appears on the bottom of the screen. After cicking Finish a warning message appears (Figure 130). Figure 130: Exampe 2 warning message after finish 7. After cicking OK, a status message appears at the top of the screen with green ights (Figure 131). Figure 131: Exampe 2 processing message 282 Avaya Remote Feature Activation (RFA) User Guide

283 The Assign Patforms, Reeases, and Add Modues screen Exampe three: Migrating and upgrading modues In exampe three, an SAP order was paced that contained the foowing operations: A patform migration on the main server from a S8500 Server to an S8700 Server. Upgrades on four existing modues. Migrations on two existing modues. The SAP order was created to provide the customer with a patform migration on the main server, upgrades of four sub-modues, and patform migrations of two sub-modues. A existing sub-modues are LSPs made up of S8300 Servers in G350 Media Modues. The foowing steps were performed for exampe two: 1. On the RFA main menu, Additions, Upgrades, and Migrations was seected foowed by Additions, Upgrades R10+, and Migrations R The SAP order number and the SID were submitted. After the SID was submitted, the Assign Patforms, Reeases, and Add Modues screen appeared (Figure 132). The three operations contained in the SAP order are shown in the SAP Order Detais section. The main server patform migration was automaticay seected by RFA. When RFA automaticay assigns the operations to modues: The words No Action Necessary by User appears in the Instructions coumn for the operation. The words RFA has automaticay assigned these vaues appears underined in bue within the modue box. The abiity to seect a modue for the operation is not avaiabe. If RFA automaticay seected a the operations on the order, the Seect coumn does not appear. If there are a combination of operations where RFA was abe to seect some operations but not others, the Seect coumn on the RFA assigned operations wi be bank without a radio button. Figure 132: Exampe 3 SAP Order Detais section Issue 5.0 September

284 RFA enhancements 3. The first radio button in the Seect coumn of the first SAP order segment requiring an assignment is seected by defaut by RFA. In exampe three, the first SAP order segment that needs modue assignment is segment 2, upgrade. When the radio button is seected for the upgrade operation a New Reease check box appears in the Modue Detais section for every modue running a software reease that is different than the reease on the SAP order. When you cick on the check box the new reease of software that the modue is upgrading to and the SAP segment number appears in red in the modue box. A tota of four upgrades were seected. A zero dispays in the Quantity Remaining coumn for segment two. 4. The radio button was seected for segment three, patform migrations. When the radio button is seected for the patform migration operation, a New Patform check box appears in the Modue Detais section for every modue that is on a different patform. A tota of two modues were seected for a patform migration. A zero dispays in the Quantity Remaining coumn for segment three. At this point we are finished seecting the modues for the operations on the SAP order. The Quantity Remaining fied for both segment two and segment three dispays a zero. The Finish button appears at the bottom of the screen. The data is submitted by cicking the Finish button. Once the data is submitted you cannot make any changes to the Assign Patforms, Reeases, and Add Modues screen. For hep on what to do if you made a mistake on the Assign Patforms, Reeases, and Add Modues screen, refer to What do I do if I seected the wrong modue for an operation? on page 285. Hepfu hints When do I have to submit the data in the Assign Patforms, Reeases, and Additions screen? Cick on the Submit button to save the data anytime you eave the Assign Patforms, Reeases, and Additions screen by cicking on another tab, or anytime you eave the transaction. You do not have to submit the data every time you cick on a check box within a modue or anytime you cick on a ink to view additiona modues. 284 Avaya Remote Feature Activation (RFA) User Guide

285 Hepfu hints How do I know which modue to seect? There are a number of ways to identify a specific modue in RFA. You can identify a modue by the seria number, the modue description, and/or the modue ocation. The modue description and the modue ocation are optiona fieds in the Mod/Appication Detais screen. If this information is not popuated in the Mod/Appications Detais screen the modue description and modue ocation fieds in the Assign Patforms, Reeases, and Add Modues screen wi be bank. In this case you coud identify the modue by it s seria number. What do I do if I forgot to change the seria number on a patform migration? Not a patform migrations require a seria number change. If you performed a patform migration that does require a seria number change and you did not enter the new seria number before you compete the transaction, you must perform a Seria Number Swap-Out in RFA. What do I do if I appied the migration or upgrade to the wrong modue before the transaction was compete? If you cicked Finish on the Assign Order Items tab and reaized before the transaction is compete that you made a mistake, you can deete the transaction and start over again. What do I do if I seected the wrong modue for an operation? If you have not aready cicked the Finish button in the Assign Patforms, Reeases, and Add Modues screen, you can use the foowing steps to make a change to the seection of a modue: 1. A red sequence number associated with the operation appears in the modue box when you seected the modue for the operation. Find the sequence number in the modue box for the operation that you want to remove. 2. Look for the sequence number in the SAP Order Detais section. Cick the radio button next to the sequence number. Cicking the radio button activates the check boxes in the Existing Modues Detais section. 3. Remove the modue as a seection by unchecking the check box. If you have aready cicked the Finish button, you cannot make any changes to the Assign Patforms, Reeases, and Add Modues screen. If you have not competed the transaction, you can deete the transaction and start again. If you have competed the transaction, you must ca the RFA Hepdesk and ask for a revert back. Issue 5.0 September

286 RFA enhancements 286 Avaya Remote Feature Activation (RFA) User Guide

287 Gossary A Appication Name Authentication fie Authentication Fie System (AFS) F Feature Extraction Too (FET) Feature keyword Feature types FSO Identifies various appications that are associated with a system. In addition to the icense fie, Avaya servers that use an open operating system require an authentication fie. The authentication fie contains non-defaut passwords and Access Security Gateway (ASG) keys for the Avaya services ogins. When you create an RFA system record for an Avaya system reease 11 and ater, RFA automaticay creates an authentication fie. For the Branch Gateway product famiy, the Authentication Fie System (AFS) is used to generate and downoad an authentication fie. The AFS appication is used to generate authentication fies for the Branch Gateway product famiy. AFS is accessed from the RFA Information page. FET is a software appication used to capture customer options, current server configuration, and other data from: G3V4 through Reease 9.5 Avaya DEFINITY Servers (csi, si, r) DEFINITY ONE or IP600 FET produces a Switch Configuration fie that Remote Feature Activation (RFA) uses to create a icense fie. FET is integrated with RFA for servers running Reease 8.x through reease 9.x system software. RFA creates a icense fie based on the materia codes that appear in the SAP order. RFA maps between the SAP materia codes and the features and capacities in the icense fie. Whie the icense fie does not contain the materia codes themseves, it does contain the features and the capacities that wi be activated for the system. The features and capacities are represented by Feature Keywords. Feature Keywords are Engish text that uniquey identify which features and capacities to activate. For a compete isting of the Communication Manager Keywords see the RFA Information page at rfa.avaya.com. A feature fas into one of three categories, Type 1, Type II, or Type III. A Type I feature has an on and an off setting. A Type II feature has a vaue or capacity. A Type III Feature has a product ID, a reease, and a capacity setting. During an RFA transaction, a feature types on an SAP order can be found in the Features tab. Fied Service Organization Issue 5.0 September

288 Group Authorization Number (GAI) G Group Authorization Number (GAI) H Host ID L License fie License Instaation Too (LIT) M Migration Modue Identification Number (MID) R RFA S Seria numbers Avaya assigns a unique GAI number to each BusinessPartner. The GUI aows access to transactions and system records. At east one GAI must be incuded in the system information when a BusinessPartner is responsibe for creating, modifying, or deivering a icense fie. For a RFA supported products that use Host IDs (except Moduar Messaging), a Host ID is the Media Access Contro Address (MAC) of the first ethernet port (eth0) on the server or License Server. For Moduar Messaging the Host ID is the voice mai domain identifier. The Host ID may be apha/numeric and up to 50 characters in ength. An RFA icense fie is an encrypted fie that is used to activate software features incuding capacities, reease, and offer categories. LIT instas an RFA icense fie on the foowing Avaya systems running Reease 10 or higher software: Avaya DEFINITY Server csi with the TN2402 Avaya DEFINITY Server si with the TN2404 Avaya DEFINITY Server r with the Un332C A migration is performed when the patform hardware is changed out for another type of patform hardware. For exampe, if you are changing out an S8500 Server to an S8700 Server, you are performing a migration. A separate icense fie is required for every Avaya server. RFA refers to each server as a modue. Each modue is given a modue identification number (MID). The main server is aways modue 1. Additiona modues, such as a Loca Survivabe Processor (LSP) or an Enterprise Survivabe Server (ESS) are assigned modue numbers greater than 1. Remote Feature Activation: The web-based appication used to generate icense and authentication fies. The hardware seria number is used to create a vaid icense fie. The hardware seria number and the seria number within the icense fie must match. 288 Avaya Remote Feature Activation (RFA) User Guide

289 Update Shared Bade Server Singe Sign On (SSO) Systems, Appications and Products (SAP) System Identification Number(SID) System Record T Transaction Record Type 2 feature upgrade Type 3 feature upgrade U Update The Shared Bade Server (SBS3000) system uses virtua machines pus mutipe bades to aow mutipe instances of Communication Manager on one SBS3000 system. RFA contains a system record for each instance of Communication Manager running on an SBS3000 system. Each system record is popuated based on the specific instance of Communication Manger. RFA is aso used to generate additiona icenses over the ife of the system to support maintenance activities such as an IPSI or gateway repacement. An Avaya corporate mechanism that requires a singe ogin to aow users access to certain web sites. Avaya s ordering system for products and services. Each icensed system is assigned a unique number caed a SID. The SID can be used to ocated the RFA system record. After a transaction is competed, a system record is created in the RFA database. The system record contains information pertaining to the customer and the Avaya system. A system record can never be deeted. Changes or additions to the system record are refected in a change in the version number for the system record. A transaction record is created when a user seects an option from the RFA Main Menu. The transaction record contains a of the information added or modified during the session. Each transaction is assigned a unique number. If you do not compete the transaction, you can enter the transaction number and find the transaction record. You can deete a transaction record at any time. Upgrades can take pace at a feature eve for SAP orders with a materia code of VALUE_STA and a setting of PER USER. Upgrades to type II features can contain a or part of the stations that are on the RFA system record. An update is part of a maintenance soution for a customer that is under warranty or has a Avaya maintenance contract. An upgrade is a reease of software with new or enhanced capabiities and is purchased by a customer. Issue 5.0 September

290 Upgrade Upgrade W Warning messages RFA considers an upgrade to be a change in the reease version of appications for a modue. An upgrade can be partia or fu. In a partia upgrade ony some of the modues within a system are upgraded. In a fu upgrade, a modues within a system are upgraded. For a partia upgrade where there is ony one possibe seection, RFA automaticay assigns the operation to the modue. For operations where there is more than one possibe seection, RFA aows the user to seect the modue or appications that wi be upgraded using the Assign Patforms, Reeases, and Add Modues screen. For a fu upgrade, RFA tries to determine the modues to upgrade and the reeases to use for the upgrade. If RFA cannot make an absoute determination of the modues to upgrade based on the SAP order, RFA aows the user to seect the modue and appications for the upgrade using the Assign Patforms, Reeases, and Add Modues screen. RFA vaidates the upgrade based on the foowing rues: The Communication Manager reease for an LSP must be equa to or greater than the main modue. The Communication Manager reease for an ESS server must be equa to or greater than the main modue. There are two types of warning messages in RFA, genera and detaied. Genera warning messages provide information about a condition that occurred when the order was appied to the RFA system record. Detaied warning messages provide exact information on a warning condition and describe how RFA processed the order after the condition occurred. 290 Avaya Remote Feature Activation (RFA) User Guide

291 Index Index A About Remote Feature Activation (RFA) About this book Training and approva Add Modues box Additions Procedure Detaied steps High-eve steps Additions and upgrades AE Appication Design Environment Diaog Designer components Appication Enabement Services Appications Audix Ca Center Appications Enabement Services RFA-icensed appications Appications under the Communication Manager product famiy Appy Changes to A Modues Appy Changes to this Modue Ony ASD Communication Manager Configurator Assign Patforms, Reeases, and Add Modues migrations Audix Authentication fie Avaya IQ Avaya Proactive Contact B Branch Gateways Repacing a Branch Gateway C Ca Center , 186 Materia codes CCR CNA Communication Manager Appications Ca Center Authentication fie Creating a icense for WSP, LSP, or SRP ESS server FET License Fie seria number swap-out License-Error mode LIT LSP No-License mode SRP Systems requiring a icense fie When is a icense fie required for Communication Manager? WSP Communications Process Manager Computer requirements Contact Center E-mai icense request Host ID Interaction Center (IC) WebLM Converged Network Anayzer (CNA) Customer Interaction Express D Deivering a fie Before you start Procedure Detaied steps High-eve steps Deivering a Fie overview Deivery options Detaied Feature Information , 252 E Enterprise Network Management Consoe ESS server Exampes of assigning modues to operations Existing Modue Detais section , 271 F Feature Extraction Too Feature Keywords FET Find a transaction record Fu upgrade Issue 5.0 September

292 Index G G250 Finding the seria number G250 and G350 Activating Virtua Private Networking Activating VPN Post instaation verification Remotey controed by a server Remotey controed by a server with an LSP Remotey controed by a server with an LSP and VPN 237 With an S3800 and VPN With an S G250 and G350 seria number G250 Media Gateway Configurations G G350 Media Gateway Configurations Standaone G350 with VPN Standaone G350 without VPN GAI Group Authorization Identification Group Authorization Identification (GAI) H Hep for RFA Hepfu hints Host ID Host IDs Unified Communication Center How to use the Assign Patforms, Reeases, and Add Modues screen I Integrated Management Additiona VMM endpoint and gateway capacity. 243 Appication information Converged Network Anayzer (CNA) New instaations of VMM VoIP Monitoring Manager (VMM) Interactive Response J Job Aid for Type 3 Feature Upgrade Warning Messages37, 219, 255 L License fie seria number swap-out Procedure Detaied steps High-eve steps License Fies How does a icense fie work? When is a icense fie not required? When is a icense fie required? License Instaation Too License-Error LIT LSP M Materia Codes , 287 Materia codes with mutipe operations MID Modue N New Insta Before you start Procedures Detaied steps High-eve steps NMC No-License O one-x Mobie one-x Porta On-ine hep Operations P Partia upgrade Patform migration Procedures for a New Insta Q Quaified modues R Registration for Avaya Associates Registration for Avaya BusinessPartners Reease 9.0 terminoogy Reease 9.6 Type 3 Feature enhancements RFA 10.8 enhancements RFA Appication Main Menu 292 Avaya Remote Feature Activation (RFA) User Guide

293 Index Center Left side My RFA Authorization Information View My Fie Deivery Status View My Upoaded switch config fie status.. 58 Work With My Pending System Records Right side Change Product Famiy Exit RFA Search/View Menu RFA Reease 9.0 exampes S S8300 Server Acting as an LSP Acting as an LSP with VPN Standaone G250 and G350 with an S Standaone G250 or G350 with an S8300 and a VPN237 SAP order detai sequence number SAP Order Detais section , 269 SBS , 289 Sequence number Seria numbers Communication Manager Avaya DEFINITY Servers Avaya S8100 Server Avaya S8300 Server Avaya S8500 and S8700 series servers DEFINITY ONE and IP Security Gateway Shared Bade Server Shared features Softcients CCS Peer-to-Peer SIP Softphone SRP sub-modues , 265 Support Updates and Upgrades Procedure Detaied steps Support Upgrades Procedure High -eve steps System record Procedure Compete a pending system record Finding a system record with the SID Finding a system record without the SID Pending system records System records , 177 Introduction System records definition T The Assign Patforms, Reeases, and Add Modues screen 266 How the Assign Patforms, Reeases, and Add Modues screen works The Add Modues box The Existing Modue Detais section The SAP Order Detais section , 269 Training Transaction records Deete a transaction record Find and continue work on a transaction record. 171 Introduction Procedure Using the Search/View menu Using the RFA Appication Main Menu Transactions What is a transaction? Transactions and system records What is a System Identification Number (SID)?.. 30 What is a system record? What is a transaction? Type 3 Feature Type II Per User upgrades Ca Center Type III Feature Information derived from the SAP Order 202, 252 U UCC What is a UCC License Server? Understanding Host IDs Understanding Type III Feature Information.. 202, 252 Update and upgrade differences Updates and Upgrades Procedure Updates and upgrades from Pre Reease 10 Before you start Using the Assign Patforms, Reeases, and Add Modues screen for migrations V View My Fie Deivery Status Procedure Detaied steps High-eve steps Viewing and changing your RFA authorization information 167 Procedure Detaied steps Virtua Private Networking VMM Issue 5.0 September

294 Index Additiona VMM endpoint and gateway capacity. 243 New instaations of VMM Voice Porta Voice Sef Service Host ID VoIP Monitoring Manager (VMM) W Warning Message tabe , 255 Warning messages , 36, 253 WebLM Working with system records Working with transaction records Introduction WSP Avaya Remote Feature Activation (RFA) User Guide