User Guide for Campus Manager 5.2 (with LMS 3.2)
Chapter 15 Troubleshooting and FAQs
Downloads: This chapterpdf (PDF - 463.0KB) The complete bookPDF (PDF - 8.48MB) | Feedback

Troubleshooting and FAQs

Table Of Contents

Troubleshooting and FAQs

Troubleshooting

User Tracking

Topology Services

Troubleshooting Time Domain Reflectometry Reports

VLAN Port Assignment

FAQs

Device Management

User Tracking

Data Extraction Engine

Virtual Network Manager


Troubleshooting and FAQs


This chapter is frequently updated with latest technical FAQs and troubleshooting tips.

This section contains:

Troubleshooting

FAQs

Troubleshooting

This section includes the troubleshooting tips for the following features in Campus Manager Application:

User Tracking

Topology Services

User Tracking

Use the information in Table 15-1 to troubleshoot the User Tracking application.

Table 15-1 Troubleshooting User Tracking 

Symptom
Probable Cause
Possible Solution

User Tracking cannot discover any users or hosts

or

User Tracking cannot display any IP phones.

There may not be information in the Campus Manager database.

The device might not be part of DCR and you must run Device Discovery and Data Collection.

For more details, see Understanding Campus Manager Administration.

User Tracking cannot discover certain users or hosts.

The Campus Manager server might not have discovered one or more devices to which users and hosts are connected.

1. Check the CiscoWorks topology for the missing devices

2. Ensure that CDP and SNMP are enabled on the devices, rediscover these devices,

3. Verify that they appear on the topology view.

User Tracking cannot discover certain IP phones.

The Campus Manager server might not have discovered the specific Media Convergence Server (MCS) that runs the instance of Cisco CallManager to which the IP phones are registered.

1. Check the CiscoWorks topology for the missing MCS that runs the instance of Cisco CallManager to which the phones are registered.

2. Ensure that Cisco CallManager is shown as a service running on the MCS and is discovered by the Campus Manager Server.

3. Rediscover all IP phones.

User Tracking table does not contain device name, IP address, and subnet information for some hosts.

User Tracking cannot find the most recent network information.

Network changes are not currently reflected in ARP information (routers) or bridge tables (switches).

User Tracking does not perform Ping Sweep on large subnets; for example, subnets containing Class A and B addresses.

Hence, ARP cache might not have some IP addresses and the User Tracking may not display the IP addresses.

In larger subnets, the ping process leads to numerous ping responses that might increase the traffic on your network and result in extensive use of network resources.

Enable Ping Sweeps when User Tracking performs Discovery. Ping Sweeps are enabled by default.

To perform Ping Sweep on larger subnets, you can either:

Configure a higher value for the ARP cache time-out on the routers.

To configure the value, you must use the arp time-out interface configuration command on devices running Cisco IOS.

Or

Use any external software, which will enable you to ping the host IP addresses.

This will ensure that when you run User Tracking Acquisition, the ARP cache of the router contains the IP addresses.

You have:

Made changes to the network.

Run User Tracking Major Acquisition.

The changes do not appear in the User Tracking display.

A complete Device Discovery process has not run since you added your changes.

User Tracking Major Acquisition is not a full network discovery. The process discovers only the user and host data in your network.

Changes that you make to your network might not appear after a User Tracking Major Acquisition.

1. Run Device Discovery from Common Services.

2. Run a complete Data collection.

3. Generate a new report after data collection is complete to see the changes.


Topology Services

To troubleshoot Topology Services, see Troubleshooting Time Domain Reflectometry Reports

Troubleshooting Time Domain Reflectometry Reports

Time Domain Reflectometry (TDR) report does not display any entries when you run TDR Cable Diagnostic Test on devices that support TDR.

This occurs even if Campus Manager supports the CISCO-CABLE-DIAG-MIB, and if the read and write community strings are correct. For more details on running TDR test on devices, see Running TDR Test for a Link.

When the TDR test fails, the following error message appears:

Unable to get TDR related information from one or more devices.
Probable Cause
One or more devices:
-May not support TDR
-May be Unreachable
-have incorrect read/write credentials in DCR
Recommended Action
Do the following:
1. Enter correct credentials in DCR.
2. Initiate Data Collection for the devices.
3. Run TDR report.

