readme file for cisco ana 3.7.3.1.0 service patch · patch on server patch...

All contents are Copyright © 2011 Cisco Systems, Inc. All rights reserved.

Readme File for Cisco ANA

3.7.3.1.0 Service Patch

Revised: October 28, 2011

This document supports the release of the Cisco Active Network Abstraction (ANA)

3.7.3.1.0, which is installed on top of Cisco ANA 3.7.3.

Note: All changes described in this document apply only to Cisco ANA 3.7.3.

Note: This Service Patch accumulates previous point patches of 3.7.3.0.x.

Note: This Service Patch installation prompts you with an option to install the latest

device package.

Note: Please also remember to update ANA Configuration and Image Management

Software to the latest ANA CIM 1.2 patch from: http://www.cisco.com/cisco/software/type.html?mdfid=282861328&flowid=24948

1 Contents This document includes the following sections:

1 Contents 1

2 Obtaining the Service Patch 1

3 Service Patch Contents 2

4 Installing the Service Patch 2

5 Verifying the Service Patch Installation 4

6 Uninstalling the Service Patch 5

7 Verifying the Service Patch Uninstalling 8

8 Resolved Caveats – Cisco ANA 3.7.3.1.0 Service Patch. 9

9 Bug Resolutions That Require VNE Device Package 14

10 Changes to Workflow and Service Activation Management 14

11 Obtaining Documentation, Support and Security Guidelines 19

2 Obtaining the Service Patch

To obtain the Cisco ANA 3.7.3.1.0 Service Patch for installation, contact Cisco

Professional Services or visit the Cisco ANA CCO download page.

http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=282861328&flowid=24948&softwareid=283613397

http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=282861328&flowid=24948&softwareid=283613397

http://www.cisco.com/cisco/software/type.html?mdfid=282861328&flowid=24948


3 Service Patch Contents Cisco ANA 3.7.3.1.0 Service Patch contains:

The necessary files and scripts to upgrade successfully.

Resolved caveats, identified in Resolved Caveats – Cisco ANA 3.7.3.1.0 Service

Patch.

4 Installing the Service Patch This procedure describes how to install the Cisco ANA 3.7.3.1.0 Service Patch on top of

an existing Cisco ANA 3.7.3 installation.

Before You Begin

1. If you are using the HA/DR VERITAS solution:

a) Uncheck the critical flag from the Cisco ANA gateway resource in the VERITAS

Cluster Manager application.

b) Via the VERITAS Cluster Manager, bring ANA offline

c) Disable the Cisco ANA gateway resource in the VERITAS Cluster Manager

application.

d) Login to the gateway and start ANA by running “anactl start“.

e) Wait until ANA gateway and units are up and running before continuing with this

patch installation.

f) After the patch has been successfully installed, enable the ANA gateway resource

and mark it as critical in the VERITAS Cluster Manager application

2. If you are using the LINUX RHCS solution:

Log into the Cisco ANA gateway as root user and move the services into freeze mode,

by running:

a) clusvcadm –Z <ANA service>

b) clusvcadm –Z <Oracle service>

For example:

clusvcadm -Z ana

clusvcadm -Z oracle_db

3. Make sure the Cisco ANA gateway and units are up and running before installing the

Service Patch.

4. Copy the Service Patch to a directory outside of the Cisco ANA home directory.

5. Grant the directory Cisco ANA user permission.

For example, after you log into the Cisco ANA gateway as root user, you might enter

commands similar to the following:

cd /export/home


mkdir 3.7.3.1.0

chown <ANA-user>:ana 3.7.3.1.0

Example: chown ana37:ana 3.7.3.1.0

Notes

The installation process is configured to execute automatic backup of all the files

under the Cisco ANA home directory. Creating the backup zip file can take up to one

hour.

You can abort the installation if a backup of the database has not been performed.

You are prompted for a destination path for the backup file and to indicate the

required disk space requirements. This path location cannot be $ANAHOME.

Grant ANA user permission to the Cisco ANA backup directory.

The backup file name is appended with the UNIX time stamp of the gateway

machine.

The file format of the backup is AnaBackUp_<unix_time>.tar.gz.

We recommend that you install Cisco ANA 3.7.3.1.0 Service Patch with the default

