AVAYA CONFIGURATION AND ORCHESTRATION MANAGER Release Release Notes. January 28 th, 2015 Issue 2.0 CID:

Transcription

1 AVAYA CONFIGURATION AND ORCHESTRATION MANAGER Release Release Ntes January 28 th, 2015 Issue 2.0 CID:

2 2015 Avaya Inc. All Rights Reserved. Ntice While reasnable effrts have been made t ensure that the infrmatin in this dcument is cmplete and accurate at the time f printing, Avaya assumes n liability fr any errrs. Avaya reserves the right t make changes and crrectins t the infrmatin in this dcument withut the bligatin t ntify any persn r rganizatin f such changes. Dcumentatin disclaimer Dcumentatin means infrmatin published by Avaya in varying mediums which may include prduct infrmatin, perating instructins and perfrmance specificatins that Avaya generally makes available t users f its prducts. Dcumentatin des nt include marketing materials. Avaya shall nt be respnsible fr any mdificatins, additins, r deletins t the riginal published versin f dcumentatin unless such mdificatins, additins, r deletins were perfrmed by Avaya. End User agrees t indemnify and hld harmless Avaya, Avaya's agents, servants and emplyees against all claims, lawsuits, demands and judgments arising ut f, r in cnnectin with, subsequent mdificatins, additins r deletins t this dcumentatin, t the extent made by End User. Link disclaimer Avaya is nt respnsible fr the cntents r reliability f any linked websites referenced within this site r dcumentatin prvided by Avaya. Avaya is nt respnsible fr the accuracy f any infrmatin, statement r cntent prvided n these sites and des nt necessarily endrse the prducts, services, r infrmatin described r ffered within them. Avaya des nt guarantee that these links will wrk all the time and has n cntrl ver the availability f the linked pages. Warranty Avaya prvides a limited warranty n its hardware and Sftware ( Prduct(s) ). Refer t yur sales agreement t establish the terms f the limited warranty. In additin, Avaya s standard warranty language, as well as infrmatin regarding supprt fr this Prduct while under warranty is available t Avaya custmers and ther parties thrugh the Avaya Supprt website: Please nte that if yu acquired the Prduct(s) frm an authrized Avaya reseller utside f the United States and Canada, the warranty is prvided t yu by said Avaya reseller and nt by Avaya. Sftware means cmputer prgrams in bject cde, prvided by Avaya r an Avaya Channel Partner, whether as standalne prducts r pre-installed n hardware prducts, and any upgrades, updates, bug fixes, r mdified versins. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Avaya grants yu a license within the scpe f the license types described belw, with the exceptin f Heritage Nrtel Sftware, fr which the scpe f the license is detailed belw. Where the rder dcumentatin des nt expressly identify a license type, the applicable license will be a Designated System License. The applicable number f licenses and units f capacity fr which the license is granted will be ne (1), unless a different number f licenses r units f capacity is specified in the dcumentatin r ther materials available t yu. Designated Prcessr means a single stand-alne cmputing device. Server means a Designated Prcessr that hsts a sftware applicatin t be accessed by multiple users. License types Designated System(s) License (DS). End User may install and use each cpy f the Sftware nly n a number f Designated Prcessrs up t the number indicated in the rder. Avaya may require the Designated Prcessr(s) t be identified in the rder by type, serial number, feature key, lcatin r ther specific designatin, r t be prvided by End User t Avaya thrugh electrnic means established by Avaya specifically fr this purpse. Cncurrent User License (CU). End User may install and use the Sftware n multiple Designated Prcessrs r ne r mre Servers, s lng as nly the licensed number f Units are accessing and using the Sftware at any given time. A Unit means the unit n which Avaya, at its sle discretin, bases the pricing f its licenses and can be, withut limitatin, an agent, prt r user, an r vice mail accunt in the name f a persn r crprate functin (e.g., webmaster r helpdesk), r a directry entry in the administrative database utilized by the Sftware that permits ne user t interface with the Sftware. Units may be linked t a specific, identified Server. Database License (DL). End User may install and use each cpy f the Sftware n ne Server r n multiple Servers prvided that each f the Servers n which the Sftware is installed cmmunicates with n mre than a single instance f the same database. CPU License (CP). End User may install and use each cpy f the Sftware n a number f Servers up t the number indicated in the rder prvided that the perfrmance capacity f the Server(s) des nt exceed the perfrmance capacity specified fr the Sftware. End User may nt re-install r perate the Sftware n Server(s) with a larger perfrmance capacity withut Avaya s prir cnsent and payment f an upgrade fee. Named User License (NU). Yu may: (i) install and use the Sftware n a single Designated Prcessr r Server per authrized Named User (defined belw); r (ii) install and use the Sftware n a Server s lng as nly authrized Named Users access and use the Sftware. Named User, means a user r device that has been expressly authrized by Avaya t access and use the Sftware. At Avaya s sle discretin, a Named User may be, withut limitatin, designated by name, crprate functin (e.g., webmaster r helpdesk), an r vice mail accunt in the name f a persn r crprate functin, r a directry entry in the administrative database utilized by the Sftware that permits ne user t interface with the Sftware. Shrinkwrap License (SR). Yu may install and use the Sftware in accrdance with the terms and cnditins f the applicable license agreements, such as shrinkwrap r clickthrugh license accmpanying r applicable t the Sftware ( Shrinkwrap License ). Heritage Nrtel Sftware Heritage Nrtel Sftware means the sftware that was acquired by Avaya as part f its purchase f the Nrtel Enterprise Slutins Business in December The Heritage Nrtel Sftware currently available fr license frm Avaya is the sftware cntained within the list f Heritage Nrtel Prducts lcated at LicenseInf under the link Heritage Nrtel Prducts. Fr Heritage Nrtel Sftware, Avaya grants Custmer a license t use Heritage Nrtel Sftware prvided hereunder slely t the extent f the authrized activatin r authrized usage level, slely fr the purpse specified in the Dcumentatin, and slely as embedded in, fr executin n, r (in the event the applicable Dcumentatin permits