In the log file for Data Collection, you can find the error message:

ERROR: Unable to get Running Status of TDR Test.
Probable Cause: Time Taken to complete the TDR test in the device takes long time/Mib 
support is not available/ Device is not SNMP reachable
Action : Add the property TDRTestTimeout and set value for the property in 
ANIServer.properties to value greater than 7000 and restart ANIServer process.Check SNMP 
reachability/Check TDR Support on the device

To view the log file for Data Collection, go to:

Solaris: /var/adm/CSCOpx/log/ani.log

Windows: NMSROOT/log/ani.log, where ani.log is the default filename for the log file for Data Collection.

Probable Cause

When you run TDR Cable Diagnostic Test from Campus Manager, the report generation might take a long time. The default time value set for generating the report is seven seconds. Hence, when TDR test takes more than seven seconds, the process times out and Campus Manager does not generate the report.

Possible Solution

When the TDR report does not generate data, you must modify the ANIServer.properties file. To modify the file, you must:


Step 1 Stop the ANI server.

Step 2 Enter pdterm ANIServer at the command line to stop the ANI server.

Step 3 Go to NMSROOT/campus/etc/cwsi/ANIServer.properties.

Step 4 Enter TDRTest.Timeout=greater that 7000 property in the ANIServer.properties file.

For example, the value can be TDRTest.Timeout=10000.

Step 5 Start the ANI server.

Step 6 Enter pdexec ANIServer at the command line to start the ANI server.

VLAN Port Assignment

Use the information in the Table 15-2 to troubleshoot the VLAN Port Assignment application.

Table 15-2 Troubleshooting VLAN Port Assignment

Symptom
Probable Cause
Possible Solution

VLAN Port Assignment starts, but shows an error message.

Server process is not running.

Confirm that the Campus Database engine and the Campus Server are running.

VTP Domain drop-down list box is empty and the following error message appears:

Discovery seed not defined for ANI Server

A seed device is not specified for the ANI Server.

Add a seed device. See ANI Server online help for more information about adding a seed device.

See the User Guide for CiscoWorks Common Services or the Online help for Campus Manager 5.0 for more information about adding a seed device.

VTP Domain drop-down list box is blank and the following message appears:

ANI is still in the discovery process. Please wait.

The initial Device Discovery is not complete.

Wait for the ANI status bar to display Idle.

The message Operation Failure appears when you try to move a port.

The operation failed for various reasons.

Click Details to display the cause of the failure.


FAQs

This section includes the frequently asked questions and answers for the following features:

The queries are available for the following features:

Device Management

User Tracking

Data Extraction Engine

Virtual Network Manager

Device Management

The following are the frequently asked questions about Device Management:

Q. Some of the devices in DCR are not managed in Campus Manager, but the group to which it belongs to, is included in the Auto mode settings. What could be the reason?

A. Check whether these devices are manually excluded from Campus Manager in the Manually Excluded Devices report. If the device you are looking for is available here, then it will not be managed in Campus Manager unless it is manually included.

Q. When I exclude a device, will it get deleted immediately or during next Data Collection?

A. If you are manually excluding a device, it will be immediately deleted from Campus Manager and it will not be managed in further Data Collections.

Q. What is the difference between manually excluding a device and deleting a device from Topology Services screen?

A. Manually Excluding a Device: If you manually exclude a device, it gets deleted from Campus. Even if you do Data Collection from the neighboring device, it does not get managed in Campus Manager.

Deleting a device from Topology Services screen: If you delete a device from Topology services, and run Data Collection on its neighbor device, the device becomes managed in Campus Manager.

Q. I have manually included a device. How do I exclude it?

A. Select and exclude that device from the device selector in the Exclude Devices page. Alternatively, you can exclude that device from the Manually Included Devices report.

Q. I have manually excluded a device. How do I include it?

A. Select and include that device from the device selector in the Include Devices page. Alternatively, you can include that device from Manually Excluded Devices report.

Q. .When I manually include a device, will it be managed immediately in Campus Manager?

A. No. Unless you run Data collection, this will not get managed in Campus Manager.

Q. I have both Auto mode and Manual mode enabled. Which one will take higher priority?

A. Manual mode always gets higher priority.

Q. I have manually added some devices and started Data collection for all devices. For which devices will Data collection run?