option: perl upgrade.pl –p.

To install the Service Patch without a backup (that is, without the option to roll back,

or a manual rollback), run the upgrade.pl script with the –nobackup option, as

follows:

perl upgrade.pl –p –nobackup

This Service Patch might include database table changes. If you would like the option

to roll back to a previous point patch, back up the database.

If your setup is installed with an embedded database, see the “Performing a Manual

Backup of an Embedded Database and Cisco ANA” section in the Cisco Active

Network Abstraction Administrator Guide, 3.7.3

The upgrade script prompts you with an option to install

The Cisco ANA gateway and units restart automatically after the installation has

completed successfully.

Installation Procedure

1. Log into the Cisco ANA gateway as ANA user.

2. Navigate to the directory in which you placed the Service Patch. (See Before You

Begin.)

3. To extract the necessary JAR files and Perl scripts, unzip the file by entering the

following command:

unzip ANA3.7.3.1.0.zip

http://preview.cisco.com/en/US/docs/net_mgmt/active_network_abstraction/3.7.3/administrator/guide/internal_db.html#wp1078616



4. Navigate to the ANA_upgrade directory:

cd ANA_upgrade

5. Enter one of the following commands, depending on whether or not you want to install

the Service Patch with the option to roll back:

To install the Service Patch and create a backup file, enter:

perl upgrade.pl -p

To install the Service Patch without creating a backup file, enter:

perl upgrade.pl –p -nobackup

6. Wait until the Cisco ANA gateway is up and running.

7. If you are using the HA/DR VERITAS solution, check the critical flag from the Cisco

ANA gateway resource in VERITAS Cluster Manager application.


Log into the Cisco ANA gateway as root user and move the services out of freeze

mode, by running:

a) clusvcadm -U <ANA service>

b) clusvcadm -U <Oracle service>

5 Verifying the Service Patch Installation

This section describes how to verify that Cisco ANA 3.7.3.1.0 Service Patch has been

installed successfully, as explained in Section 4, Installing the Service Patch.

This procedure uses the script ~/Main/scripts/checkPatchInstallation.pl to confirm that

the Service Patch has been installed correctly.

Note: Execute the commands from the gateway.

Verification Procedure

1. Enter the following command to determine the version of the Service Patch installed:

checkPatchInstallation.pl -p

The gateway responds with the Service Patch information, such as:

Current patch (in 127.0.0.1): ANA3.7.3.1.0_SP.jar:patch.jar

2. Enter the following command to determine whether all components of the Service

Patch installed successfully:

checkPatchInstallation.pl ANA3.7.3.1.0_SP.jar

If the installation was successful, information similar to the following is displayed:

Patch ANA3.7.3.1.0_SP.jar correctly installed in the gateway

(127.0.0.1)


Patch ANA3.7.3.1.0_SP.jar correctly installed in the golden source

registry (0.0.0.0)

Patch ANA3.7.3.1.0_SP.jar correctly installed in the unit <unit IP>

Patch ANA3.7.3.1.0_SP.jar correctly found at the start of 0.out log

file

Patch ANA3.7.3.1.0_SP.jar correctly found as the first reference on

file /export/home/ana37/Main/webstart/agentregistryviewer.jnlp


file /export/home/ana37/Main/webstart/bosmanage.jnlp


file /export/home/ana37/Main/webstart/dcdebugger.jnlp


file /export/home/ana37/Main/webstart/eventvision.jnlp


file /export/home/ana37/Main/webstart/networkvision.jnlp


file /export/home/ana37/Main/webstart/processdebugger.jnlp


file /export/home/ana37/Main/webstart/regedit.jnlp


file /export/home/ana37/Main/webstart/sessiondebugger.jnlp


file /export/home/ana37/Main/webstart/stresser.jnlp


file /export/home/ana37/Main/webstart/workflowstudio.jnlp

Patch ANA3.7.3.1.0_SP.jar's classes files are being called from this

patch on server 127.0.0.1

Patch ANA3.7.3.1.0_SP.jar's xml files are being called from this

patch on server 127.0.0.1

Patch ANA3.7.3.1.0_SP.jar's classes files are being called from this

patch on server <unit IP>