3 installatin n nn-avaya equipment) fr cmmunicatin with Avaya equipment. Charges fr Heritage Nrtel Sftware may be based n extent f activatin r use authrized as specified in an rder r invice. Cpyright Except where expressly stated therwise, n use shuld be made f materials n this site, the Dcumentatin, Sftware, r hardware prvided by Avaya. All cntent n this site, the dcumentatin and the Prduct prvided by Avaya including the selectin, arrangement and design f the cntent is wned either by Avaya r its licensrs and is prtected by cpyright and ther intellectual prperty laws including the sui generis rights relating t the prtectin f databases. Yu may nt mdify, cpy, reprduce, republish, uplad, pst, transmit r distribute in any way any cntent, in whle r in part, including any cde and sftware unless expressly authrized by Avaya. Unauthrized reprductin, transmissin, disseminatin, strage, and r use withut the express written cnsent f Avaya can be a criminal, as well as a civil ffense under the applicable law. Virtualizatin Each virtual appliance has its wn rdering cde. Nte that each instance f a virtual appliance must be rdered separately. If the enduser custmer r Business Partner wants t install tw f the same type f virtual appliances, then tw virtual appliances f that type must be rdered. Third Party Cmpnents Third Party Cmpnents mean certain sftware prgrams r prtins theref included in the Sftware that may cntain sftware (including pen surce sftware) distributed under third party agreements ( Third Party Cmpnents ), which cntain terms regarding the rights t use certain prtins f the Sftware ( Third Party Terms ). Infrmatin regarding distributed Linux OS surce cde (fr thse Prducts that have distributed Linux OS surce cde) and identifying the cpyright hlders f the Third Party Cmpnents and the Third Party Terms that apply is available in the Dcumentatin r n Avaya s website at: supprt.avaya.cm/cpyright. Yu agree t the Third Party Terms fr any such Third Party Cmpnents. Preventing Tll Fraud Tll Fraud is the unauthrized use f yur telecmmunicatins system by an unauthrized party (fr example, a persn wh is nt a crprate emplyee, agent, subcntractr, r is nt wrking n yur cmpany's behalf). Be aware that there can be a risk f Tll Fraud assciated with yur system and that, if Tll Fraud ccurs, it can result in substantial additinal charges fr yur telecmmunicatins services. Avaya Tll Fraud interventin If yu suspect that yu are being victimized by Tll Fraud and yu need technical assistance r supprt, call Technical Service Center Tll Fraud Interventin Htline at fr the United States and Canada. Fr additinal supprt telephne numbers, see the Avaya Supprt website: Suspected security vulnerabilities with Avaya prducts shuld be reprted t Avaya by sending mail t: securityalerts@avaya.cm. Trademarks The trademarks, lgs and service marks ( Marks ) displayed in this site, the Dcumentatin and Prduct(s) prvided by Avaya are the registered r unregistered Marks f Avaya, its affiliates, r ther third parties. Users are nt permitted t use such Marks withut prir written cnsent frm Avaya r such third party which may wn the Mark. Nthing cntained in this site, the Dcumentatin and Prduct(s) shuld be cnstrued as granting, by implicatin, estppel, r therwise, any license r right in and t the Marks withut the express written permissin f Avaya r the applicable third party. Avaya is a registered trademark f Avaya Inc. All nn-avaya trademarks are the prperty f their respective wners, and Linux is a registered trademark f Linus Trvalds.

4 Cntents 1. Summary Imprtant Ntes befre Installing this Release What is new in this release New in this release Issues Reslved in this release Server and Client Requirements Server Requirements Client Requirements Licensing Pre-requisites fr the COM installatin/upgradatin Upgrading COM 3.1 using COM installer Upgrading COM 3.1 OVA using COM installer Supprted Manual Upgrade Scenaris in COM Manual Data migratin frm existing COM 3.0.x installatin Limitatins and Knwn Issues Limitatins Device Issues Knwn Issues Miscellaneus Infrmatin General Inf Recmmendatins fr Imprved Netwrk Discvery Prcedure t frce management IP: Wrkarund fr script running slwly - brwser issue General Recmmendatins List f COM dcuments Appendix: Device Supprt (cmprehensive list) Avaya Inc Issue: 1.0 (28 th January 2015) Page 4 f 22

5 1. Summary COM Release Date: January 28 th, Purpse: The Cnfiguratin & Orchestratin Manager (COM) Release Ntes prvide the fllwing infrmatin: General release infrmatin including Changes/Bug fixes in COM Supprted perating systems, hardware requirements and brwser clients Knwn issues and limitatins 2. Imprtant Ntes befre Installing this Release COM is a minr release which fllws the previus release COM 3.1 based n Avaya Aura System Manager versin 6.3. This release addresses several custmer issues and new device supprt. Imprtant! Only Micrsft Windws Server 2008 R2 (64-bit standard and enterprise editins) SP1 and Red Hat Enterprise Linux (RHEL) v5.6 and v5.7 (bth 64 bit) are supprted. Refer t sectin 4 fr details n the hardware requirements fr the server. COM can be installed nly as a Primary SMGR-CS server. Installer supprts fresh installatin f COM 3.1.1, as well as upgrade frm COM 3.0.1, COM and COM 3.1. Manual data migratin is supprted frm existing installatins f COM and COM COM des nt supprt c-residency with VPFM. Virtualizatin Prvisining Service (VPS) versin v1.1 cannt be installed afresh n COM The existing system(s) where COM R3.1 and VPS R1.1 are installed, COM 3.1 nce upgraded t COM R3.1.1, user will be able t launch VPS and perfrm all the actin. Thugh, a warning will be displayed at the time f VPS launch that the VPS R1.1 is nt cmpatible with COM R Older versins f VPS are nt supprted n COM COM 3.1 license will wrk fr COM Upgrade r migratin frm COM 3.0.x t wuld require new license. COM 3.1 OVA upgrade t COM can be dne by running COM installer. General Instructins: Please read this Release Ntes cmpletely befre installing COM The Linux bin file needs t have apprpriate permissins befre installing. Use the cmmand: chmd 777 <filename> befre executing the Linux installer Avaya Inc Issue: 1.0 (28 th January 2015) Page 5 f 22

6 3. What is new in this release 3.1. New in this release Device supprt Full Supprt fr ERS 4800 v5.8 ERS 5500/5600 v6.3.4 and v6.6.1 VSP 7000 v10.3.1, v10.3.2, and v VSP 4000 v4.0 (New Mdel VSP4450 GSX-PWR+), v (New Mdel VSP4450 GTX- HT-PWR+) and v (New Mdel VSP-4450GSX-PWR+) VSP 8200 v VSP 9000 v ERS 8000 v7.2.13, v x, and v Partial (Discvery and EDM Plugin) Supprt fr VSP 8200 v4.1 VSP 4000 v4.1 Enhancements BCM Cnfiguratin and Backup Restre Enable Diff feature will nw be part f base license Avaya Inc Issue: 1.0 (28 th January 2015) Page 6 f 22

7 3.2. Issues Reslved in this release Fllwing bugs have been fixed in COM release WI id Wi Wi Descriptin COM 3.0 Trials: Device Save Cnfiguratin Tl shuld have "Device Name" clumn COM ibdata1 MySQL database file grwing t large Wi COM BCM backup changes the bt mde n a 5520 Wi Wi Wi Wi Wi Wi Wi Wi WI Wi wi wi wi wi * wi wi wi wi wi wi COM/BCM3.0.2-scheduler displays n tasks COM / Inventry Manager / n GBIC tab inf prvided if 8600 is in ACLI mde COM Cannt pen SSH cnnectin using CLI Manager COM Imprve the "EDM plugin versin mismatch" message display rule BCM Scheduler gets blcked in certain circumstances COM 3.1 install fails CCHMC: COM Optimizatins fr Device invent COM admin user cannt lgin back t the system after screen lcker gets activated COM OVA file dwnlad gets truncated COM Belden Hirschman devices nt discvered after upgrade frm COM COM functin des nt wrk when COM 3.1 installed frm OVA package COM Base Unit card missing when displaying Prt Status fr ERS4524GT-PWR stack COM 3.0.2/3.1 EDM ERS 8800 with plugin des nt display full arp table COM / BCM - "enable diff" feature part f base license COM3.0 - CLI*manager des nt wrk n COM 3.0 fr telnet r SSH cnnectins EDM plugin causes high cpu utilizatin BCM3.0.1-errr when pening applicatin COM 3.1 unable t generate CSR request Inventry Manager errr/philadelphia airprt COM 3.0.2/3.1 BCM restre desn't restre the entire vlan cnfig 2015 Avaya Inc Issue: 1.0 (28 th January 2015) Page 7 f 22

8 4. Server and Client Requirements 4.1. Server Requirements The server requirements are same as COM 3.1 and hasn t changed Hardware: Fllwing hardware/vm cnfiguratin is recmmended fr COM primary server setup. HW Cmpnent Critical Minimum Recmmended CPU Quad-cre 2GHz Quad-cre 2GHz Quad-cre 2GHz Memry 4 GB 6 GB 8 GB Free Disk Space 60 GB 60 GB 80 GB Imprtant! Frm COM 3.1 nwards, the RAM requirement has gne up by 2 GB. Operating System: Operating system Micrsft Windws Linux 64-bit RHEL v5.6 and v5.7 Versin 64-bit Windws Server 2008 R2 (standard and enterprise editins) SP Avaya Inc Issue: 1.0 (28 th January 2015) Page 8 f 22

9 Applicatin memry: The heap memry requirement fr COM depends n the size f the netwrk that will be managed using COM. Netwrk Size Heap Memry Requirement fr COM (Recmmended) Small ( < 250 devices) Medium ( 250 t 750 devices) Large ( 750 t 1500 devices) 4 GB 6 GB 8 GB (Physical RAM n the m/c als needs t be increased accrdingly) The default heap size fr COM is set t 4GB. If as per the abve table, a higher heap size is required, please cntact Avaya Supprt team t have them make the required changes t COM setup Client Requirements Brwser Versin Internet Explrer (IE) Versins 8, 9 and 10 FireFx (FF) Versins 19, 20 and Licensing COM 3.1 license will wrk fr COM New license is required nly when upgrading/migrating frm COM and COM t COM Avaya Inc Issue: 1.0 (28 th January 2015) Page 9 f 22

10 6. Pre-requisites fr the COM installatin/upgradatin 1. It is recmmended t have the IP & FQDN entries in etc\drivers\hsts in windws and /etc/hsts in Linux. 2. Hstname (FQDN) in the hsts file and the Cmputer-Name must be same; else FQDN reslutin during mdule-registry fails. The file is hsts file and path is etc\drivers\hsts in windws and /etc/hsts in Linux. Cmputer-Name: On Windws: My Cmputer >> Prperties >> Full cmputer name On Linux: System >> Administratin >> Netwrk >> DNS >> Hst Name 3. It is recmmended t have the Dmain Prfile Windws Firewall ff since it may blck sme prts during installatin. 4. On Windws perating system, it is recmmended t have the Passwrd Plicy glbally disabled. 5. It is recmmended t have the time/clck n the VM within (+/-) 24 hurs f the actual time since CND service may nt cme up if the time is incrrect. 6. On RHEL perating system, It is recmmended t have the Firewall/SELinux Linux disabled since it may blck sme prts during installatin. 7. Upgrading COM 3.1 using COM installer 1. Dwnlad the COM installer frm the Avaya supprt site. Windws Installer fr COM is cm-installer windws.exe. Linux Installer fr COM 3.1 is cm-installer linux.bin. 2. Start COM installer and accept the license agreement. 3. Prceeding further will cntinue COM installatin. User is advised t g thrugh the installatin wizard. 4. A successful installatin message will be displayed t the user at the end f the installatin Avaya Inc Issue: 1.0 (28 th January 2015) Page 10 f 22

11 8. Upgrading COM 3.1 OVA using COM installer 1. Dwnlad the COM installer frm the Avaya supprt site. Windws Installer fr COM will be like cm-installer windws.exe. Linux Installer fr COM 3.1 is cminstaller linux.bin. 2. Start COM installer and accept the license agreement. 3. Prceeding further will cntinue COM installatin. User is advised t g thrugh the installatin wizard. 4. A successful installatin message will be displayed t the user at the end f the installatin Avaya Inc Issue: 1.0 (28 th January 2015) Page 11 f 22

12 9. Supprted Manual Upgrade Scenaris in COM The fllwing table shws hw existing COM installatins can be mved t COM Current installatin Upgrade Using Installer Manual Data Migratin Prcedure fr Migratin COM 3.1 Running n Windws server 2008 R2 SP1 (standard/enterprise) OS COM 3.1 Running n 64- bit RHEL (any supprted flavr) Yes, this can be upgraded NA NA Yes, this can be upgraded NA Na COM and COM Running n 32-bit Windws OS (any supprted flavr) COM and COM Running n 32-bit RHEL (any supprted flavr) N, this cannt be upgraded N, this cannt be upgraded Yes, COM data needs t be migrated Yes, COM data needs t be migrated See the manual migratin sectin fr windws See the manual migratin sectin fr RHEL COM and COM Running n Windws server 2008 R2 SP1(standard/enterprise) OS COM and COM Running n 64-bit RHEL v5.6/5.7 COM and COM Running n 64-bit Windws ther than Windws server 2008 R2 SP1(standard/enterprise editin) COM and COM Running n 64-bit RHEL ther than RHEL v5.6/5.7 COM 2.3[.x] Yes, COM 3.0.x running n 2008 R2 can be upgraded Yes, this can be upgraded N, this cannt be upgraded N, this cannt be upgraded N, this cannt be upgrade Yes. If needed t install COM n a new hst. Yes. If needed t install COM n a new hst. Yes, COM data needs t be migrated Yes, COM data needs t be migrated N, data migratin is nt supprted See the manual migratin sectin fr windws See the manual migratin sectin fr RHEL See the manual migratin sectin fr windws See the manual migratin sectin fr RHEL N/A COM 3.1 OVA RHEL v5.7 Yes, this can be upgraded NA See the manual migratin sectin fr RHEL 2015 Avaya Inc Issue: 1.0 (28 th January 2015) Page 12 f 22

13 9.1. Manual Data migratin frm existing COM 3.0.x installatin When the lder versin f COM (r3.01 and r3.0.2) exists n a server with 32-bit OS r n a 64-bit OS that is incmpatible with COM (e.g. 64-bit Windws Server R2 SP1 standard/enterprise r 64-bit RHEL 5.6/5.7), then there is a need t migrate the UCM/COM data frm the lder server t a new installatin f COM This sectin explains hw this can be dne. The fllwing scenaris are pssible. 1) Mving t COM frm COM 3.0.x running n 32bit OS 2) Mving t COM frm COM 3.0.x running n 64bit OS incmpatible with COM 3.1. Fllwing steps describe the wrkflw fr migrating frm lder versin f COM t COM Pre-requisite: Older versin (release 3.0.x) f COM running as UCM Primary. Steps fr Windws servers: 1. Dwnlad the file Migratin_Frm_32Bit_UCM_T_SMGR-CS.zip frm the same Avaya Supprt page frm which yu dwnladed COM installer and unzip it. In its cntent yu will find anther zip file named - ucm-t-smgr-migratin-windws.zip. a. G thrugh the ReadMe file in the main zip file yu have dwnladed, befre prceeding further. b. Nw unzip the file ucm-t-smgr-migratin-windws.zip. 2. Back up the data n COM 3.0.x. a. Take back up n UCM by running the script backupdatamigratin.bat. b. Upn successful cmpletin, it will generate a jar file (like _13.06.jar) and a zip file (as JbssQuantumMigratin.zip) in the backups flder f UCM (<UCM-dir>\backups\). 3. Install COM n a 64-bit Windws 2008 R2 SP1 Standard/Enterprise. 4. Obtain new COM License and install the license. 5. Nw Cpy the backup data jar file t backups flder in SMGR-CS (<smgr-dir>\backups\>) and zip file t the <smgr-dir>\cre\tmp flder n windws. 6. T restre the data n SMGR-CS, run restredatamigratin.bat present in COM <smgr-dir>\bin. 7. Upn successful cmpletin, lgin t SMGR-CS and verify if the app is functining as expected and that the data has been restred frm UCM. The default username is admin and default passwrd is admin123 (bth withut qutes). 8. This cmpletes the data migratin frm COM 3.0.x n UCM Primary t COM n SMGR-CS Primary Avaya Inc Issue: 1.0 (28 th January 2015) Page 13 f 22