A. Data collection will run for manually added devices and the devices that are already managed in Campus Manager.

Q. I have added n devices in DCR and in that I want to manage only subset of devices in Campus Manager. Is there any way to do this?

A. Either:

Manually include those devices and run Data collection.

Or

Create a group in Common Services that includes these IP addresses, include the group in Auto mode settings in Campus Manager and run Data Collection.

Q. How to make Campus Manager identify the HSRP devices and perform data collection?

A. To make Campus Manager identify the HSRP devices and perform data collection, do the following:


Step 1 Add the virtual IP address of the HSRP router as the value for the property "HsrpVitrualIPAddress" in the ANIServer.properties file

Since there is no UI to specify the virtual IP address, you need to enter it in the ANIServer.properties file.

When you need to specify multiple virtual IP addresses, separate them with a colon.

For example:

HsrpVitrualIPAddress=10.77.210.20:10.77.211.21

Step 2 Restart the ANIServer for the changes to take effect.


Q. I have an office with 300 remote branches each with a Cisco router. The routers are connected to the head office over an SP infrastructure and IPSec is used to encrypt the traffic between the remote branches and the head office. How do I manage the devices in the remote network using Campus Manager?

A. If you want to discover and manage the devices in the remote network, add these devices to DCR. For managing them in Campus Manager, see Device Management.

User Tracking

Q. Why are outdated entries appearing in my User Tracking table?

A. Outdated entries result when:

A user or host is assigned to new VLAN/port/VTP domain.

A power failure occurred.

A workstation has been switched off or removed from the network.

User Tracking does not automatically delete outdated end-user host entries. To delete these entries:

Manually delete selected entries.

Or

Configure delete interval for purging old records more than the given number of days.

Q. How does User Tracking acquisition process differ from that of the Campus Manager Server?

A. User Tracking is a Campus Manager client application. The Campus Manager Server provides several types of global discoveries, including:

Device and physical topology acquisition, resulting in baseline network information such as device identity, module and port information, and physical topology. This type of acquisition is required for logical, user, and path acquisition.

User acquisition, resulting in information about users and hosts on the network.

The Campus Manager Server stores this information in the database. User Tracking discovers the host and user information in the Campus Manager server database, correlates this information, and displays it in the User Tracking Reports.

For more information about the various acquisition processes, see Various Acquisitions in User Tracking.

Q. How does User Tracking user and host acquisition process work?

A. Before collecting user and host information, Campus Manager must complete Data Collection. After the completion of Data Collection User Tracking performs steps described in Table 15-3.

Table 15-3 User Tracking User and Host Acquisition Process 

Process
Description

Performs Ping Sweeps

Pings all IP addresses on all known subnets, if you have Ping Sweeps enabled (the default).

This process updates the switch and router tables before User Tracking reads those tables. This ensures that User Tracking displays the most recent information about users and hosts.

Obtains MAC addresses from switches

Reads the switch's bridge forwarding table.

The bridge forwarding table provides the MAC addresses of end stations, and maps these MAC addresses to the switch port on which each workstation resides.

Obtains IP and MAC addresses from routers

Reads the Address Resolution Protocol (ARP) table in routers to obtain the IP and corresponding MAC addresses.

Obtains hostnames

Performs a Domain Name Service (DNS) lookup to obtain the hostname for every IP address.

Obtains usernames

Attempts to locate the users currently logged in to the hosts and tries to obtain their username or login ID.

Records discovered information

Records the discovered information in the Campus Manager database.


Q. Why is User Tracking not performing Ping Sweeps on some subnets?

A. The criterion for whether or not User Tracking performs Ping Sweeps on a subnet is the number of hosts in the subnet:

You must check if you have excluded the subnets from Ping Sweep.

If a subnet has 256 or fewer hosts, User Tracking performs Ping Sweeps on that subnet. User Tracking does not perform Ping Sweeps on the subnets, which have more than 256 hosts.

If Ping Sweeps are not performed, User Tracking still obtains information from the router and switch mapping tables during a discovery. For more details on Ping Sweep, see Notes on Ping Sweep Option.

Q. How long does User Tracking maintain data?

A. It depends on the delete interval you have set. For more details, see Modifying Delete Interval.

