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