14 Steps fr RHEL servers: 1. Dwnlad the file Migratin_Frm_32Bit_UCM_T_SMGR-CS.zip frm the same Avaya Supprt page frm which yu dwnladed COM installer and unzip it. In its cntent yu will find anther zip file named - ucm-t-smgr-migratin-linux.zip. a. G thrugh the ReadMe file in the main zip file yu have dwnladed, befre prceeding further. b. Nw unzip the file ucm-t-smgr-migratin-linux.zip. 2. Please, fllw the instructins in it t back up the data n COM 3.0.x. a. Take back up n UCM using backupdatamigratin.sh. b. Upn successful cmpletin, it will generate a jar file (like _13.06.jar) and a zip file(as JbssQuantumMigratin.zip) in the backups flder f UCM (<ucm-dir>/backups/). 3. Install COM n a 64-bit RHEL v5.6/v5.7 hst. 4. Obtain new COM License and install the license. 5. Nw Cpy the backup data jar file t backups flder in SMGR-CS (<smgr-dir>/backups/) and zip file t the /tmp flder. 6. T restre the data n SMGR-CS, run restredatamigratin.sh present in COM <smgr-dir>/bin. 7. Upn successful cmpletin, lgin t SMGR-CS and verify if the app is functining as expected and that the data has been restred frm UCM. The default username is admin and default passwrd is admin123 (bth withut qutes). 8. This cmpletes the data migratin frm COM 3.0.x n UCM Primary t COM n SMGR-CS Primary Avaya Inc Issue: 1.0 (28 th January 2015) Page 14 f 22