Q. Does User Tracking discover users and hosts connected to non-Cisco Discovery Protocol (CDP) devices?

A. Campus Manager does not manage non-CDP devices. Hence User Tracking will not discover users and hosts in the network connected to non-CDP devices.

Q. Where does User Tracking log errors?

A. User Tracking major acquisition errors are logged in the User Tracking error log. Data Collection errors are logged in the respective log file. The log files are located at
Solaris : /var/adm/CSCOpx/log
Windows: NMSROOT/log
Where NMSROOT is the directory where you have installed CiscoWorks.

Data Extraction Engine

Following is a list of frequently asked questions about Campus Manager DEE:

Q. Where does DEE collect the Discrepancy information from?

A. DEE collects the running Discrepancy data from the latest configuration in Campus Manager server.

Q. What is an XSD file?

A. XSD file is an XML based alternative to Document Type Definition (DTD). It is based on XML schema which describes the structure of an XML document. An XML schema defines the valid building blocks of an XML document, similar to a DTD.

An XML Schema:

Defines elements that can appear in a document.

Defines attributes that can appear in a document.

Defines which elements are child elements.

Defines the order of child elements.

Defines the number of child elements.

Defines whether an element is empty or can include text.

Defines data types for elements and attributes.

Defines default and fixed values for elements and attributes.

For more information, see W3Schools Online Web Tutorials site.

Q. How can I make use of the servlet interface?

A. You must write customized scripts that can connect to the servlet. The arguments and options have to be specified in XML format. Details can be found in Using Servlet to Export Data from Campus Manager.

Q. How can I get user tracking and Layer 2 topology data for a particular set of switches or subnets managed by separate Campus Manager servers?

A. No. This feature is not supported.

Q. I do not want to provide the password in the command line as it is insecure. Is there a way to provide it in a secure way?

A. Yes. You can create an environment variable CMEXPORTFILE, which points to a text file that contains the userid and password list separated by a blank space.

Q. Where will the XML output file be stored?

A. The default locations for storing the XML output files are:

PX_DATADIR/cmexport/ut/timestamput.xml

PX_DATADIR/cmexport/l2topology/timestampL2Topology.xml

PX_DATADIR/cmexport/Discrepancy/timestampDiscrepancy.xml

You can use the -f option to specify an alternative location.

Q. Why am I getting a parse error when trying to parse some of the output files?

A. A few classes in Optical switches contain special characters with ASCII code higher than 160. Most of the XML parsers do not support these characters and hence fail to parse them.

To overcome this, you have to manually search for those elements with special characters and append CDATA as given in the example below:

If there is an element

<checksum> ¢Úo </checksum>

Change it to:

<checksum> <![CDATA[¢Úo ]]> </checksum>

Virtual Network Manager

Q. What is Virtual Network Manager ?

A. Virtual Network Manager is an application that allows you to pre-provision, provision and monitor Virtual Routing and Forwarding-Lite (VRF-Lite) technology on an enterprise network.

Q. What is Network Virtualization?

A. Virtualization deals with extending a traditional IP routing to a technology that helps companies utilize network resources more effectively and efficiently. Using virtualization, a single physical network can be logically segmented into many logical networks. The virtualization technology supports multiple virtual routing instances of a routing table to exist within a single routing device and work simultaneously.

Q. What is VRF-Lite ?

A. Virtual Routing and Forwarding - Lite (VRF - Lite) is the one of the simplest form of implementing virtualization technology in an Enterprise network. A Virtual Routing and Forwarding is defined as VPN routing/forwarding instance. A VRF consists of an IP Routing table, a derived forwarding table, a set of interfaces that use the forwarding table and set of routing protocols that determine what goes into the forwarding table.

Q. What are the pre-requisites to manage a device using Virtual Network Manager?

A. The pre-requisites to manage a device in Virtual Network Manager are:

1. The device must be managed by Campus Manager.

2. The device must either be L2/L3 or L3 device

3. The devices failing to satisfy pre-requisite # 1 or #2, are not displayed in Virtual Network Manager.

The device must have the necessary hardware support. For more information on hardware support, see http://www.cisco.com/en/US/partner/products/sw/cscowork/ps563/products_device_support_tables_list.html.

If the device hardware is not supported then the device will be classified as Other devices

4. If a device does not support MPLS VPN MIB, it is classified as a capable device.