Patch ANA3.7.3.1.0_SP.jar's xml files are being called from this

patch on server <unit IP>

---> Patch ANA3.7.3.1.0_SP.jar correctly installed

If the installation was not successful, messages are displayed that indicate where

problems are located. The final line in the report is:

---> Patch ANA3.7.3.1.0_SP.jar not correctly installed or at least

one warning displayed

6 Uninstalling the Service Patch

This procedure describes how to uninstall the Service Patch. You do not need to uninstall

a Service Patch unless you need to completely remove the Service Patch.

Note: you can uninstall the Service Patch only if it was installed with the backup option,

using the command: perl upgrade.pl –p.

Rollback Procedure

1. If you are using the HA/DR VERITAS solution:


a) Uncheck the critical flag from the Cisco ANA gateway resource in the VERITAS

Cluster Manager application.

b) Via the VERITAS Cluster Manager, bring ANA offline

c) Disable the Cisco ANA gateway resource in the VERITAS Cluster Manager

application.

d) Login to the gateway and start ANA by running “anactl start“.

e) Wait until ANA gateway and units are up and running before continuing with this

patch uninstall.

f) After the patch has been successfully uninstalled, enable the ANA gateway

resource and mark it as critical in the VERITAS Cluster Manager application



mode, by running:

a) clusvcadm -Z <ANA service>

b) clusvcadm -Z <Oracle service>

2. Log into the Cisco ANA gateway as ANA user.

Stop Cisco ANA by entering the following commands:

anactl stop

3. Log into the Cisco ANA units as ANA user.

Stop Cisco ANA by entering the following command on the units:

anactl stop

4. Restore the Cisco ANA database:

For an embedded database, see “Restoring an Embedded Database and

Cisco ANA “ section in the Cisco Active Network Abstraction Administrator

Guide, 3.7.3

For a non-embedded database setup, restore the backed-up database and start

the database services and the listener. The database table structure is changed

during the upgrade. In order for the system to function correctly after a rollback,

the old table structure must be recovered through a database backup.

5. Verify that the gateway and unit workstations can communicate via ssh.

6. Navigate to the ANA_upgrade directory in the 3.7.3.1.0 directory you created for

installing the Service Patch:

cd 3.7.3.1.0/ANA_upgrade

7. As the Cisco ANA user, enter the following command on the Cisco ANA gateway only:

perl rollback.pl

Note: Do not deploy the rollback.pl script in the Cisco ANA home directory. If you deploy the




rollback.pl script in the Cisco ANA home directory, the rollback fails and the home directory is removed.

8. At the prompt "Are you sure you want to roll back the current ANA installation," enter yes:

- Writing log to /export/home/ana-upgrade/ANA_upgrade/rollback-

number.log

- Are you sure you want to rollback the current ANA installation?

(yes,no)[default yes] yes

- Stopping ANA on GW & units

9. At the prompt "Please enter the full path to the backup archive file," enter the location of the backup archive directory. The rollback.pl script does not delete the backup archive.

- Please enter the full path to the backup archive file:

/export/home/ana-upgrade/AnaBkup/AnaBackUp_<unix_time>.tar.gz

10. The scripts revert the gateway back to its earlier version:

- Removing content of /export/home/ana37

[OK]

- Extracting backup archive under /export/home/ana37

[OK]

- Starting ANA on GW

+ Rollback completed successfully.

Please remember to do the following:

- Manually roll back database changes because ANA does not roll

back these changes.

- Reinstall the units (see the ANA Installation Guide for

instructions)

- Re-login as the ANA user for environment changes take place

check logs for further information.

- Rollback logs can be found at <logFile>

11. If your environment contains a standby unit, use Cisco ANA Manage to remove the

standby unit from the gateway.

12. If you are using the HA/DR VERITAS solution, check the critical flag from the Cisco

ANA gateway resource in VERITAS Cluster Manager application.



mode, by running:

a. clusvcadm -U <ANA service>

b. clusvcadm -U <Oracle service>


14. Reinstall all units (including running ana-conf on all units). Then, use the anactl restart

command to restart the nonstandby units.

15. Use Cisco ANA Manage to reconnect the standby unit.