15 10. Limitatins and Knwn Issues COM has the fllwing limitatins and knwn issues Limitatins N space character is allwed in the path name fr the installatin flder (pre-check exists in the installer) a limitatin inherited frm JBss Cnfiguratin Audit Tl (CAT) des nt supprt ERS8k devices running in ACLI mde Device Issues wi : VSP7024XLS-sw versin ASCII Cnfig File uplad is failing wi : ERS5600-sw versin (Build 33) - Binary Cnfig File Uplad is failing wi : ERS5600-sw versin (Build 28) - ASCII Cnfig File Dwnlad is failing wi : ERS5600-sw versin (Build 33) - ASCII Cnfig File Dwnlad is failing wi : COM ERS 5K ( ) - SNMPv3 - Facing errr while reading devices wi : COM ERS 5K ( ) - SNMPv3 - Facing errr while reading devices wi : COM Ruting Manager - IPv4 - ARP - Add / Delete ARP entry Fails VSP7k Knwn Issues Installatin/Upgrade related: EDM Manager: COM installer requires the system language t be set t English (US). Visual C and abve versins shuld be uninstalled frm the system t install Aura System Manager based COM The required Visual C++ can be installed pst the COM installatin. JDM (fr sw versins f devices that are ld and d nt have EDM plugin) des nt wrk with Java 7. If yur brwser has Java 7 plugins/add-ns installed, yu need t disable it and use Java 6 plugins. Limitatins/issues in COM supprt fr VSP7000: COM des nt discver a VSP7k device which uses nly Out-f-band management using the dedicated management prt. Inventry Manager actins give errr ( ncreatin SNMP errr) fr ASCII cnfig file uplad/dwnlad fr VSP7k. Inventry Manager binary cnfig uplad/dwnlad may require increasing the SNMP timeut in the Preferences t 10sec r mre. (Applies t VSP7k sw 7.2.x and lder). VSP7000 Device Limitatins affecting COM functinality: 2015 Avaya Inc Issue: 1.0 (28 th January 2015) Page 15 f 22