5. VTP Server must be support MPLS VPN MIB. If the VTP Server does not support MPLS VPN MIB, VNM will not manage VTP Clients.

Q. The device must be managed by RME to exercise all the functionality of VNM. The desired device is not listed in the device selector for the VNM configuration workflows. What is the reason for a device not listed in the device selector?

A. A device is not listed in the device selector due to the following reasons:

All VNM Configuration workflows like Create, Edit, Extend, Delete VRF and Edge VLAN Configuration.

A device will not be listed in the Device Selector, if a device does not satisfy the pre-requisites as mentioned in the Pre-Requisites to manage devices using VNM.

If VNM Configuration workflow is either Edit VRF, or Delete VRF or Edge VLAN Configuration then a device will not be listed in the Device Selector, if a device is not participating in the selected VRF.

In the Readiness Report, a device listed as a supported device may be because it is not managed by RME. You can check if a device is managed by RME using the Device Management State Summary. You can access the Summary by selecting Device Management option from RME > Devices.

In Extend VRF workflow, the devices listed in the Device Selector are the devices that are not participating in the selected VRF.

In Edge VLAN Configuration workflow, the devices listed in the Device Selector are only L2/L3 devices that are not participating in the selected VRF.

Q. What are the different categories in which the devices are managed by Virtual Network Manager? Or what criteria are used by Virtual Network Manager to categorize the devices in the network?

A. Virtual Network Manager identifies the devices based on the minimum hardware and software support required to configure VRF on the devices.

Based on the available hardware and software support in the devices, Virtual Network Manager classifies the devices into following categories:

VRF Supported Devices- Represents the devices with required hardware and software support available to configure VRF on the devices.

VRF Capable Devices - Represents the devices with required hardware support available. But the device software must be upgraded to support MPLS VPN MIB. For information on the IOS version that supports MPLS VPN MIB, refer http://tools.cisco.com/ITDIT/MIBS/MainServlet.

VNM classifies all the devices from Cat 3k and Cat 4k family of devices as VRF Capable devices as these devices do not have the required MPLS VPN MIB support.

Other - Represents the devices without required hardware support to configure VRF. SysOID of the device needs to be checked.

Q. If a device is managed by both RME and CM in the ACS mode, that particular device is not listed in the device selector in VNM Configuration or in VRF Troubleshooting workflow.

Q. In the ACS mode, the Virtual Network Manager application checks for user permissions in VNM and RME application. The user permissions are as defined below:

a. VNM > Configuration > Configuration permission in VNM application

b. VNM > Troubleshooting > Troubleshooting permission in VNM application

c. VNM > Reports > Reports permission in VNM application

d. RME > Config Management > NetConfig > NetConfig Create Job in RME application

e. RME > Config Management > Archive Management > Config Version Viewer

To use the following VNM functionality, the user must have the following permissions:

1. Create/Edit/Extend: The user must have permissions listed in A, D, and E

2. AEV/Delete: The user must have permissions listed in A and D

3. Troubleshooting: The user must have permissions listed in B and D

4. Reports: The user must only have permission mentioned in C

Q. While performing the VNM Configuration, VNM application prompts the following messages:

"The device(s) with display name(s) are already locked as they are used by configuration workflows. You cannot configure these devices. Wait for some time Or Ensure the devices are not used by configuration workflows and free the devices from CS > Admin > Resource Browser.

Or

Selected Device(s) are locked as they are used by configuration workflows. You cannot configure these devices. Wait for some time Or Ensure the devices are not used by configuration workflows and free the devices from CS > Admin > Resource Browser.

The above messages appear even if no VNM configuration is performed parallelly. Why do I get these messages?

A. The VNM application prompts with these messages when some other configurations are performed simultaneously.

You can check the status of the configuration workflow using CS > Admin > Resource Browser. The JOB Id/Owner column will give the details of the workflows currently running in the application.

These messages also appear if any VNM configuration workflow is abruptly ended or an error has occurred while unlocking the device. You can release the locked devices only after ensuring that no other configuration workflows are running simultaneously. You can release the locked device using the CS > Admin > Resource Browser option.


Note If you unlock a device which is participating in a configuration workflow, the configurations details will be overwritten or corrupted. By default, a lock will be released after two hours.