16. After the rollback to your original Cisco ANA 3.7.x environment is complete,

reconfigure your user-defined crontabs.

7 Verifying the Service Patch Uninstalling

This procedure allows you to verify that the Service Patch was uninstalled successfully.

Uninstalling Verification Procedure

1. On the Cisco ANA gateway, log in as ANA user.

2. Navigate to the Main directory.

3. Enter the following command:

./runRegTool.sh -gs 127.0.0.1 get 0.0.0.0 site/mvm/services/bsm/patchjar

You should not see the Service Patch that was removed.


./runRegTool.sh -gs 127.0.0.1 get 127.0.0.1 site/mvm/services/bsm/patchjar


5. Enter the following command from the Cisco ANA gateway for all the units:

./runRegTool.sh -gs 127.0.0.1 get <unit ip> site/mvm/services/bsm/patchjar


6. To verify that the ANA3.7.3.1.0_SP.jar file does not exist in any of the JNLP files,

enter the following command:

cat ~/Main/webstart/*.jnlp | grep ANA3.7.3.1.0_SP.jar

The output should be empty.


find ~/Main/ -name ANA3.7.3.1.0_SP.jar


8. Navigate to the logs directory (~/Main/logs).

9. Check the AVM 0 log file by entering the following command:

cat 0.out | grep ANA3.7.3.1.0_SP.jar



10. Check the AVM 11 log file by entering the following command:

cat 11.out | grep ANA3.7.3.1.0_SP.jar


8 Resolved Caveats – Cisco ANA 3.7.3.1.0 Service Patch.

The following caveats have been fixed in Cisco ANA 3.7.3.1.0 Service Patch.

Resolved Caveats - 3.7.3.1.0 Service Patch

Identifier Summary

CSCtn95986 Workflow search by attribute CR

CSCtq17593 Rollback.pl can be used with illegal parameters

CSCto02398 "Old version, code should be fixed" Error massage in AVM log

CSCtq32240 Inconsistent check for repeated characters in the user password

CSCtq53116 Excessive log messages in AVM 100

CSCtq57932 OSPF-5-ADJCHG syslog alarms have empty location string

CSCtq47378 Flapping update definition adjustment needed

CSCto71654 MPLS L3VPN trap correlation issue

CSCtq64162 ANA does not block user that is disabled and already connected to ANA vi

CSCtn99082 CheckPatchInstallation.pl print that PP in correctly installed for unre

CSCto67409 unable to add soft properties to Sonet High Order entries

CSCtq24620 Ticket not removable in Network Vision

CSCtq24603 Column names in Cisco ANA EventVision differ from Filter dialog fields

CSCtq24793 Ticket Property:Correlation Tab export does not include Severity/AlarmID

CSCtq09169 partitioning on sheer_ep schema stopped to work after Oracle exception

CSCtn28420 add a management command for the recorder from persistency

CSCtq63690 Spaces should be added in "Failed to move AVM 201from:" log

CSCtq01992 BQL No Error or feedback querying a non-existent user

CSCtq40518 Duplicated commands while changing Context IMO

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtn95986

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtq17593

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCto02398



















Identifier Summary

CSCto99292 Unregistering for Security Get&Register BQL Commands leading to timeout

CSCtq22377 Line Up/Down Syslog message not associated with EFP

CSCtn57568 Monitoring & archiving dangling events and auto-clearing old tickets

CSCto85571 ANA does not block user that is deleted and already connected to ANA vis

CSCtq34722 Wrong event description when Viewer try to open EventVision

CSCtq32270 GW not being able to reconnect to Units after shutdown connectivity

CSCtn77010 System Events traps forwarded with wrong fields

CSCtq37419 Export / Import of Command Builder Script fails

CSCtq12650 Independent Fans are not get correlated with main FAN ticket-ASR9k

CSCtq34559 Cannot create a soft property at module or submodule

CSCtn93039 Rollback remark on rollback DB should be in the beginning of the script

CSCtq94051 3.7.3 Readme updates

CSCtq06718 617520439 ASR-9006-DC, No Critical alarms forwarded to Netcool

CSCtq23210 Export Ticket Button greyed out on Network Event Vision

CSCtl20583 When loading AVM, the drivers jars order is not consistent

CSCtq29650 NullPointerException in ManagedElementReachabilityUtil for multi-context

CSCtq91078 After creating a redundant unit, it appears with a status of Unreachable

CSCtn96564 Unnecessary operation on patch.jar in upgrade.pl script

CSCtq82636 Exception in NetworkEventAspectListNotificationHandler.handleNotificatio

CSCtq45071 add Tellabs & DragonWave as a vendor in ana

CSCtq37445 Can't use DSA as algorithm on the device

CSCtq17422 NCCM HTTPS option not configurable in ANA

CSCtq05058 rollback script should not fail when anactl is missing

CSCtq75456 IVNE installation from web repository

CSCtq35111 Unknown polling interval in the soft property polling rate

CSCtg24887 Impossible to run Drool reload command via Command Excecuter (IMO)

CSCtq61838 persistency.xml file differs in 3.7.0 - 3.7.2 updgrade and 3.7.2 instal

CSCti24173 MOTD is NOT loaded after system restart















http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl20583











http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtg24887


http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCti24173



Identifier Summary

CSCtq40321 BQL : Multiple similar registrations possible

CSCtq22416 Power Down Scenario leads to two identical "Device Unreachable" tickets

CSCtr35194 Timer threads are flooding the AVM process

CSCtr16999 BFD neighbors not discovered by ANA for ASR9K device

CSCtq37320 Upgrade.pl does not add 3 columns to ITicket table in DB

CSCtr30314 Readme 3.7.3.0.1: Need add comment that DP installation is part on PP in

CSCtq04435 Embedded Oracle installation fails in Cisco ANA 3.7.2

CSCto33739 Cisco CRS-8 XR382: SIP Reload did not raise card down ticket

CSCtn92232 V1Traps are not displayed in ANA NetworkVision if varbind list is empty

CSCtq99049 No new tickets after ASR9K RSP Failover

CSCtr33456 Eval License Usage gets reset after a emdbctl --restore (current date)

CSCtq04992 Unit free memory decreases over time from 10-12 GB to 500 MB

CSCtr42785 Element Type entry for a Firewall in Cisco ANA

CSCtq18898 NCCM - username not encrypted in initial form

CSCto76046 When switching over in H/A, VNEs become stuck in Maintenance mode

CSCtq75086 OSServiceImpl doesn't listen to registry changes on gateway ip

CSCtq39668 Applying 3.7.2PP upgrade fixes to 3.7.3PP

CSCtq61687 Duplicate Link events GSR XR with "Link down on Unreachable"

CSCtq67830 ASR9k stuck in currently unsync after removing all power supply and inse

CSCto71158 Missing Link in Multi path window

CSCtr31327 VNEs remain unreachable after switching to redundant unit

CSCtq73235 Ethernet Counters don't get populated properly due to confusing API

CSCtr30287 Port down due to oper tickets do not get cleared in HA Env.

CSCtr62150 Unable to see the newly added soft properties in the ANA Networkvision

CSCtr13265 Workflow Migration is not migrating Template Display Name

CSCtq39320 Double error windows appear when tring change password from ANA vision

CSCtr71979 Workflow Search Migration from 3.7.3 PP to 3.8 should not run

CSCtq58847 Multicast transport between units is not working



http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtr35194




























Identifier Summary

CSCts00990 Port Utilization Graph does not display the graphs

CSCtn25053 Not correct modeling of the MPLS TE-Tunnel

CSCtl85746 Add new non cisco device types supported in device-group.properties

CSCts02948 HA warning timeout value is greater than timeout timer

CSCtq74471 EFP down ticket escape while reload ASR9k

CSCtq23799 HA:incorrect replication failure system events sometime

CSCtr01936 Search does not present 'Running" WF

CSCtr09652 WF Search Equals melfunction

CSCtr35398 Manage: Cannot delete Workflow Template (ClassCastException)

CSCto50214 AVM77 in Unreachable state with Dual NIC

CSCtq71590 ASR5k VNE goes to partially reachable and unsynchronized state

CSCto53346 Soft Property Error - LSEs-> Label Switching

CSCto53396 Soft Property Error - MPBGP

CSCtq75150 Build jars and DP jars under Main/Drivers/folder after ana-conf is rerun

CSCtr71232 L2 tunnel down events do not get cleared

CSCtr58821 ANA373 ASR1K- MLPPP down ticket not correlating to SPA Card down Ticket

CSCtr10518 NSA - CLI Output is not exported

CSCtr55747 VFI pseudowire is not modeling in RLS10 image

CSCtr35352 Nullpointer exception appear in AVM 11 when create SP

CSCtr72682 Change topo_l1 from 30000 to 90000 in pollinggroups.xml

CSCts30980 NCCM installer should stop if Oracle account is locked

CSCtr99971 IVNE installation over 3.7.3.0.2 shows changes compared to ANA 3.7.3 FCS

CSCts36590 VNE is investigating in old community string after changing it

CSCts43864 CRS4s is assigned to C8 device group instead of C7

CSCts42364 avm25 doesn't recover a database network disconnection

CSCts32502 Discovery port 161 assignement for AVM100 creates Java BindException

CSCts28001 ANA 3.8 65.2-7200 device shows as Unsupported while added as an EVNE

CSCts18351 Add Fortinet as a vendor in ana

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCts00990


http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl85746




























Identifier Summary

CSCts53175 Embedded DB backup time is negative

CSCtr95869 Manual backup of registry with default dir not working

CSCts05588 TCA alarm not deleted from site.xml when soft property deleted

CSCts42249 Link down event has a location of a port instead of a link

CSCtn28573 after bgp link is rediscover bgp link admin down ticket isn't produce

CSCto27921 Multi Context support -

CSCts69108 Change event-correlation-app.xml for RSP switch/reload correlation issue

CSCts34673 EVNE FW changes for Nexus 7000 EVNE

CSCtr16429 Unable add unit that was redundant unit

CSCts59844 VNE with snmpv3 try to register to avm100 every ~30 sec when unreachable

CSCto57337 ANA 3.7.2 Scope permission issue in ticket with multiple device location

CSCtn56602 BGP Link down events are missing on route reflector links03

CSCts80497 Readme changes for Veritas steps + Section 9

CSCtn59106 SHDSL traffic profile descriptor not created in ANA 3.7.2

CSCts98324 incorrect path for end-to-end pw flow

CSCtt16887 Polling of ME3600X from NV causes link to go down

CSCto64838 from oracle 11g the default profile password is valid for 180 days

CSCtr35459 Cannot create Command builder on sub interface

CSCts64211 Security Violation on nsa activation history button with user operator

CSCtt17296 Missing reference to the RHEL Local HA if the patch install

CSCts96142 AVM 11 does not process any links for 15 min

CSCtr95957 OSAgent.handleThrowable - UNEXPECTED ERROR ... appear in AVM 25 log

CSCtr77944 Multiply services (registry, logger, ..) when client relogin(Avm.init).

CSCtt28425 switchover in cluster fails if ana service starts before db service














9 Bug Resolutions That Require VNE Device Package

The following bug resolutions are contained in this ANA Point-Patch. However, to completely resolve the bug you must also install a VNE Device Package that contains the associated VNE software fix. The following table describes these bugs and the VNE Device Package that is required (along with the associated VNE bug). To obtain any ANA patches, contact your Cisco representative.

Identifier Headline Resolved in Required Device Package (VNE Bug)

CSCto71654 MPLS L3VPN trap correlation issue ANA 3.7.3.0.1 DP 3.0 (CSCto08087)

CSCtq22377 Line Up/Down Syslog message not associated with EFP

ANA 3.7.3.0.1 DP 4.0 (CSCtq12003)

CSCto33739 Cisco CRS-8 XR382: SIP Reload did not raise card down ticket

ANA 3.7.3.0.2 DP 5.0 (CSCto69964)

CSCtq61687 Duplicate Link events GSR XR with "Link down on Unreachable"

ANA 3.7.3.0.2 DP 6.0 (CSCtr44804)

CSCtr72682 Change topo_l1 from 30000 to 90000 in pollinggroups.xml

ANA 3.7.3.0.3 DP 6.0 (CSCtr16473)

CSCto27921 Multi Context support ANA 3.7.3.1.0 T.B.D (CSCtt99843)

CSCts69108 Change event-correlation-app.xml for RSP switch/reload correlation issue

ANA 3.7.3.1.0 T.B.D (CSCtq75010)

CSCtn28573 after bgp link is rediscover bgp link admin down ticket isn't produce

ANA 3.7.3.1.0 T.B.D (CSCtt99843)

CSCts34673 EVNE FW changes for Nexus 7000 EVNE ANA 3.7.3.1.0 T.B.D (CSCtt99843)

10 Changes to Workflow and Service Activation Management

This chapter describes:

Feature Description

How to Access the Feature

How the Search Works

Search Results

Data Mapping, Upgrade & Migration

Database Implications

Maximum Result Size Configuration

http://cdetsweb-prd.cisco.com/apps/goto?identifier=CSCtn28573


AVM 66 Memory

Feature Description

ANA has been enhanced to maintain up to 500,000 workflows in the database and provide

workflow searching capabilities. Existing active workflows have been migrated so that

they are also searchable using the new enhanced search capabilities.

The searching capabilities include compound search criteria with match all or any

conditions, case insensitive string search, substring search support and using one or more

of the following workflow attributes:

Workflow ID

Template Name

User

Execution Time Range

State

Device Name

Device IP

Information - User-defined field

Search results will be displayed within 10 seconds.

The search results table has been enhanced to display the searchable attributes.

All the supported operations remain available. The Properties, Show Output, Deactivate and Deact ivate Preview operat ions are now avai lable as ri ght-click menu options inst ead of buttons.

How to Access the Feature

Workflows can be viewed in one of the following three ways:

In ANA Manage, select Workflow Engine > Workfl owsThe new search panel is displayed, allowing you to search

all workflows in ANA.

In ANA NetworkVision, select Show Service Activations > Service Activation List. The new search panel is

displayed, allowing you to search Service Activation workflows only.

In ANA NetworkVision, select A cti vation > Clone A cti vation. The new search panel is displayed,

allowing you to search active Service Activation workflows that match the selected

template name.

How the Search Works

After you have accessed the workflow search panel using one of the procedures above,

you can search for workflows as follows:


1. In the Execution Time area, enter the time period you want to search. By default, the

current day is selected. (This is a required field.)

2. In the Match area, enter the criteria you want the search to match.

Note If you only want to search by date, choose None from the Match drop-down list.

a. Select the Match operator:

– None—This is normally used if you want to perform a search based only on a

timeframe.

– Any—Return the workflow if it matches any of the rules.

– All—Return the workflow if it matches all of the rules.

Create a rule by selecting an attribute, operator, and value. The operators and values

that are displayed depend on the attribute you select.

If desired, create additional rules by clicking the plus button after the rule.

3. Click Search to display the results. The timestamp above the table indicates when the

query was run.

You can filter the table of results by using the tools that are directly above the table.

The following buttons are also provided:

• Previous Search— Displays the search criteria from the previous search.

• Clear— Clears all table data and criteria from the previous search.

The search is case insensitive, and wildcard characters are not supported

Search Results

After you have defined your search criteria and clicked Search, a tabular list of workflows

is displayed, sorted according to Workflow ID. The total number of workflows in the

system is listed at the top left of the window. This counter is updated whenever a

workflow is deleted or added to the system.

The timestamp above the table indicates when the query was executed (the results are a

snapshot of the data at that time and are not updated unless the search is rerun). You can

filter the table of results by using the tools that are directly above the table.

The search results table displays the following information:

• Workflow ID—The unique identifier of the service activation workflow job.

• Template Name—The name of the template used by this workflow. (All NSA templates are

indicated by the prefix NSA_.). This will appear only in ANA Manage.

• Template Display Name—The service name of the workflow template.

• State—The state of the service activation:

– Done—The activation successfully completed.

– Aborted—The activation failed.

– Ready—The activation is ready.

– Running—The activation is running.

• Execution Time—The time the workflow was executed.

• User—The user who executed the activation.


• Device name—The name of the devices on which the activation was performed.

• Device IP—The IP addresses of the devices on which the activation was performed.

• Information—Additional details, if available.

• Operation is missing (displayed only in Network Vision)

Use the right-click menu options to perform different operations on the workflows in the

search results table:

• To view the activation details of a selected workflow, select Properti es from the right-cl ick menu. The Properties window displays the

attributes for all of the Cisco ANA workflows, in NetworkVision only public parameters are

presented while in Manage private parameters are displayed as well

• To view the workflow output, select Show Output from the right -cli ck menu.

• To view the deactivate preview, select Deactivate Preview from the right-cl ick menu.

• To deactivate a workflow, choose the service you wish to deactivate and right-click the selected

workflow, choose Deactivate.

Eligible service workflows display “Add” in the Operation column, and “Done” or

“Aborted” in the State column. You can only preview deactivation and do deactivate

of one service at a time from the Service Activation List window.

Data Mapping, Upgrade & Migration

The following data mapping logic will take place on workflows data:

1. Every attribute that starts with „deviceName‟ (case insensitive) will be searchable using the

“Device Name” criteria

2. Every attribute that starts with „deviceIP‟ or IPAddress (case insensitive) will be searchable

using the “Device IP” criteria.

3. Every attribute that have the „info‟ string (case insensitive) in it will be searchable using the

“Information‟ criteria.

The same logic will take place upon workflows data migration, ensuring that the existing

workflows will be searchable using the new search capabilities.

The upgrade process will create a new table in the database following with its population

as part of the migration process.

The workflow migration process can be time consuming pending the number of the

workflows in the system. (~30,000 workflows can take ~20 minutes).

Database Implications

Having up to 500,000 NSA workflows in the database has implications on the database

table space required.


If the intention is to have more than 70,000 workflows and up to 500,000 workflows, the

database table space of DWE schema needs to be changed to a size of 47GB to be able to

hold a max value of 500,000 workflows.

For DWE 3.7.3 storage allocation, the following would be required:

1. If the free space threshold is exceeded, the following System Event is issued:

"$TS_NAME tablespace is $TS_FULL_PCT % full. If this is unexpected please refer to the Cisco

ANA Administrator guide"

2. As mentioned above, the size of the DWE schema should be changed to 47GB, to be able to hold

the capacity of 500K workflows.

In the 3.8 Capacity planning guide and Memory assessment Tool the sizing values will be updated

accordingly to support 500K workflows.

3. In the case of an embedded database, the actual storage addition can be done using the

add_emdb_storage.pl – command. When the above system event regarding space issues on

ANA37_DWE tablespace is received, please run the add_emdb_storage.pl command and providing

a higher value for the workflow archiving size in days.

The rest of the values should be the same as provided in the previous run (Profile & fault history

size).

Example:

ana37@sh-t1000-008 [~/Main/scripts/embedded_db]% add_emdb_storage.pl

- writing log to /export/home/ana37/Main/logs/emdb/add-storage-1307024614.log

- Retrieving registry information & initializing connection

- How would you estimate your DB profile?

-----------------------------------------

1) POC deployment (1 actionable events per second)

2) Small deployment (up to 5 actionable events per second)

3) Medium deployment (up to 20 actionable events per second)

4) Large deployment (up to 50 actionable events per second)

5) High scale deployment (up to 100 actionable events per second)

(1 - 5) [default 1] 1

- Insert the event archiving size in days. ANA default archive is 14 days:

[default 14] 2

- Insert the workflow archiving size in days. ANA default archive is 7

days: [default 7] 40

Maximum Result Size Configuration

The search result size is limited to a default value of 5000 workflows, which is configured

in the registry.

This value was benchmarked and certified as the number of results that will meet the

target for displaying the results in 10 seconds.

This value can be configured using the following steps:

1. Run command: ./runRegTool.sh -gs 127.0.0.1 set 127.0.0.1

cvm/management/workflow/searchResultMaxRawSize <number>

2. Run ~/Main/scripts/clientregpacker.sh

3. Reconnect with the client

Note: If you change this value so that a larger number of workflows are returned, the

target response time of 10 seconds might be exceeded.


AVM 66 Memory

AVM 66 memory size increased from 256 to 512 MB.

11 Obtaining Documentation, Support and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security

guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in

Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures

included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 1999-2011 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

readme file for cisco ana 3.7.3.1.0 service patch · patch on server patch...

Documents