16 SONMP packets are nt sent n BEB-BCB ISIS links (even when device is SONMP enabled). Therefre, these links are nt discvered by COM and t discver bth devices, bth f them need t be specified as seeds. Dump Tplgy des nt shw these links; but Shw Cnnectins d. TACACS settings and Web Passwrd settings related SNMP MIBs are nt supprted in VSP7k. S these peratins will result in ncreatin SNMP errr. MLT Manager related: Tls related: Remving last VLAN frm an active MLT culd cause lss f cnnectivity t the device. COM des nt shw any warning when this is attempted. CLI*Manager tl (a Java Webstart applicatin), when first launched creates <OS lgin name>.ppk file in the specified wrking directry. But the tl expects this file t be in the fllwing lcatin Windws Same directry frm where CLI*Manager is launched (typically the Desktp) Linux In the /rt/ directry. S, mve the file <OS lgin name>.ppk t the abve directry frm the specified wrking directry and re-launch CLI*Manager. If Firefx is yur default brwser, then fr CLI*Manager t wrk, yu need t set the brwser prxy settings t Use System Prxy settings. TFTP Server tl the Rt directry and Lg file name specified in the tl s preferences d nt indicate where they are lcated n the server. The lcatin is dependent n the OS, and are relative t the fllwing path Windws they are relative t <JBOSS_HOME>/bin/ Linux they are relative t JBOSS/bin. CAT Tl pens a blank page frm IE9.x and IE10.x with a JavaScript errr. It wrks fine n IE8 and als in all supprted versins f FireFx brwser. Brwser supprt related: License installatin des nt wrk with IE brwsers when the abslute path t the license file t be installed cntains a directry whse name has a dt (. ) in it (e.g. C:\licenses\COM3.1.1\myLicense.lic). Virtual Machine related: TFTP data transfer des nt wrk prperly (times ut) when the VNIC used by the Virtual Machine is f type VMXNET3. It is recmmended t use E1000 type f VNIC fr the Virtual Machine Avaya Inc Issue: 1.0 (28 th January 2015) Page 16 f 22