Q. Sometimes, while performing VNM configuration, I get the following message:

The device(s) with display name(s) are already locked as they are used by configuration workflows. You cannot configure these devices. Wait for some time Or Ensure the devices are not used by configuration workflows and free the devices from CS > Admin > Resource Browser.

Or

Selected Device(s) are locked as they are used by configuration workflows. You cannot configure these devices. Wait for some time OR Ensure the devices are not used by configuration workflows and free the devices from CS > Admin > Resource Browser.

Can I get the details of the user who has locked the devices to perform VNM configuration?

A. You cannot get the details of user who has locked the devices to perform VNM configurations.

Q. In the Create, Edit, or Extend workflow, the application do not list the Routing Protocols used while configuring VRF. The Routing Protocol information displayed is NA. What do I need to do to get the routing protocol configurations details?

A. When the Routing Protocol information displayed is NA, it means that the configuration details are not fetched successfully in Resource Manager Essential. You can schedule the Sync Archive job from Resource Manager Essentials > Config Mgmt > Archive Mgmt > Sync Archive.

Q. What are the details of the VNM log files? In which location are the VNM log files located?

A. The following are the details of the VNM log files:

1. Vnmserver.log - This log file logs the messages pertaining to the VNMServer process.

2. Vnmcollector.log - This log file logs the messages pertaining to the VNM collection.

3. Vnmclient.log - This log file logs the messages related to the User Interface.

4. Vnmutils.log - This log file logs the messages pertaining to the utility classes used by VNM client and server.

The above-mentioned VNM log files are located in the following location:

In Solaris : /var/adm/CSCOpx/log/

In Windows: NMSROOT/logs

Q. When is the VRF Collection process triggered?

A. Manually:

You can manually schedule to run the VRF Collection process by :

Providing the setting details using Virtual Network Manager > Administration > VRF Collector Settings > VRF Collector Schedule option.Or Clicking the Start VRF Collection link present in the Virtual Network Manager home page.

Automatically:

If you enable the Run VRF Collector After Every Data Collection in the VRF Collector Schedule page. The VRF Collection process will be automatically triggered after the completion of Data Collection.

You can reach the VRF Collector Schedule page using Virtual Network Manager > Administration > VRF Collector Settings page.

Q. After the completion of the Data collection process, the VNM Collector failed to run, What is the reason for failure?

A. Check if the Run VRF Collector After Every Data Collection option is enabled in the VRF Collector Schedule page. You can reach the VRF Collector Schedule page from Virtual Network Manager > Administration > VRF Collector Settings page.

Q. Where the SNMP timeout and retries details are taken for Virtual Network Manager?

A. The SNMP timeout and retires details are taken from Virtual Network Manager > Administration > VRF Collector Settings > VNM SNMP Timeouts and Retries. By default, all the devices have a timeout of six seconds and retry attempt of 1 second.

Q. What is the reason for VLANs not getting populated in the VLAN to VRF Mapping page in the Create VRFand Extend VRFworkflows ?

A. The VLAN to VRF Mapping page lists the links connecting the source and the destination device. The VLANs are not listed in fields displaying the links in the VLAN to VRF Mapping page because VNM tries to find a free VLAN in the devices connected using a link based on the following procedure

1. An SVI, VNM searches for free VLANs in the range 1- 1005

2. An SI, VNM searches for free VLANs in the range 1006-4005

Q. Why do I see the VRF description for all VRF(s) in home page as "Discovered by VNM" ?

A. While creating or extending VRF, the description that you have provided is deployed to the selected devices on which VRF is configured. But, the description provided while configuring or extending, is not read by the VNM application. Instead, the VNM application provides the default description for all VRFs as "Discovered by VNM".

Therefore, the description that you had provided is not displayed in the VNM home page.

Q. How do I enable the debug messages for Virtual Network Manager?

A. You can enable the debugging levels for a particular module using VNM > Administration > Debugging Options.

You can manually change the name and the size of the log file. The configuration log files are available under NMSROOT/MDC/tomcat/webapps/vnm/WEB-INF/classes. The changes made will be reflected after approximately 60 seconds.

Q. Why some port-channels are are not discovered in Virtual Network Manager?

A. Virtual Network Manager does not support port-channel and GRE Tunnel. Also, Currently VNM supports only 802.1Q

