Table Of Contents
Adding and Deleting Network Elements
Managing Network Auto Discovery and Seed Files
Understanding the Network Auto Discovery User Interface
Roles Required to Use Network Auto Discovery
Creating or Editing a Network Auto Discovery Configuration File
Performing Network Auto Discovery to Create a Seed File
Importing Network Elements Using the Seed File
Managing the Gateway
Roles Required to Stop or Start the Gateway
Managing Units (and High Availability)
Roles Required to Manage Units
Adding a New Unit
Viewing and Editing Unit Properties
Removing a Unit
Managing AVMs
Roles Required to Manage AVMs
Understanding AVM Status
Creating an AVM
Viewing and Editing AVM Properties
Starting and Stopping an AVM
Moving an AVM
Deleting an AVM
Managing VNEs
Roles Required to Manage VNEs
Understanding VNE Status
Prerequisites for Adding VNEs to AVMs
Defining and Creating a VNE
Viewing and Editing VNE Properties
Changing a VNE's State
Moving One or More VNEs
Deleting a VNE
Adding and Deleting Network Elements
These topics describe how to add, delete, and maintain network elements in ANA. You must have Administrator privileges to use these functions, unless otherwise noted.
•
Managing Network Auto Discovery and Seed Files
• Managing the Gateway
• Managing Units (and High Availability)
• Managing AVMs
• Managing VNEs
Managing Network Auto Discovery and Seed Files
ANA provides a Network Auto Discovery function that helps you create a list of elements in your network. In this way, you do not have to go through the tedious process of creating the list by hand. You can then refine the list to create your seed file, which specifies the elements you want ANA to manage. ANA then discovers those elements and create a model of them.
The following is an overview of this process, from performing network autodiscovery to importing the seed file.
1. Use Network Auto Discovery to discover existing devices:
a. Create a discovery configuration file that ANA uses to find existing network elements. You specify the discovery methods, seed device IP addresses, and hop counts for the discovery process. You can also specify dependent discovery methods, so the output from one method is used as the input to another method.
For example, if you configure the RoutingTable discovery method with the Neighbor method as a dependent, ANA runs the Neighbor discovery first, then uses those results as input to the RoutingTable discovery method.
If desired, you can save the discovery configuration file to use later. See Creating or Editing a Network Auto Discovery Configuration File.
b. Run the network autodiscovery process to create the list of elements in your network. You can run the job immediately or schedule it for a later time. See Performing Network Auto Discovery to Create a Seed File.
2. Use VNE Import to create a seed file and import the elements, so a ANA can manage them:
a. From the list of devices found during the autodiscovery process, choose the ones you want ANA to manage. This information is saved as the seed file.
b. Import the seed file. ANA discovers the network element details, and uses their information to create a model of the network.
See Importing Network Elements Using the Seed File.
Related Topics
• Understanding the Network Auto Discovery User Interface
• Roles Required to Use Network Auto Discovery
Understanding the Network Auto Discovery User Interface
The Network Auto Discovery user interface is where you configure the criteria you want ANA to use to create the seed file, as described in Creating or Editing a Network Auto Discovery Configuration File.
Figure 2-1 Network Auto Discovery User Interface
Roles Required to Use Network Auto Discovery
Table 2-1 lists the roles that are required to use Network Auto Discovery. For more information on roles, see Creating and Managing Users and Scopes, page 14-27.
Table 2-1 Roles Required to Use Network Auto Discovery
Task
|
Role Required
|
Create or edit autodiscovery settings
|
Administrator
|
Creating or Editing a Network Auto Discovery Configuration File
ANA discovers the elements in your network, based on parameters that you provide, such as discovery method, seed devices, and hop counts. You can specify the parameters and save them in a configuration file to be used or edited at another time. If you have a saved configuration file, you can import that file and make further edits.
Use this procedure to create or edit a discovery configuration file.
Step 1 Go to the Task tab in the Administration perspective and click the Other drawer.
Step 2 Double-click Network Auto Discovery (see Figure 2-1).
Step 3 If you have a saved configuration file that you want to use, perform these steps. (otherwise, proceed to Step 4):
a. Click Import. The Configuration List dialog box lists all configuration files that are stored in the ANAHOME/ThirdParty directory (where ANAHOME is normally /export/home/ana40).
b. Choose the file and click OK. The Discovery Configuration Settings box is populated with the file information.
c. If you want to make any changes, proceed to Step 4.
Step 4 Configure your basic discovery methods. This is required.
a. Choose Discovery Methods and click Add. At a minimum, you must provide settings for Discovery Methods and SNMP Credentials.
b. Choose a discovery method from the drop-down list. The methods are described in Table 2-2.
Table 2-2 Discovery Methods Used by Network Auto Discovery
Discovery Method
|
Description
|
Neighbor
|
Uses the Cisco Discovery Protocol (CDP) to learn about the device type and SNMP agent address of network elements that are neighbors to the elements being queried.
|
Cluster
|
Processes the command switches in a DSBU cluster. The Cluster method queries the ciscoClusterMIB for all members of the cluster, then adds the members to the list.
|
Credential
|
Queries devices based on the supplied SNMP and enable credentials.
|
PingSweep
|
Pings all devices in a given IP address range. You can also limit the sweep using subnets.
|
PingWithHop
|
Pings all IP addresses in the seed device ipTable, and for the next-hop router of those IP addresses, and adds the members to the list.
|
RouterPeer
|
Queries the OSPF, BGP, or HSRP MIB.
|
RoutingTable
|
Queries and analyzes the routing table of the seed routers to find all subnets and next-hop routers in the network. ANA traverses the routers to find their directly connected subnets and known networks, and next-hop routers as clues. Eventually ANA finds a router for every known subnet.
|
ARP
|
Queries and analyzes the seed routers' ARP table.
|
c. Enter an IP address and (optionally) the hop count, and click OK. The information is added to the Discovery Configuration tree.
d. Add additional discovery methods, as desired.
Step 5 For the discovery methods you configured in Step 4, configure their dependent discovery methods.
Note You must perform this step if you are using the Credential or ARP methods.
To configure dependent methods:
a. Ensure that any dependent methods you plan to choose are already configured, as described in Step 4.
b. Choose Discovery Methods and click Edit. The Discovery Method Settings dialog box opens.
c. Choose the discovery method to which you want to add a dependent method from the Choose a Discovery Method drop-down list.
d. From the Choose Dependent Discovery Methods field, choose dependent methods by checking the appropriate check boxes. (All discovery methods depend on the System method; it drives the entire discovery process.)
Note The Credential method must have at least one dependent method, other than System.
The ARP method must have RoutingTable as a dependent method.
The dependent method PingSweep must have the same seed IP address and hop counts as its parent method.
e. Click Update.
f. Configure additional dependent methods, as desired. (You can configure multiple dependents for any of the methods you configured in Step 4.)
Step 6 Verify your discovery settings in the Discovery Methods and Dependencies area by choosing the configured methods from the drop-down list, and checking the settings. If you chose PingSweep as a dependent method, click the Ping Settings link and verify the submask settings.
Step 7 Specify the SNMP credentials. This is required.
a. Choose SNMP Credentials and click Add.
b. In the SNMP Credentials Settings dialog box, enter the credentials you want the Network Auto Discovery process to use, and click OK.
Step 8 (Optional) Specify the following discovery methods by choosing the method and clicking Add.
Note If both exclude and include filters of the same type are used, the exclude filter is applied first.
Table 2-3 Optional Discovery Settings Used by Network Auto Discovery
Optional Discovery Setting
|
Description
|
Telnet Credentials
|
Includes the device if it matches the supplied Telnet credentials.
|
IP Addresses Included
|
Includes the device if any of its IP addresses match the specified IP address.
|
IP Addresses Excluded
|
Excludes the device if any of its IP addresses match the specified IP address.
|
System OIDs Included
|
Includes the device if the system OID matches the specified OID.
|
System OIDs Excluded
|
Excludes the device if the system OID matches the specified OID.
|
System Locations Included
|
Excludes the device if the sysLocation in MIB2 system table matches the specified system location.
|
System Locations Excluded
|
Excludes the device if the sysLocation in MIB2 system table matches the specified system location.
|
Domain Names Included
|
Includes the device if the domain name resolved by a DNS lookup on the IP address matches the specified domain name.
|
Domain Names Excluded
|
Excludes the device if the domain name resolved by a DNS lookup on the IP address matches the specified domain name.
|
Step 9 To save the configuration file, click Generate Configuration Files. This does not start the discovery process that generates the seed file; it simply saves your criteria. The file is saved on the gateway in ANAHOME/ThirdParty/_Discovery_user_settings.ad.xml (where ANAHOME is normally /export/home/ana40).
Step 10 To schedule the autodiscovery (or perform it immediately), proceed to Performing Network Auto Discovery to Create a Seed File.
Performing Network Auto Discovery to Create a Seed File
Once you have set your discovery settings as described in Creating or Editing a Network Auto Discovery Configuration File, you can perform (or schedule) the network autodiscovery using the following procedure. This creates the seed file that you use to add network elements to ANA.
Step 1 On the Network Auto Discovery page, click Discovery Configuration Schedule.
Step 2 Set your schedule:
•To perform the discovery immediately, choose Immediate from the Run Type drop-down list, and click Schedule Discovery Now. ANA prompts you for confirmation and then provides job information. You can use this information to check on the status of the job using Job Management (see Browsing and Controlling Jobs, page 14-3).
•To perform the discovery at a later time, choose Schedule from the Run Type drop-down list, set your criteria, and click Schedule Discovery Now. If desired, you can set the discovery to run at regular intervals, to add new network elements.
The network autodiscovery process creates a list of the devices in the network in ANAHOME/Main/sfresources/deviceimport.xml (where ANAHOME is normally /export/home/ana40). This file is used to populate the VNE Import page, as described in Importing Network Elements Using the Seed File.
Importing Network Elements Using the Seed File
Once the network autodiscovery process has found the elements in the network according to your discovery criteria, you can specify which devices you want to add to ANA.
Step 1 Go to the Task tab in the Administration perspective and click the Other drawer.
Step 2 Double-click VNE Import. The page is automatically populated with the devices that ANA found during the network autodiscovery process (ANAHOME/Main/sfresources/deviceimport.xml).
Step 3 Choose the devices ANA should use when initiating the import:
a. On the left side of the workspace, right-click the devices and enter the necessary credentials.
b. Use the various Add and Remove buttons to move your seed devices to the right side of the workspace.
Step 4 If desired, you can save your choices and perform the import at a later time. Enter a seed file name in the Enter Seed File Name field. The file is saved in the ANAHOME/Main/sfresources directory. By default, the file is named SeedOutput-date-hhmmss.xml; for example, SeedOutput-Jul02-041442.xml. If you entered MySeedFile as the name, the filename would be MySeedFile-Jul02-041442.xml.
Step 5 Click Run Seed File.
To check on the results of the VNE import, check the log file at ANAHOME/Main/logs/SeedFile.log (where ANAHOME is the installation directory, normally /export/home/ana40).
ANA traverses the network to discover the network elements and use this information to create the model of the network. ANA uses internal algorithms to allocate the VNEs among AVMs, based on the memory and bandwidth required by the various network elements. Calculations are done based on the algorithms; it does not matter if the VNE is not active during the import.
Managing the Gateway
As described in ANA Architecture, page 1-5, the gateway enforces access control and security for all connections and manages client sessions. It maintains a repository of system settings, topological data, and snapshots of active alarms and events. The gateway also maps network resources to the business context, which enables ANA to contain information that is not directly contained in the network (such as VPNs and subscribers) and display it to northbound applications.
To connect to a gateway, download and install the client software on your client machine. Installing the gateway and client software is described in Cisco Active Network Abstraction 4.0 Installation and Setup Guide, along with other basic setup information.
Note Be sure to configure Network Time Protocol (NTP) on the gateway so that all network elements are synchronized to a common time base (UTC).
To get information about configured gateways:
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer. (If you double-click the Servers tree, ANA displays the gateway and units that are configured on the system.)
Step 2 Open the Servers tree and double-click any gateway.
The gateway workspace displays gateway information, such as its status, allocated and used memory, and AVMs configured on the gateway. (See Viewing and Editing AVM Properties, for information on the fields displayed in the table.)
You can also use the cmpctl command to start and stop the gateway and all component processes, or just perform a general check of the system status. The cmpctl command is located in ANAHOME/Main (ANAHOME is the installation directory, normally /export/home/ana40). It takes the following arguments:
start
|
Starts the gateway and component processes
|
stop
|
Stops the gateway and component processes
|
status
|
Displays the status of the gateway and component processes
|
You must be logged in as anauser to use this command. The following is an example:
# cd /export/home/ana40/Main
# ./cmpctl status
.-= Welcome to ana40-2, running Cisco ANA gateway =-.
+ Checking for services integrity:
- Checking if host's time server is up and running [OK]
- Checking if blood test webserver daemon is up and running [OK]
- Checking if secured connectivity daemon is up and running [OK]
- Checking if license server is up and running [OK]
+ Detected AVM99 is up, checking AVMs
- Checking for AVM112's status [OK 0/119]
- Checking for AVM113's status [OK 0/44]
Checking for AVM66's status [OK 0/83]
- Checking for JBoss status [OK]
- Checking for AVM11's status [OK 3/523]
- Checking for AVM55's status [OK 0/388]
- Checking for AVM100's status [OK 0/95]
- Checking for AVM0's status [OK 0/4874]
Note Checking if host's time server is up and running is the only item that can safely
have a status of DOWN. Everything else must display OK.
cmpctl may display any of the following status indictors:
OK
|
Service or AVM is up and running.
|
DOWN
|
Service or AVM is down.
|
LOAD
|
Service or AVM is down, but the system is trying to start (load) it.
|
EVAL
|
License service is running with an evaluation license.
|
For performance information, see System Health and Diagnostics, page 14-34. If you would like to configure gateway high availability, contact ask-ana@cisco.com.
Roles Required to Stop or Start the Gateway
Table 2-4 lists the roles that are required to stop or start the gateway. For more information on roles, see Creating and Managing Users and Scopes, page 14-27.
Table 2-4 Roles Required to Stop or Start the Gateway
Task
|
Role Required
|
Stop or start the gateway using cmpctl
|
Administrator
|
Managing Units (and High Availability)
As described in ANA Architecture, page 1-5, the interconnected fabric of units comprises the lowest level of the ANA architecture. Each unit manages a group of network elements. Units host the autonomous VNEs. This creates a fabric of interconnected VNEs which can intercommunicate with other VNEs (regardless of which unit they are running on). ANA also provides a high ability mechanism to protect the system in case a unit malfunctions. If the unit is configured for high availability, ANA switches over to the redundant standby unit, with no loss of information.
For more information on high availability, see Managing Protection Groups (for Unit High Availability), page 14-9.
See these topics for more information:
• Roles Required to Manage Units
• Adding a New Unit
• Viewing and Editing Unit Properties
• Removing a Unit
Roles Required to Manage Units
Table 2-1 lists the roles that are required to manage units. For more information on roles, see Creating and Managing Users and Scopes, page 14-27.
Table 2-5 Roles Required to Manage Units
Task
|
Role Required
|
Add a unit
|
Administrator
|
View unit properties
|
Administrator
|
Edit unit properties
|
Administrator
|
Find units
|
Administrator
|
Remove units
|
Administrator
|
Adding a New Unit
After you install the ANA software on a unit, you can add it to the ANA fabric. ANA automatically registers the unit in the registry and creates a transport uplink between the unit and the gateway. The units are linked to the gateway in a star topology.
In addition, administrators can enable or disable high availability for a unit. These settings enable the administrator to define to which protection group a unit is assigned, and whether it is enabled for high availability. For more information on high availability, see:
• Configuring Units for High Availability, page 14-12
• High Availability Events, page 14-16
Before You Begin
Before adding a unit, you must install the ANA software on the unit as described in the Cisco Active Network Abstraction 4.0 Installation and Setup Guide.
To add a new unit:
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 From the gateway, right-click New ANA Unit. The New ANA unit dialog box is displayed.
Step 3 Enter the following information:
a. IP Address—Enter the unique IP address of the unit.
b. Enable Unit Protection—Check the check box to enable high availability. This option is enabled by default.
Note It is highly recommended that you do not disable this option. When you define the unit as the "new" standby unit, this option is automatically disabled. For more information about configuring standby units, see Configuring Units for High Availability, page 14-12.
c. Standby Unit—Choose this check box to identify the unit as a standby unit (for high availability).
d. Protection Group—If you are enabling high availability, choose a protection group from the drop-down list of available groups.
Step 4 Click OK. The new unit is displayed in the tree pane and the workspace.
If the new unit is installed and reachable it starts automatically. The active unit is registered with the gateway. Specifically, the command creates the configuration registry for the new unit in the registry. In addition, ANA automatically creates the transport uplinks between the unit and the gateway.
Viewing and Editing Unit Properties
To view or edit a unit's properties:
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 Open the Servers tree and double-click any unit.
Step 3 The unit workspace displays the following information (if the unit is inactive, some of the following information is not be displayed):
•IP Address—The IP address of the unit or gateway.
•Status—The status of the unit or gateway (up or down).
•Up Since—The date and time that the unit or gateway was started.
•Physical Memory—The physical memory of the unit or gateway.
•Allocated Memory—The amount of memory allocated to the unit or gateway. Allocated memory is the sum of all the memory settings for all the AVMs.
•Used Memory—The maximum memory used by the unit or gateway. (Used memory is the sum of the memory used by all the AVMs that are up.)
The Protection Group list displays the currently defined list of customized protection groups.
The workspace also lists the AVMs that are on that unit. For more information about AVM properties, see Viewing and Editing AVM Properties.
Step 4 You can change the assigned unit protection group, as required, by choosing an option from the list.
The AVM HA check box defines whether the watchdog protocol is enabled. This should be selected. (See Managing the Watchdog Protocol, page 14-15.)
Note When you change (disable or enable) the Enable Unit Protection option (high availability), changes are effective after a delay of about 15 minutes.
Step 5 Exit the window. If you made any changes, you are prompted to confirm them.
Removing a Unit
Before You Begin
Delete all the VNEs and unreserved AVMs before deleting a unit; see Deleting an AVM. The reserved AVMs cannot be deleted.
Use this procedure to remove a unit:
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 Open the Servers tree, right-click the unit you want to delete, and choose Delete. A warning message is displayed.
Step 3 Click Yes to proceed or No to cancel the operation. A confirmation message is displayed.
Step 4 Click OK. The unit is deleted and is no longer displayed in the navigation area or workspace.
Managing AVMs
As described in ANA Architecture, page 1-5, AVMs are Java processes that provide the necessary distribution support platform for executing and monitoring multiple VNEs. AVMs and VNEs commonly reside on ANA units but they can also reside on an ANA gateway. The following AVMs are always created, and cannot be edited or deleted:
•AVM 0—High Availability/Switch Virtual Machine. Enables communication between the unit with other units, as well as the gateway.
•AVM 55—Inventory service. Provides modeling information.
•AVM 66—Workflow engine. Defines rules and dependencies to activate business and network processes.
•AVM 99—Management Virtual Machine, which manages the unit and the other AVMs running on the unit (or gateway, if there are no separate units).
•AVM 100—Trap management, which processes alarms and traps.
You can add AVMs to units or directly to a gateway.
The ANA Watchdog Protocol monitors the AVM processes to make sure any AVMs that have died are restarted. For information on the Watchdog Protocol, see Configuring AVMs for High Availability, page 14-15.
See these topics for more information:
• Roles Required to Manage AVMs
• Understanding AVM Status
• Creating an AVM
• Viewing and Editing AVM Properties
• Starting and Stopping an AVM
• Moving an AVM
• Deleting an AVM
Roles Required to Manage AVMs
Table 2-6 lists the roles that are required to manage AVMs. For more information on roles, see Creating and Managing Users and Scopes, page 14-27.
Table 2-6 Roles Required to Manage AVMs
Task
|
Role Required
|
Add an AVM
|
Administrator
|
View AVM properties
|
Administrator
|
Edit AVM properties
|
Administrator
|
Start or stop an AVM
|
Administrator
|
Find an AVM
|
Administrator
|
Move an AVM
|
Administrator
|
Delete an AVM
|
Administrator
|
Understanding AVM Status
The status of AVMs and VNEs is affected by Admin Status and Operational Status. Admin Status comprises the administrative instructions that are sent to the AVM. Operational Status is the actual status of the AVM (for example, Up).
When moving an AVM, its status has a bearing on whether the file is reloaded. If its status is Up, it is reloaded; if its status is down, it is not reloaded. For more information about moving AVMs, see Moving an AVM. For more information about starting and stopping AVMs, see Starting and Stopping an AVM.
An AVM can have only one of the following statuses at a time:
•Up—The file (process) is reachable, and was loaded and started. When a Start command is issued, and no problems, such as an overloaded server, are encountered, the AVM is running (has been loaded and started), and its status is Up.
•Down—The file (process) is reachable, and was stopped. When a Stop command is issued, ANA issues instructions to shut down all the processes. When all the processes have been stopped, the status of the AVM is down.
•Starting Up—When a Start or upload command is issued and, for example, the server cannot run it because it is busy or overloaded, the status of the AVM is Starting Up.
•Shutting Down—When a Stop command is issued, and while the command is being run (some processes may still be running), the status of the AVM is Shutting Down.
The AVM status table describes the status of an AVM depending on the Admin and Operational Status, as displayed in the Status column of the AVMs table. The Admin Status comprises the administrative instructions that are sent to the VNE. The Operational Status is the actual status of the VNE, for example, Up.
Table 2-7 AVM Status
Status
|
Admin Status
|
Operational Status
|
Up
|
Enabled
|
Up
|
Shutting Down
|
Disabled
|
Up
|
Down
|
Disabled
|
Down
|
Starting Up
|
Enabled
|
Down
|
Creating an AVM
ANA lets you define AVMs for ANA units. Every AVM in the ANA fabric is by default managed by the watchdog protocol. ANA enables the administrator to define AVMs for units, and enable or disable the watchdog protocol on the AVM.
Before You Begin
•Decide which unit you want to use to install the AVM. See Creating an AVM.
•The unit must be installed.
•The unit must be connected to the transport network.
•The default AVMs (AVM 0, the switch AVM; AVM 99, the management AVM; AVM 100, the trap management AVM) must be running. For more information on the status of AVMs, see Understanding AVM Status.
•The new AVM must have a unique ID within the unit.
Note AVM ID numbers 0-100 are reserved, and cannot be used. Do not enter a reserved number.
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 Open the Servers tree, right-click the unit, and choose New AVM.
Step 3 Enter the following information:
•ANA Unit—The IP address of the selected unit. The unit does not have to be up to create a new AVM.
•ID—The name of the AVM as defined in ANA, unique to the unit (for example, AVM 18).
Note The AVM numbers 0-100 are reserved and cannot be used. Do not enter a reserved number. If you do, a message is displayed in the New AVM dialog box, informing you that the number is reserved.
•Key—A string that uniquely identifies an AVM in the system, across all units, thus enabling a transparent failover scenario in the system. If you do not enter a key, the default key, ID + time stamp, is used.
•Allocated Memory—The maximum memory allocated to the AVM, in megabytes. The default is 256. (For an AVM managing IOS-XR devices, you will need more memory, such as 1024 MB.)
Note For Cisco IOX network elements, the allocated memory should be 1024 MB.
•Activate on Creation—Loads the AVM into the bootstrap of the unit. This changes the administrative status of the AVM to up and ensures that the AVM is loaded on subsequent restarts of the unit. By default this option is unchecked, and the newly created AVM has an administrative status of down.
•Enable AVM Protection—By default this option is selected, enabling the watchdog protocol on the AVM when high availability is enabled. For more information, see Configuring AVMs for High Availability, page 14-15.
Note It is highly recommended that you do not disable this option if high availability is enabled. If this option is selected or unchecked when the AVM is up, then you need to restart the AVM to enable this change to take affect.
Step 4 Click OK. The new AVM is added to the selected unit, displayed in the workspace, and activated.
Creating the new AVM results in ANA providing the registry information of the new AVM in the specified unit. The AVM can now host VNEs. For more information, see Defining and Creating a VNE.
Viewing and Editing AVM Properties
To view and edit an AVM's properties:
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 Open the Servers tree, and double-click the unit that contains the AVM in which you are interested.
Step 3 Double-click the AVM you want to view or edit. The AVM Properties dialog box is displayed with the details of the selected AVM, including the IP address or key of the unit.
Step 4 The AVM workspace displays the following information:
•AVM Protection Enabled—If checked, the watchdog protocol is enabled on the AVM (available only when high availability is enabled). For more information, see Managing the Watchdog Protocol, page 14-15.
•Status—The VNE status (see Understanding VNE Status).
•Max. Memory—The maximum memory, in megabytes, allocated to the AVM. The default is 256.
•ID—The name of the AVM as defined in ANA, unique to the unit.
Note The AVM numbers 0-100 are reserved and cannot be used. Do not enter a reserved number. If you do, a message is displayed in the New AVM dialog box, informing you that the number is reserved.
•Up Since—When the AVM process was last started.
•Key—A string that uniquely identifies an AVM in the system, across all units, thus enabling a transparent failover scenario in the system. The default key, ID + time stamp, is used.
The workspace also lists the VNEs that are in that AVM. For more information about VNE properties, see Viewing and Editing VNE Properties.
Step 5 Edit the details of the AVM as required.
Note For more information on the other fields displayed in the AVM Properties dialog box, see Creating an AVM.
Step 6 Click OK. The AVM's new properties are displayed in the workspace.
Starting and Stopping an AVM
Note Stopping the AVM stops all the VNEs in the AVM. You should be aware that any change in status of the AVMs may take some time to be applied. For example, when running the Stop command, it may take several minutes before the status changes from Shutting Down to down.
To start or stop an AVM:
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 Open the Servers tree, and double-click the unit that contains the AVM you are interested in.
Step 3 Choose the AVM and right-click Start or Stop.
The AVM is started or stopped, and the appropriate status is displayed in the workspace as follows:
•Starting Up—An AVM is in the process of starting.
•Up—The AVM is running.
•Shutting Down—The AVM is in the process of stopping.
•Down—The AVM is stopped.
Moving an AVM
You can move an entire AVM between units.
Note Reserved AVMs 0-100 cannot be moved.
ANA automatically checks the status of the AVM and VNE before it is moved. This information is maintained in the memory.
If the AVM is up, it is stopped, and then it is moved to the target unit. After the move is completed, the AVM is reloaded, maintaining the status it was in before the move. For example, if it was up before the move, it remains up; if it was down, it remains down.
To move an AVM:
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 Open the Servers tree, and double-click the unit that contains the AVM in which you are interested.
Step 3 Right-click the AVM and choose Move.
The Move To dialog box displays a tree-and-branch representation of the selected ANA server and its units, excluding the unit in which the AVM is currently located. The highest level of the tree displays the ANA server. The branches can be expanded and collapsed to display and hide information.
Step 4 Browse to and choose the unit (branch) where you want to move the AVMs.
Step 5 Click OK. The AVM is moved and now appears beneath the selected unit.
For information about moving VNEs, see Moving One or More VNEs.
Deleting an AVM
If an AVM that you want to delete is running, it is stopped before being removed. This procedure deletes the registry information of the AVM in the specified unit. If there are VNEs running in the AVM, then an error message is displayed, and you cannot delete the AVM.
For more information, see Deleting a VNE.
Note Reserved AVMs 0-100 cannot be deleted.
Before You Begin
Remove all VNEs from the AVM, or the deletion fails. See Deleting a VNE.
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 Open the Servers tree, and double-click the unit that contains the AVM in which you are interested.
Step 3 Right-click the AVM and choose Delete. A warning message is displayed.
Step 4 Click Yes. A confirmation message is displayed and the selected AVM is deleted from the selected unit.
Note Multiple rows can be selected for deletion.
Managing VNEs
As described in ANA Architecture, page 1-5, each Virtual Network Element (VNE) is assigned to manage a single network element instance, and contains a replica of that element. The VNEs maintain a live model of each network element and of the entire network. The information collected by a VNE depends on the VNE type and scheme. The VNE uses whatever southbound management interfaces the network element implements (for example, SNMP or Telnet).
See these topics for more information:
• Roles Required to Manage VNEs
• Understanding VNE Status
• Prerequisites for Adding VNEs to AVMs
• Defining and Creating a VNE
• Viewing and Editing VNE Properties
• Changing a VNE's State
• Moving One or More VNEs
• Deleting a VNE
Roles Required to Manage VNEs
Table 2-6 lists the roles that are required to manage VNEs. For more information on roles, see Creating and Managing Users and Scopes, page 14-27.
Table 2-8 Roles Required to Manage VNEs
Task
|
Role Required
|
Create a VNE
|
Administrator
|
View VNE properties
|
Administrator
|
Edit VNE properties
|
Administrator
|
Change a VNE's state
|
Administrator
|
Find a VNE
|
Administrator
|
Move a VNE
|
Administrator
|
Delete a VNE
|
Administrator
|
Understanding VNE Status
VNE status is affected by the Admin Status and Operational Status. Admin Status results from the administrative instructions that are sent to the VNE. Operational Status is the actual status of the VNE, for example, up. For more information about Admin and Operational Status, see Understanding VNE Status.
When moving a VNE, its status, for example, up or down, has a bearing on whether the VNE is reloaded (up) or not (down). For more information about moving VNEs, see Moving One or More VNEs. For more information about starting and stopping VNEs, see Changing a VNE's State.
A VNE can have only one of the following statuses at a time:
•Up—The VNE (process) is reachable, and was loaded and started. When a Start (command) option is issued, and no problems are encountered, such as an overloaded server, the VNE is running (has been loaded and started), and its status is up.
•Down—The VNE (process) is reachable and was stopped. When a Stop (command) option is issued, ANA issues instructions to shut down all the processes. When all the processes have been stopped, the status of the VNE is down.
•Unreachable—The VNE cannot be managed by ANA and its status is defined as Unreachable. When an option (command) is issued that cannot be run by ANA, the status of the VNE is Unreachable.
•Starting Up—When a Start or upload (command) option is issued, and, for example, when the server cannot run it because it is busy or overloaded, the status of the VNE is Starting Up.
•Shutting Down—When a Stop (command) option is issued, and while the command is being run (some processes may still be running), the status of the VNE is Shutting down.
In addition to the statuses described, the VNE can be placed in Maintenance mode. For example, a VNE's status can be up and in Maintenance mode. Network elements often undergo maintenance operations and planned outages. The ANA platform supports such maintenance operations without affecting the overall functionality of the active network.
While in Maintenance mode (temporary state) a VNE:
•Does not change state on its own, unless you explicitly (manually) switch it back to active state.
•Never polls the network element.
•Is capable of sending alarms, but does not poll the network element. Therefore, service alarms are not supposed to be sent, except for those that are negotiated between adjacent ports; for example, a link-down alarm is still sent.
•Maintains any existing links.
•Does not fail on verification requests.
For more information about Maintenance mode, see Changing a VNE's State.
The VNE status table describes VNE status resulting from the Admin Status and Operational Status, displayed in the Status column of the VNE table. The Admin Status results from the administrative instructions that are sent to the VNE. The Operational Status is the actual status of the VNE, for example, up.
Table 2-9 VNE Status
Status
|
Admin Status
|
Operational Status
|
Up
|
Enabled
|
Up
|
Shutting Down
|
Disabled
|
Up
|
Down
|
Disabled
|
Down
|
Starting Up
|
Enabled
|
Down
|
Unreachable
|
Enabled
|
Unreachable
|
The following examples illustrate Starting Up and Shutting Down status.
•The status is Starting Up if:
–You start the VNE, and the Admin status is up.
–The Operational status is down, and the VNE has not started yet (because the server is busy).
•The status is Shutting Down if:
–The VNE is up and running, and you stop it.
–The Admin status is down, but the process is not immediately terminated.
Prerequisites for Adding VNEs to AVMs
Do the following before you begin adding a VNE to an AVM:
1. If you are concerned about the memory that is consumed by VNEs, contact ask-ana@cisco.com for help with installing VNEs on AVMs in a way that does not adversely impact system performance.
2. Decide on the VNE type you want to use. See Choosing a VNE Type.
3. Decide on the VNE scheme you want use. This determines the type of information that is modeled in ANA. See Choosing a VNE Scheme.
4. Make sure you have the information required for the protocol you use to obtain the network element information. See Gathering the Required Protocol Information for a Network Element.
Basic Network Element Information Required to Add a VNE
Make sure you have the following network element information before you add the VNE:
•Network element IP address
•SNMP version that is supported, if any
Choosing a VNE Type
When you add the VNE, you must choose a VNE type from a drop-down list. The types you can choose from are described in Table 2-10.
Table 2-10 VNE Types
If your network element fits these criteria:
|
Use this VNE type:
|
and ANA does the following:
|
SNMP is enabled on the network element.
|
Auto Detect
|
Use SNMP to gather all available inventory information.
|
SNMP is enabled on the network element and:
•ANA does not support the network element, or
•ANA supports the network element but you only want basic information to be modeled.
|
Generic SNMP
|
Use SNMP to gather the most basic inventory information that is normally provided by all network elements.
|
ICMP is enabled on the network element and:
•ANA does not support the network element, or
•ANA supports the network element but you only want basic information to be modeled.
|
ICMP
|
Use ICMP to gather the most basic inventory information that is normally provided by all network elements.
|
Choosing a VNE Scheme
The information collected by a VNE and populated in its model depends on the scheme you choose when adding the VNE to an AVM. ANA supports two schemes: Foundation and MPLSIOXSR. The scheme you should use depends on the type of network element you are adding, as shown in Table 2-10.
Table 2-11 Choosing a VNE Scheme
Foundation
|
You are adding a Cisco IOS network element, or a non-Cisco network element.
|
MPLSIOSXR
|
You are adding a Cisco IOS XR or Cisco IOX network element.
|
Gathering the Required Protocol Information for a Network Element
When you add a VNE, you are prompted to enter the information listed in Table 2-12.
Note For Cisco IOS-XR elements, you must know the Telnet login sequence.
Table 2-12 Required Protocol Information
If you use this protocol:
|
Verify the following:
|
SNMP
|
•SNMP is running on the network element
•The version that is supported (V1, V2, V3)
•For SNMPV1/V2, you have the SNMP read and write community strings
•For SNMP V3, you have the authentication and/or privacy config
|
Telnet
|
•Telnet is supported on the network element
•The type of connection (port number and socket)
•You have the Telnet login sequence: username, password, and prompt (this information is critical for Cisco IOS-XR network elements)
|
SSH
|
•SSH is supported on the network element
•The version that is supported (V1 or V2)
•You have the SSH username and password and any other configuration information (cipher, authentication, key exchange (V2), MAC (V2))
|
Defining and Creating a VNE
Each VNE corresponds to a network element and should only be added to the system once. As the VNE loads, ANA starts investigating the network element and automatically builds a live model of it, including its physical and logical inventory, its configuration, and its status. ANA also creates the registry information of the new VNE in the unit. The newly created VNE has an administrative status of down, and uses the default community strings and polling rates. The VNE inherits these properties from the configuration record that corresponds to the network element type.
These topics describe the steps you must perform to create a VNE:
Note Before you add the VNE, be sure you meet the required prerequisites. See Prerequisites for Adding VNEs to AVMs.
• Entering VNE General Information
• Entering VNE SNMP Information
• Entering VNE Telnet/SSH Information
• Entering VNE ICMP Information
• Entering VNE Polling Information
A VNE must be loaded into the bootstrap of the unit before it starts monitoring its underlying network element. This changes the administrative status of the VNE to up, and ensures that the VNE is loaded on subsequent restarts of the unit. Loading the VNE also starts the VNE immediately. For more information about the status of VNEs, see Understanding VNE Status.
Note A new VNE cannot be added to the reserved AVMs 0-100.
You can define and manage SNMP, Telnet/SHH, ICMP, and polling information for the appropriate VNEs in the New VNE dialog box. If desired, you can create VNEs that perform reachability testing, through ICMP only. Do this by creating the VNE, choosing ICMP for the VNE type, and defining the details in the ICMP area.
Before You Begin
Make sure you have all required information. See Prerequisites for Adding VNEs to AVMs.
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 Open the Servers tree, double-click the AVM to which you want to add the VNE, and choose New VNE. The New VNE dialog box opens.
Step 3 Enter the desired information in the following tabs:
Note At a minimum, you must complete the VNE name and IP address in the General tab in order to create a new VNE. For Cisco IOS-XR network elements, you must know the complete Telnet login sequence.
•General—Manage VNE information in the connected ANA (mandatory name and IP fields). See Entering VNE General Information.
•SNMP—Support polling and network element access using SNMP v1, SNMP v2, and SNMP v3. See Entering VNE SNMP Information.
•Telnet/SSH—Choose Telnet or SSH for network element access and configure the login sequence. See Entering VNE Telnet/SSH Information.
•ICMP—Verify that network elements are reachable by sending repetitive ICMP request packets, and testing reachability by defining the polling rate. See Entering VNE ICMP Information.
•Polling—Associate a VNE in the ANA with a polling group, or define an instance. See Entering VNE Polling Information.
Note The OK button in the New VNE dialog box is enabled only when you enter the VNE name and IP address (mandatory fields) in the General tab.
Step 4 Click OK. The VNE is loaded into the bootstrap of its unit, and ANA starts investigating the network element. ANA builds a live model of the network element, including its physical and logical inventory, its configuration, and its status. ANA also creates the registry information of the new VNE in the unit. After a few minutes, the VNE status changes to up.
Entering VNE General Information
The General tab lets you manage VNE information in the connected ANA.
To enter VNE general information:
Step 1 Enter this information in the Identification area:
•VNE Name—The name of the VNE that is used as a unique key in ANA. It is also used for VNE manipulation commands.
•IP Address—The IP address of the network element.
•Type—The VNE type, selected from the list:
–Auto Detect—Automatically detects the network element type and loads the relevant VNE.
Note SNMP cannot be disabled if the Auto Detect option is selected.
See Entering VNE SNMP Information.
–Generic SNMP—Loads a generic VNE. For more information about defining a generic VNE, see Viewing and Editing VNE Properties.
–ICMP—Uses this ICMP-based reachability test to validate communication with the managed network element by continuously sending ICMP packets. When this option is selected, the ICMP tab is enabled (the SNMP, Telnet/SSH, and Polling tabs are disabled).
•Scheme—Defines the VNE modeling components investigated during the discovery process. This enables the administrator to define different behavior for some network elements; for example, some network elements poll only with SNMP, and other network elements poll with Telnet. Soft properties and activation scripts are also attached to a specific scheme. By default, the VNE inherits the VNE scheme from the default scheme. Where more than one scheme exists in the network, the VNE loads the selected scheme.
Note For GSR, Cisco IOS-XR, and Cisco IOX network elements, use the MPLSIOSXR scheme.
Step 2 Enter this information in the Initial State area:
•State—The initial state of the VNE:
Note Normally you should set the state to Start. You may not want to do this if you want to verify the VNE configuration, or if you know the VNE is very complex and might need extra processing to complete the loading procedure.
–Stop—Do not load the VNE (default).
–Start—Load the VNE and start collecting data.
–Maintenance—Start the VNE but move it to Maintenance mode.
Step 3 Enter this information in the Location area:
•ANA Unit—The IP address of the unit that hosts the VNE's AVM.
•AVM—The AVM on the unit that hosts the VNE.
Entering VNE SNMP Information
The SNMP tab lets you support polling and network element access using SNMP Version 1, Version 2, and Version 3.
To enter VNE SNMP information:
Step 1 Enter this information at the top of the tab:
•Enable SNMP—Check this option to enable the SNMP communication protocol so that the user can work with it.
Note A VNE can be SNMP enabled or disabled at any time; however, when the Auto Detect option is selected in the General tab, it cannot be disabled. (For more information, see Entering VNE General Information).
•SNMP V1—Choose SNMP Version 1
•SNMP V2—Choose SNMP Version 2
•SNMP V3—Choose SNMP Version 3
Note The SNMP V3 settings area is only enabled when SNMP V3 is selected.
Step 2 Enter this information in the SNMP V1/V2 Settings areas:
•Read—The SNMP read community status, public (default) or private, as defined by the user.
•Write—The SNMP write community status, public or private (default), as defined by the user.
Step 3 Enter this information in the SNMP V3 settings area. These settings are enabled only when SNMP V3 is selected:
•Authentication—Choose one of the following:
–No—No authentication is required (default)
–md5
–sha
If MD5 or SHA is selected, enter the required information in the following fields:
–User
–Password
•Encryption—Choose one of the following:
–No—No encryption is required (default)
–DES (default for SNMP v3)
•If DES is selected, enter the required information in the following field:
–Password
Note If you enter the wrong credential information, the VNE is not be managed. Make your changes, and restart the AVM (see Starting and Stopping an AVM).
Entering VNE Telnet/SSH Information
The Telnet/SSH tab lets you define the Telnet command sequence and support SSH for network element access (reachability) and investigation.
To enter VNE Telnet/SSH information:
Step 1 Enter the port and protocol information at the top of the New VNE dialog box:
•Protocol—Choose one of the following from the drop-down list:
–Telnet—When Telnet is selected the port field automatically displays 23 (Telnet is the default).
–SSHv1—When SSHv1 is selected the port field automatically displays 22, and an SSHv1 information field appears at the bottom of the dialog box.
–SSHv2—When SSHv2 is selected the port field automatically displays 22, and an SSHv2 information field appears at the bottom of the dialog box.
•Port—When Telnet is selected this field automatically displays 23. When SSHv1 or SSHv2 is selected this field automatically displays 22. You can edit the port number displayed.
Step 2 To enable the communication protocol, do the following:
•Enable—Check this check box to enable the Telnet/SSH1 communication protocol to be used by the VNE to investigate the reachability of the network element. Checking this box activates the Prompt and Run fields, and the Add and Remove buttons.
Note A VNE can be Telnet/SSH enabled or disabled at any time.
•Prompt—Enter the expected Telnet/SSH prompt.
•Run—Enter the Telnet/SSH string to send to the network element (when the expected prompt is detected), and click Add. The Prompt and Run information is added to the table.
Use the Add, Remove, Up, and Down buttons to finalize your entries.
Note The Telnet sequence (the order of the commands) must end with a line that includes only the prompt field.
Step 3 If you selected the SSHv1 or SSHv2 protocols, enter the required credential information.
Entering VNE ICMP Information
The ICMP lets you enable repetitive transmission of packets to a network element for verification that the network element is reachable. You can define the polling rate in seconds for the VNE.
To enter VNE ICMP information:
Step 1 Check the Enable check box to enable the use of the ICMP communication protocol to verify that the network element is reachable.
Note The ICMP enable option can be enabled or disabled at any time.
Step 2 If ICMP polling is enabled, enter an ICMP polling rate (in seconds) in the Polling Rate field.
Entering VNE Polling Information
The Polling tab enables the administrator to associate a VNE with a previously created polling group, or customize polling intervals for a VNE.
Caution Changing polling rates may result in excess traffic and cause the network element to crash. Although fast polling rates ensure high data accuracy, they also generate high CPU utilization and heavy network traffic.
In addition, you can configure a polling interval for a class of network elements; for example, for all Cisco routers.
To enter VNE polling information:
Step 1 Enter this information in the Polling Method area:
•Group—Use the polling rates from the polling group selected from the list (by default, from the default polling group). When you choose Group, the Polling Intervals and Topology areas are disabled.
For more information about creating customized polling groups, see Creating or Customizing a Polling Group, page 14-8.
•Instance—Change the polling rates of any one of the built-in polling intervals currently displayed in the dialog box tab. When you choose Instance, the Polling Intervals and Topology areas are disabled.
Note A polling rate that is not changed inherits its settings from the group specified in the Group drop-down list.
Step 2 If you selected Instance:
a. Enter your changes in the Polling Intervals area:
–Status—Sets the polling rate for status-related information, such as network element status (up or down), port status, admin status, and so on. The information is related to the operational and administrative status of the network element. The default setting is 180 seconds.
–Configuration—Sets the polling rate for configuration-related information, such as VC tables, scrambling, and so on. The default setting is 900 seconds (15 minutes).
–System—Sets the polling rate for system-related information, such as network element name, network element location, and so on. The default setting is 86,400 seconds (24 hours).
b. Enter the following information in the Topology area:
–Layer 1—Sets the polling rate of the topology process as an interval for the Layer 1 counter. This is an ongoing process. The default setting is 30 seconds.
–Layer 2—Sets the polling rate of the topology process as an interval for the Layer 2 counter. This process is available on demand. The default setting is 30 seconds.
Viewing and Editing VNE Properties
You can view and edit the properties of a VNE, such as the status and Telnet settings. Use this procedure to view and edit a VNE's properties.
Note After making your edits, you must restart the AVM. If you do not want to restart the AVM, you must delete the VNE and recreate it.
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 Open the Servers tree, and double-click the AVM that contains the VNE in which you are interested. All VNEs in that AVM are displayed in a table in the workspace.
Step 3 Do one of the following:
•To view the VNE details, double-click the VNE in which you are interested. The VNE Properties dialog box is displayed with the details of the selected VNE.
•To edit the VNE, right-click the VNE and choose Edit.
For more details about the fields displayed in the VNE Properties dialog box, see
Defining and Creating a VNE. In addition to the fields displayed when adding a new VNE, the following fields and buttons are displayed:
•VNE Status—Up, Down, Shutting Down, Starting Up, or Unreachable. For more information on the status of VNEs, see Understanding VNE Status.
•Start—Start the VNE if it has been stopped or is in Maintenance mode. See Changing a VNE's State.
•Stop—Stop the VNE if it is running or is in Maintenance mode.
•Maintenance—Move the VNE to Maintenance mode. If this is done when the VNE has been stopped, it has no effect on the VNE.
•ANA Unit—The current unit that hosts the VNE.
•AVM—The current AVM number, which changes according to the unit selected to show one of the available AVMs on that unit.
Step 4 Edit the details of the VNE as required.
Step 5 Click Apply.
Step 6 Click OK. The VNE's properties are edited.
Step 7 Restart the AVM to enable the changes to take effect.
Changing a VNE's State
You can start or stop a VNE, or move it to Maintenance mode. Starting the VNE adds if to the server bootstrap. Stopping it removes it from the server bootstrap.
During normal operation, network elements often undergo maintenance operations and planned outages such as software upgrades, hardware modifications, cold reboots, and so on. The ANA platform supports such maintenance operations without affecting the overall functionality of the active network. Neighboring VNEs do not generate alarms that are related to links to or from the maintained VNE.
While in maintenance state (temporary state) a VNE:
•Does not change state on its own unless the user explicitly (manually) switches the VNE back to active state.
•Never polls the network element.
•Is capable of sending alarms but does not poll the network element. Therefore, service alarms are not supposed to be sent except for those that are negotiated between adjacent ports. For example, a link-down alarm is still sent.
•Maintains any existing links.
•Does not fail on verification requests.
The VNE blocks all provisioning flows that run through it. A network element in maintenance state can be disconnected and restarted, and this does not result in link-down alarms. Upon restart, the VNE receives only persistent information and returns to its latest known configuration. The topology links are renewed automatically.
To change the VNE's state:
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 Open the Servers tree, and double-click the AVM that contains the VNE in which you are interested. All VNEs in that AVM are displayed in a table in the workspace.
Step 3 Choose the VNE and right-click Start, Stop, or Maintenance.
Step 4 The state of the VNE changes based on your selection:
•If the VNE is started a confirmation message is displayed. Click OK. An up status is eventually displayed in the VNE properties table. You may see a Starting Up status, when, for example, the Server is overloaded, or the VNE is still being loaded.
•If the VNE is stopped a confirmation message is displayed. Click OK. A down status is eventually displayed in the VNE properties table. You may see a Shutting Down status while various processes are closing down.
•If the VNE is moved to Maintenance mode a confirmation message is displayed. Click OK. A Maintenance status is displayed in the VNE properties table.
Moving One or More VNEs
You can move single and multiple VNEs between AVMs. The VNEs that are moved are unloaded from the old unit, and after they are reloaded on the new unit, their original status is maintained.
To move a single VNE or multiple VNEs:
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 Open the Servers tree, and double-click the AVM that contains the VNE in which you are interested. All VNEs in that AVM are displayed in a table in the workspace.
Step 3 Choose one or more VNEs and right-click Move VNEs.
The Move To dialog box displays a tree-and-branch representation of the selected ANA server, its units, and AVMs, excluding the AVM in which the VNE is currently located. The highest level of the tree displays the ANA server. The branches can be expanded and collapsed to display and hide information.
Step 4 In the Move To dialog box, browse to and choose the AVM (branch) where you want to move the VNEs.
Step 5 Click OK. The VNE is moved to its new location, and now appears beneath the selected AVM (branch) in the VNE properties table.
Deleting a VNE
You can delete a VNE from an AVM (and its unit). When you delete a VNE, ANA stops the VNE and deletes all VNE references from the system and golden source, which includes the registry information of the VNE in the specified unit. A VNE that has been removed no longer appears in any future system reports. If the VNE has any static links, you must remove them before removing the VNE (dynamic links are automatically removed).
Since all VNE information is deleted, adding the VNE again requires you to enter all the VNE information.
Before You Begin
If the VNE you plan to delete has any static links, remove them. Dynamic links are automatically removed.
Step 1 Go to the Object tab in the Administration perspective and click the ANA Servers drawer.
Step 2 Open the Servers tree, and double-click the AVM that contains the VNE in which you are interested. All VNEs in that AVM are displayed in a table in the workspace.
Step 3 Choose the VNE and right-click Delete. A warning message is displayed.
Step 4 Click Yes. A confirmation message is displayed.
Step 5 Click OK. The selected VNE is deleted from the AVM, and is no longer displayed in the VNE properties table.