17 11. Miscellaneus Infrmatin General Inf Default User ID and Passwrd fr accessing newly installed Aura System Manager based COM is admin / admin123 After installatin/upgrade cmpletes successfully as well as after a restart f the COM applicatin, it takes a few minutes (abut 5 minutes) fr the applicatin t be available fr client access Recmmendatins fr Imprved Netwrk Discvery Fllwing set f prcedures t be fllwed n mdular devices (ERS 8k series, VSP 9k series, VSP 4k series and VSP 8 k series) t frce/priritize a device t always send the cnfigured management IP Address in the SONMP Discvery packets. This will result in the aut tplgy table n its neighbr devices t cntain the management IP Address f the device instead f the IP Address f the interface f the device that cnnects t the neighbr. This helps COM netwrk discvery t clearly identify the end devices f each link, even when the interface IP addresses are duplicated in the netwrk, resulting in significant reductin in the number f lgical hubs (physically nn-existing) being displayed in COM tplgy Prcedure t frce management IP: ERS 8600/8800 (ACLI mde): Using ACLI user interface, execute the fllwing cmmands in the cnfig mde: (cnfig)# sys frce-tplgy-ip-flag enable (cnfig)# shw sys setting FrceTplgyIpFlag : true clipid-tplgy-ip: X (If clipid-tplgy-ip is nt 0, then find ut the IP address fr the CLIP id X using shw ip interface cmmand and run the fllwing cmmand) (cnfig)# n ip address x.x.x.x/x (cnfig)# shw sys setting FrceTplgyIpFlag : true clipid-tplgy-ip: 0 ERS 8600/8800 (CLI mde): 2015 Avaya Inc Issue: 1.0 (28 th January 2015) Page 17 f 22