Q. What are the processes newly introduced for Virtual Network Manager ?

A. To run VNM, VNMServer process is newly introduced in the Campus Manager application. The VNM Collector process is executed as a Job.

Q. What is tested number of devices support in VNM?

A. In an Enterprise network, Virtual Network Manager is tested to support the configuration of 32 VRFs with VRF configuration supported in 550 devices in your network. However, at a given time, you can select up to 20 devices and configure VRF using the Create, Edit and Extend VRF workflow.

Q. What are the property files associated with Virtual Network Manager?

A. The following property files are associated with Virtual Network Manager:

1. NMSROOT/vnm/conf/VNMClient.properties - This property file is used to provide the settings for Purge and Home page auto Refresh

2. NMSROOT/vnm/conf/VNMServer.properties - This property file is used to provide the SNMP and VNMServer settings.

3. NMSROOT/vnm/conf/VRFCollectorSnmp.conf - This property file stores the SNMP Timeout and Retries that you have configured

Q. In the Interface to VRF Mapping page for the Create, Edit and Extend VRF workflow, why are values for the IP Address and SubnetMask fields empty?

A. If the physical interface that links two devices is not configured with an IP Address, then the IP Address and the SubnetMask fields are empty.

Q. What is protocol ordering for configuration workflows?

A. Configuration workflow uses the protocol ordering similar to ordering used by NetConfig in Resource Manager Essentials.

Choose the NetConfig as Application Name from using RME > Admin > Config Mgmt > Transport Settings page. You can view the protocol ordering in the Transport Settings page.

Q. What is protocol ordering for troubleshooting?

A. Troubleshooting VRF workflow uses the protocol ordering similar to ordering used by NetShow in Resource Manager Essentials.

Choose the NetShow as Application Name from using RME > Admin > Config Mgmt >Transport Settings page. You can view the protocol ordering in the Transport Settings page.

Q. If you configure commands to be deployed to two different devices, will the commands be deployed parallelly or serially?

A. The commands will be deployed to multiple devices parallelly, where as a series of commands with-in a single device, will be deployed in serial manner.

Q. Which VNM configuration jobs that are failed can be retried?

A. You can retry all the VNM Configuration jobs which are failed. VNM Configuration jobs are the jobs pertaining to Create, Edit, Extend, Delete VRF and Edge VLAN Configuration workflow.

Q. Why is the Monitor Real Time button disabled in the Ping or Traceroute VRF page?

A. The functionality for Monitor Real Time button is provided by Internetwork Performance Monitor (IPM). This button is enabled only when IPM is installed in the local server.

Q. In a multi-server setup environment, both RME and CM are installed in the remote machine. I have RME/CM in remote machines, but still devices are not shown in configuration workflows and are displayed as un-managed devices. Why?

A. It is mandatory to install Resource Manager Essentials in the local server to use the functionality of Virtual Network Manager.

Q. In the Troubleshooting VRF page, after selecting the source device, no VRFs are listed in the VRF List to troubleshoot. Why?

A. Initially, check if a VRF is configured on the selected source device. The VRF list in the Troubleshooting page enlists the VRF(s) configured in the selected source device as well as in the Global Table, which refers to the global routing table.

Q. Which interfaces are displayed in the Troubleshooting VRF page

A. When a VRF is selected then all the interfaces that are configured with the selected VRF in the corresponding device is listed.

If you select VRF as "Global Table", then the application displays all the interfaces that are not configured to any VRF

Q. In some scenarios, the VRF configuration commands are pushed to unselected devices. What is the reason?

A. In the following scenarios, the VRF configuration commands are pushed to unselected devices:

The VLANs are created in the VTPServer by default. In any VNM Configuration workflow, if you create a VLAN in VTP Client devices, then VNM application finds the corresponding VTP Server and create VLANs in that device.

In Delete VRF workflow, the virtualized interface in the connecting device will also be deleted, even if the device is not selected.

Q. Why the FHRP and DHCP configurations are not shown in Virtual Network Manager?

A. VNM does not fetch the details for the FHRP or DHCP configuration from the device. Also, VNM won't put the list of vlan(s) allowed on a trunk

The Protocols and DHCP Server details for existing or newly created SVIs are not fetched from the selected devices.