18 Using CLI user interface, execute the fllwing cmmands in the cnfig mde: (cnfig)# sys set frce-tplgy-ip-flag true (cnfig)# shw sys set-tplgy-ip # TOPOLOGY-CLIP-IP # clip-ip Set as Tplgy-ip : <ipaddr> (If a clip-ip has been set, then use the cmmand belw t delete that clip) (cnfig)# ip circuitless-ip-int <id> delete <ipaddr> (cnfig)# shw sys set-tplgy-ip # TOPOLOGY-CLIP-IP # VSP 9000, VSP 8000 and VSP 4000: Using ACLI user interface, execute the fllwing cmmands in the cnfig mde: (cnfig)# sys frce-tplgy-ip-flag enable (cnfig)# default sys clipid-tplgy-ip (cnfig)# shw sys setting FrceTplgyIpFlag : true clipid-tplgy-ip : Avaya Inc Issue: 1.0 (28 th January 2015) Page 18 f 22

19 11.3. Wrkarund fr script running slwly - brwser issue COM uses java script technlgy which executes scripts n the client brwser. Hwever, fr large cnfiguratins, the script may take lnger t execute and may be seen by the brwser as a lp that may need t be terminated by the user. This issue is mre prnunced in IE. If such an issue is encuntered, yu will see pp-ups asking whether yu want t terminate the script. Yu can select N (In IE) and Cntinue (in FF) t ignre this pp-up r yu may permanently change the time after which the pp-up is seen (r disable it cmpletely). T change yur brwser settings, use the fllwing instructins: Fr Firefx: Type abut:cnfig in the address bar and filter fr the string dm.max_script_run_time. The default setting is 20 (secnds), add sme mre time, raise it t 40 fr instance. Fr Internet Explrer: Using a Registry Editr such as Regedt32.exe, pen this key: HKEY_CURRENT_USER\Sftware\Micrsft\Internet Explrer\Styles Nte If the Styles key is nt present; create a new key that is called Styles. Create a new DWORD value called "MaxScriptStatements" under this key and set the value t the desired number f script statements. If yu are unsure f what value yu need t set this t, yu can set it t a DWORD value f 0xFFFFFFFF t cmpletely avid the dialg. By default the key desn't exist. If the key has nt been added, the default threshld limit fr the time-ut dialg bx is 5,000,000 statements fr Internet Explrer 4 and later. Mre infrmatin is available at General Recmmendatins T circumvent sme f the knwn issues, the fllwing recmmendatins shuld be adhered t: Fr using the feature in COM (including BCM) r t test feature thrugh the test buttn, the Firewall and Antivirus shuld have a rule t allw COM t send . If is blcked n the COM server, the user will see an errr Message Exceptin and the will nt be sent. It is recmmended t enable SONMP prtcl n devices even if LLDP is enabled since sme types f devices d nt supprt LLDP currently, they will nt be discvered using seeds which have nly LLDP enabled. It is recmmended that yu d nt imprt Device Inventry xml file frm an lder versins f COM (COM 2.3, 2.3.x) int COM Device inventry xml exprted in COM 3.0.x is cmpatible with COM IE9 and IE10 brwser requires the setting f Tls/internet ptins/advanced D nt save encrypted pages t disk t be un-checked in-rder fr the JDM tl t be launched crrectly. BCM peratins such as CUG might require paginatin t be disabled based n the user script. In case f ERS 35xx/4xxx/5xxx, check the terminal length n the device using CLI. Set terminal length t 0. In case f ERS 83xx/86xx/88xx, check the CLI settings n the device and make sure mre is set t false. Fr the sftware versin upgrade peratins n ERS 8600 v7.2.14, Release Ntes recmmends t always keep DLD files in Flash. Kindly refer the fllwing dcument n Avaya supprt site ERS 8600 SVU - L2 C issue handling custmer is recmmended t handle manual upgrade in case f L2C issue in 8692 cpu dual pwer supply Avaya Inc Issue: 1.0 (28 th January 2015) Page 19 f 22

20 12. List f COM dcuments Fllwing is a list f dcuments available fr Cnfiguratin and Orchestratin Manager (COM) Release Nte that these dcuments remain same as in COM Release Ntes (this dcument) - Avaya Cnfiguratin and Orchestratin Manager Release NN Issue 07.01, Avaya Cnfiguratin and Orchestratin Manager Installatin 3. NN Issue 07.01, Avaya Cnfiguratin and Orchestratin Manager Fundamentals 4. NN Issue 08.01, Avaya Cnfiguratin and Orchestratin Manager Administratin 5. NN Issue 05.01, Avaya Bulk Cnfiguratin Manager Fundamentals 6. NN Issue 05.01, System Manager Cmmn Services Fundamentals These dcuments are available at Avaya Supprt site (supprt.avaya.cm) Avaya Inc Issue: 1.0 (28 th January 2015) Page 20 f 22

21 Appendix: Device Supprt (cmprehensive list) Fllwing devices are fficially supprted by COM Device Virtual Services Platfrm 4000 Virtual Services Platfrm 8200 Sftware release 3.0, 3.0.1, 3.1, 4.0, , , 4.1(partial supprt) 4.0, , 4.1(partial supprt) Virtual Services Platfrm , 3.1, 3.2, 3.3, 3.4, Ethernet Ruting Switch 8600 & 8800 including the fllwing hardware: 8681XLW mdule, 8681XLR mdule, 8616GTE mdule, 8672ATME MDA, 8608GBM mdule, 8608GTM mdule, 8632TXM mdule, 8648TXM mdule, 8672ATMM mdule, 8683POSM mdule. 4.0, 4.1, 5.0, 5.1, 7.0, 7.1, 7.1.3, 7.1.5, 7.2, , , x, Virtual Services Platfrm , 10.2, , 10.3, , , Ethernet Ruting Switch 55xx/56xx Ethernet Ruting Switch 45xx/48xx Ethernet Ruting Switch 35xx Ethernet Ruting Switch 25xx Ethernet Ruting Switch 16xx WLAN 5.1, 6.0, 6.1, 6.2, 6.3, 6.6, 6.3.4, , 5.3, 5.4, 5.5, 5.6, 5.6.1, 5.6.2, 5.7, , 5.0.1, 5.0.2, 5.1, 5.1.1, x, 4.2, 4.3, x, x 23xx, AP 23xx WLAN WC8100, AP , 1.1, 1.2 Belden NOTE: 1. Device versin(s) highlighted in green clr are the new device releases which are supprted as part f COM release. 2. partial supprt implies device discvery, tplgy display and installatin and launching f EDM plugin are the nly features supprted Avaya Inc Issue: 1.0 (28 th January 2015) Page 21 f 22

22 Fllwing device supprt is available with COM but the test cverage n these devices isn t cmplete (shuld wrk but lacks fficial supprt) Device Sftware release Ethernet Ruting Switch 8600, 3.0, 3.0.x, 3.1.x, 3.2.0, , , 3.2.2, 3.3, 3.5, 3.7 including the fllwing hardware: 8681XLW mdule, 8681XLR mdule, 8616GTE mdule, 8672ATME MDA, 8608GBM mdule, 8608GTM mdule, 8632TXM mdule, 8648TXM mdule, 8672ATMM mdule, 8683POSM mdule. Ethernet Ruting Switch 8600 WebOS 9.x, 10.0.x Web Switching Mdule Ethernet Ruting 2.0, , 3.1.x, 3.2.0, , , 3.2.2, 3.3 Switch 8100 Ethernet Ruting 2.0, 2.1, 2.2, 2.2.8, 2.3, 3.0, 4.0, 4.1, 4.2 Switch 8300 Passprt 1050/1150/ , , , , , 2.1.0, /1250 Ethernet Ruting 2.1 Switch 1424T Ethernet Ruting 1.0, 1.2, 2.1 Switch 1612G, 1624G, 1648T BayStack 350/410/ 3.0, 3.1, 4.0, 4.1, 4.2, 4.3, Business Plicy Switch , 1.0.1, 1.1, 1.2, 2.x, 3.0, 3.1 BayStack T 2.0, 3.0 BayStack , 1.0.2, 1.1, 1.1.1, 1.1.2,1.1.3, 3.0, 3.1 Ethernet Switch , 3.0, 3.1, 3.5, 3.6, 3.7 Ethernet Switch 3.0, 3.0, 3.1, 3.5, 3.6, T Ethernet Switch (standalne nly), 2.2.0, (stack als supprted), T 3.0, 3.0, 3.1, 3.5, 3.6, 3.7 Ethernet Switch 2.0, 3.0, 3.0, 3.1, 3.5, T Ethernet Switch 3.1, 3.5, T Ethernet Ruting 3.0, , 4.0, 4.1, 4.2, 4.3, 5.0 Switch 5510, 5520 Ethernet Ruting 4.2, 4.3, 5.0 Switch 5530 Ethernet Ruting 4.0 Switch 3510 Ethernet Ruting 5.0 Switch 45xx Ethernet Ruting 4.0, 4.1.x, 4.2 Switch 25xx Alten 2208, 2216, AOS , 2424, 2424 SSL, 3408 OPTera Metr 1.0, 1.2, /1400/1450 WLAN 2200 AP Avaya Inc Issue: 1.0 (28 th January 2015) Page 22 f 22