Guest

Cisco netManager IP Infrastructure

Troubleshooting Cisco netManager 1.1

Hierarchical Navigation

Downloads

Table Of Contents

Troubleshooting Cisco netManager 1.1

Introduction

Logging Information

Log File Location

Log File Configuration

IP Phone, Service Level View, and Physical Connectivity View Log Configuration

Services and Processes

Installation and Licensing

Upgrade from Cisco netManager 1.0 to Cisco netManager 1.1 Fails

Remote Deskstop Installation

Installation Fails to Install MSDE

SQL Error Appears During Installation

Evaluation License File Not Found

"Failed to read license files. Error:[]" Appears when Adding a License

Licensing Errors

Application Files Are Not Removed After Uninstalling

Device Management Problems

Device Addition Errors

Device Count Limit Error Message

Device Capabilities Are Not Discovered

Device Import Progress Bar Hangs

Device Capability Not Found During Device Discovery

Device Attributes Are Not Updated

Cannot Receive SNMP Traps or Syslog Messages from Devices.

Workspace Content

Device Capability Information Is Not Available

Device Information Missing or Listed as Not Available

Workspace Content Shows Old Information

IP Phone Information

Cannot Discover Phones for a Cisco Unified Communications Manager

Phones Are Not Seen After Adding a Device

Device Management Page Does Not Show Any Phones

Cannot Discover Phones of a Specific Model

Switch Details Are Missing

Service Level and Physical Connectivity Views

Views Are Blank

Service Level View or Physical Connectivity View Does Not Launch

Physical Topology View Is Not Updated when Adding or Removing Devices

Service Level View Does Not Show Correct Information

Miscellaneous Problems

Performance Polling Does Not Occur

JSON Parse Error Occurs

Handle Leaks Occur

Event and Semaphore Handle Leaks Occur

Changing the Hostname Causes Problems

Cisco netManager Services Stop and the System Tray Icon Is Red

Error Appears when Cisco netManager Is Launched

Telnet Not Working


Troubleshooting Cisco netManager 1.1

Revised: October 17, 2008

This troubleshooting document contains the following sections:

•Introduction

•Logging Information

•Services and Processes

•Installation and Licensing

•Device Management Problems

•Installation and Licensing

•IP Phone Information

•Service Level and Physical Connectivity Views

•Miscellaneous Problems

Introduction

Cisco netManager is available in two product configurations: Cisco netManager IP Infrastructure and Cisco netManager Unified Communications. Cisco netManager IP Infrastructure provides standards-based monitoring of network devices, services, or applications on TCP/IP and Windows. Cisco netManager Unified Communications includes all features of Cisco netManager along with the additional capability to provide visibility into, and monitoring of, Cisco Unified Communications devices. See the Quick Start Guide for Cisco netManager for licensing information.

This document covers steps to try when troubleshooting problems that may occur when using Cisco netManager. For additional information, see the Release Notes for Cisco netManager for limitations, known problems and workarounds.

Logging Information

This section contains the following logging information:

•Log File Location

•Log File Configuration

•IP Phone, Service Level View, and Physical Connectivity View Log Configuration

Log File Location

The installation log files are located in the root directory (<install_location>\logs)where Cisco netManager is installed. The file names are preceded with "CisconetManager." For example, Cisco_netManager_setup001.log.

Log File Configuration

ERROR level logging is enabled by default. Also, the maximum log file size is 5 MB.

To enable debug or trace level logging or to increase file size, modify the log configuration properties file located in <install_location>\conf\CNMLog.Properties.

Figure 1

CNMLog.Properties File

Supported log levels are the following:

•ERROR (currently shown as "ERROR" in the log4cplus.logger lines of Figure 1)

•WARNING

•INFO

•DEBUG

•TRACE

Note Saved changes will immediately take effect.

Different log files log information related to different components and features:

•CiscoDiscovery.log - Logs device addition, import, discovery and rediscovery information.

•LCPoller.log - Logs Cisco Communications Manager logical connectivity information which is used by the Service Level View.

•FaultComponent.log - Logs device event information.

•TrapProcessor.log - Logs SNMP trap information.

•CiscoNotificationFrameWorkApp.log - Logs events generated and processed by notifications.

•NotificationEmailApp.log - Logs emails sent by the notificatione engine.

•Performance.log - Logs Cisco-specific performance monitor polling information.

•CiscoInventoryCollector.log - Logs inventory collection and polling information.

•CNMLicenseManager.log - Logs licensing-related information.

IP Phone, Service Level View, and Physical Connectivity View Log Configuration

To configure the IP phone and topology logs, modify the <install_location>/etc/cwsi/PIFServer.properties file and uncomment the LogMsg.debug and LogMsg.trace statements. Also, increase the LogMsg.logFileSize so that information is not lost when the log file wraps.

Note For the log settings to take effect, you must restart the IPIUService from the windows services.

Services and Processes

The Cisco netManager application runs as multiple window services and processes. It is essential that these services be running properly for the application to function correctly. Check the services from the Control Panel and to see if the following have been started properly:

Service/Process Image Name
Description

NmService.exe

Polling engine service

NmWebService.exe

Web server service

Sqlservr.exe

Database engine service

PIFService.exe

IP phone information and topology view services


Installation and Licensing

This section contains the following installation and licensing information:

•Upgrade from Cisco netManager 1.0 to Cisco netManager 1.1 Fails

•Remote Deskstop Installation

•Installation Fails to Install MSDE

•SQL Error Appears During Installation

•Evaluation License File Not Found

•"Failed to read license files. Error:[]" Appears when Adding a License

•Licensing Errors

•Application Files Are Not Removed After Uninstalling

Upgrade from Cisco netManager 1.0 to Cisco netManager 1.1 Fails

The upgrade fails when Cisco netManager 1.0 is not installed in the default installation folder. The default installation drive is where the operating system is installed; for example, C:\Program Files\Cisco netManager. To correct the problem, do the following:

Step 1 Uninstall Cisco netManager 1.0 and select the option to save a database backup.

Step 2 Install Cisco netManager 1.0 in the default installation folder that the installation wizard displays and select the option to restore from the database backup.

Step 3 Install Cisco netManager 1.1.

Remote Deskstop Installation

Do not start installation from Remote Desktop. Microsoft SQL Server Desktop Engine (MSDE) has known compatibility issues with Remote Desktop, a feature in Windows 2000 Server (and later versions). Do not use any remote control software that uses sessions to install Cisco netManager.

Note Sessionless remote control software, such as VNC, should work.

Installation Fails to Install MSDE

Installation fails to install MSDE if file and print sharing are not enabled.

To enable file and print sharing:

Step 1 In the Control Panel, double-click Network Connections.

Step 2 From the Advanced menu, select Advanced Settings.

Step 3 On the Adaptors and Bindings tab, ensure that File and Print Sharing for Microsoft Networks is selected.

SQL Error Appears During Installation

SQL configuration fails during installation, displaying error messages. This happens when MSDE is not installed properly.

Step 1 Close the error messages.

Step 2 Create a new registry key and string value:

a. Click Start > Run. The Run dialog box opens.

b. In the Open field, enter Regedit, then click OK. The Registry Editor opens.

c. Create the following registry key: 

HKEY_LOCAL_MACHINE\SOFTWARE\ 
Cisco Systems\Cisco netManager\1.0

d. Create a String Value key named NMSROOT and, for the value, enter the installation folder that you selected during installation; for example: C:\Progra~1\CiscoN~1.

e. Close the Registry Editor.

Step 3 From the command line, execute clean_system.exe in the <CD Drive>\cleanup_tools folder.

Step 4 Restart the server.

Step 5 Start the installation again.

Evaluation License File Not Found

This occurs during Cisco netManager installation when there are multiple CD ROM drives and the product CD is inserted into one of the drives. Do the following:

Step 1 When the installation prompts you for the license file, navigate to the CD ROM drive where the product CD is located.

Step 2 From the CD directory, navigate to the license folder.

Step 3 Select the evaluation.lic file.

Step 4 Click Next to proceed with the installation.

"Failed to read license files. Error:[]" Appears when Adding a License

This occurs when changing the hostname. See Changing the Hostname Causes Problems.

Licensing Errors

Licensing errors can be caused by the following:

•The license file is corrupt or the file have been edited.

•Features in the license file has expired.

•The system time has been changed.

•The license is being installed on the wrong machine.

•Other internal errors; for example, not being able to connect to the database.

Step 1 From Start > Programs > Cisco netManager > Daemons > Stop, stop the following services:

–NMService

–NMWebService

–IPIU

Step 2 Copy the new license file to <Install Location>/etc/license.

Step 3 Run the upgrade script from Start > Programs > Cisco netManager > Upgrade License. A pop-up message box showing the final device count, expiration dates will be presented to the user.

Step 4 Click OK.

Step 5 From Start > Programs > Cisco netManager > Daemons > Start, start the following services:

–NMService

–NMWebService

–IPIU

Application Files Are Not Removed After Uninstalling

After uninstalling Cisco netManager from some servers, files sometimes remain in the installation folders. This can also occur if the uninstallation process is cancelled before it completes.

Run the clean_system.exe script to remove the files:

Step 1 Go to the Windows\System32\cleanup_tools folder. For example, if the operating system is installed on C:, then the folder will be at C:\Windows\System32\cleanup_tools.

Step 2 Locate and run clean_system.exe.

Step 3 Follow the instructions provided by the script.

Note If clean_system.exe is not available in the Windows\System32\cleanup_tools folder, you can run it from the cleanup_tools folder on the Cisco netManager product CD.

Device Management Problems

This section contains information on the following device management problems:

•Device Addition Errors

•Device Count Limit Error Message

•Device Capabilities Are Not Discovered

•Device Import Progress Bar Hangs

•Device Capability Not Found During Device Discovery

•Device Attributes Are Not Updated

•Cannot Receive SNMP Traps or Syslog Messages from Devices.

Device Addition Errors

The following errors may appear when adding or importing devices:

•"Error scanning device x.x.x.x. Probable cause is it does not exist"

This error appears because the device is Internet Control Message Protocol (ICMP) ping unreachable. Troubleshoot the connectivity and try to add the device again.

•"Domain Name Server (DNS) reports that (x) cannot be resolved to a network address"

This error may appear due to the following:

–The forward DNS resolution for the given DNS name does not work.

–It is an invalid IP address.

Device Count Limit Error Message

An error appears, stating that a device cannot be added because the device count limit on the purchased license has been reached. Duplicate devices may have been added, increasing the devicecount inventory. A device might have also been added and discovered multiple times as different device types; for example, a host and a voice gateway.

When adding a device to Cisco netManager, do not click Cancel while a device scan is in progress. Doing so could cause duplicate devices to be added to the system. If duplicate devices are added, manually delete the duplicate device from the Device tab (right-click the device and select Device Management > Delete).

Device Capabilities Are Not Discovered

Try the following:

–Verify that the right credentials were entered while adding the device (New Device > Advanced > SNMP Community).

–Check the CiscoDiscovery.log file for runtime errors.

–Delete and readd the device.

–Update the credentials (Device > Properties > Credentials) and rediscover the device.

Device Import Progress Bar Hangs

This happens when the connection between the web client and server is lost. Try the following:

•Check the status of the device import on the home page. If it is showing as "In Progress," it means the device addition is in progress.

•Click the status to get a detailed report for the device import. If device discovery takes too long, a "Timeout" error is displayed in the report. Default time-out is 10 minutes for each device. Reimport the same file if this error is seen.

Device Capability Not Found During Device Discovery

Try the following:

•Edit the CiscoDiscovery.log file to enable level to TRACE.

•Rediscover the device whose capability entries are missing.

•In the log file, for that device (IP address), check for the statement "GetDeviceCapability detected : XXX". If there is no such statement for missing capability, it means Cisco netManager is not able to discover that capability for the following reasons

–Device might not support the required MIB implementation needed to discover that capability. Check with any MIB browser whether the SNMP OID is returning the expected value.

–If the MIB browser responds, but Cisco netManager is not able to discover the capability, then the problem might be due to SNMP timeout. Increase the Global SNMP Timeout and Retry value and rediscover the device.

To increase the Global SNMP Timeout and Retry value, select GO > Configure > Default SNMP timeout, and enter a value higher than 2 seconds.

Note Increasing the SNMP timeout also increases polling times. This is because SNMP takes more time on slower devices and provides a mechanism to discover device inventory.

Device Attributes Are Not Updated

Device attributes, such as interface status, are not updated during polling cycles. Try the following:

•Verify that NmService.exe is running and shows activity. Do this by looking at its CPU consumption figures in the Task Manager.

•Verify that polling is occurring by running NmEventViewer.exe (<INSTALL LOCATION>\infrastructure). Right-click inside the NmEventViewer window and set Debug on.

Watch for debug statements containing the keyword Cisco. This will tell you which performance monitor has finished running. If no Cisco-related logs appear in the Event Viewer, or if there are no logs at all, then something has gone wrong and requires debugging. You can try restarting the NmService from control panel'Services.

Cannot Receive SNMP Traps or Syslog Messages from Devices.

Check the following:

•By default, the SNMP trap receiver runs on port 162, and the syslog receiver runs on port 514. Verify that third-party receivers are running on these ports by running netstat. The status of Cisco netManager trap and syslog receivers is shown in the SNMP trap log, and on the syslog report page, as either ON or OFF.

•To run third-party receivers, you must run scripts (cisco netManager\conf\TrapReg.vbs and SyslogReg.vbs) that disable Cisco netManager trap and syslog receivers. You must then restart Cisco netManager Engine for the change to take effect.

•From Reports > System > SNMP Trap log, you can see all of the traps the system has received. A trap is translated to an event only if the device is managed and the trap is supported.

•Usually, when the system receives active monitor events such as Ping Down or SNMP Down, it stops receiving other events for that device.

•Cleared events that are removed from the event report can be found in the Event History report.

•Some events, such as Link Down, persist for a long time due to the interface being down continually.

Workspace Content

This section contains information on the following workspace content problems:

•Device Capability Information Is Not Available

•Device Information Missing or Listed as Not Available

•Workspace Content Shows Old Information

Device Capability Information Is Not Available

The workspace content relating to the capability you are interested in does not appear in the device-specific workspace view. Try the following:

•Identify if the capability is associated with the device. Verify that the monitor is selected in the Device Properties Performance Monitors dialog box.

•If a capability is not identified by Cisco netManager, follow the troubleshooting steps (located in the beginning of this document) relating to discovery.

•The workspace content might have been removed from the workspace. Add the workspace content again.

Device Information Missing or Listed as Not Available

This could be due to improper SNMP response from the device or to SNMP timeout during discovery. Look at the CiscoInventoryCollector.log file for details. If the data is part of the normally polled information, the data will be collected in the next poll cycle. If the data is not collected as part of inventory, rediscover the device.

Workspace Content Shows Old Information

Most of the data in the inventory capability portlet is discovered during discovery. Rediscover the device to refresh the data.

If the information is statistical in nature or is a status field (enabled/disabled) then this could be caused by data not being retrieved during a polling cycle. To debug this issue look at the CiscoInventoryCollector.log file. The possible reasons are SNMP timeouts or credential changes.

IP Phone Information

This section contains information on the following IP phone problems:

•Cannot Discover Phones for a Cisco Unified Communications Manager

•Phones Are Not Seen After Adding a Device

•Device Management Page Does Not Show Any Phones

•Cannot Discover Phones of a Specific Model

•Switch Details Are Missing

Cannot Discover Phones for a Cisco Unified Communications Manager

•Check the device report to see if a Cisco Unified Communications Manager is listed.

•Verify that the IPIUService is running in Windows Services.

•Verify that the SysAppl MIb is responding to the Cisco Unified Communications Manager by running snmpwalk on sysApplInstallPkgTable (sysApplInstallPkgProductName OID is 1.3.6.1.2.1.54.1.1.1.1.3).

•Check the PIFServer.log found under NMSROOT/logs to verify that the service was able to connect to the database. Check for a "Failed to establish DB connectivity" entry.

•Walk the ccmPhoneTable of the Cisco Unified Communications Manager MIB with OID 1.3.6.1.4.1.9.9.156.1.2.1 for the device and verify that SNMP data is populated.

•Walk the ccmPhoneTable of the Cisco Unified Communications Manager MIB with OID 1.3.6.1.4.1.9.9.156.1.2.2 for the device and verify that SNMP data is populated.

•Make sure ccmPhoneProductTypeIndex (OID 1.3.6.1.4.1.9.9.156.1.2.1.1.18) returns nonzero values. If a zero value is returned, restart the SNMP service on Cisco Unified Communications Manager.

•Check the SNMP walk of ccmPhoneExtnTable OID 1.3.6.1.4.1.9.9.156.1.2.5.

•Restart IPIUService from Windows Services.

Phones Are Not Seen After Adding a Device

See Cannot Discover Phones for a Cisco Unified Communications Manager.

Device Management Page Does Not Show Any Phones

See Cannot Discover Phones for a Cisco Unified Communications Manager

Cannot Discover Phones of a Specific Model

Verify that the phone model is supported.

Switch Details Are Missing

Verify the following:

•The switch is in monitored state.

•SNMP walk on switch cdpCacheTable .1.3.6.1.4.1.9.9.23.1.2.1 returns phone information.

Service Level and Physical Connectivity Views

This section contains information on the following Service Level View and Physical Connectivity View problems:

•Views Are Blank

•Service Level View or Physical Connectivity View Does Not Launch

•Physical Topology View Is Not Updated when Adding or Removing Devices

•Service Level View Does Not Show Correct Information

Views Are Blank

If Sun Microsystems Java Runtime Environment (JRE) version 6.0 is installed after the Cisco netManager installation is complete, the Service Level View and Physically Connectivity View may not appear. Reboot the system after installation to make the topologies appear.

Service Level View or Physical Connectivity View Does Not Launch

Try the following:

•Verify that IPIUService is running in the Windows Services panel. See Physical Topology View Is Not Updated when Adding or Removing Devices.

•Check the PIFServer.log found under NMSROOT/logs to verify that the service was able to connect to the database. Check for the following entry: "Failed to establish DB connectivity"

•Telnet to port 43451 to see if it is enabled across a firewall.

•Verify that the browser being used is supported by Cisco netManager.

•Verify that the right version of Flash Plugin is installed on Internet Explorer.

•Verify that JRE version 6.0 is installed on the machine by executing java -version at the command prompt. If the correct version is installed, restart restart the machine and launch the Physical Connectivity View.

Physical Topology View Is Not Updated when Adding or Removing Devices

Do the following:

Step 1 Select Start > Settings > Control Panel > Administrative Tools > Services.

Step 2 Locate and double-click the IPIU service. The Properties window appears.

Step 3 Click Start to restart the IPIU service.

Service Level View Does Not Show Correct Information

Try the following:

•Verify that NmService is running.

•Verify that Cisco Unified Communications Manager device is discovered with the capability.

•Verify that Cisco Unified Communications Manager MIB is responding properly.

•CVerify that the device is in suspended or maintenance state.

•Verify that all the Cisco Unified Communications Managers in the cluster are added in Cisco netManager.

Miscellaneous Problems

This section contains information on the following miscellaneous problems:

•Performance Polling Does Not Occur

•JSON Parse Error Occurs

•Handle Leaks Occur

•Event and Semaphore Handle Leaks Occur

•Changing the Hostname Causes Problems

•Cisco netManager Services Stop and the System Tray Icon Is Red

•Error Appears when Cisco netManager Is Launched

•Telnet Not Working

Performance Polling Does Not Occur

Try the following steps:

Step 1 Check on the Device Page to see if the device icon is green. If it is red, it means the device is unresponsive via ping or SNMP. If the icon is green, then go to the Detailed Device View Page of the device and check the last poll time for any of the reports for Fan, Power Supply, or Temperature.

Step 2 Wait 3 to 4 minutes and refresh the page, then verify that the poll time is updated to the latest time.If the poll time is not updated, then start the event viewer located at <INSTALLPATH>/Infrastructure/EventViewer.exe.

Step 3 Right-click the NmEventViewer window and select Debug On. Wait for two minutes, the following lines should appear:

[2007-08-09 17:07:14][EVENTLOG][2007-08-09 17:07:14 Type:Success, Category:RDC, Source:Cisco Memory Utilization] Memory Polling Completed for 10.76.91.116

[2007-08-09 17:07:14][EVENTLOG][2007-08-09 17:07:14 Type:Success, Category:RDC, Source:Cisco Disk Utilization] Disk Polling Completed for 10.76.91.116

[2007-08-09 17:07:20][EVENTLOG][2007-08-09 17:07:20 Type:Success, Category:RDC, Source:Cisco CPU Utilization] CPU Polling Completed for 10.76.91.147

[2007-08-09 17:07:20][EVENTLOG][2007-08-09 17:07:20 Type:Success, Category:RDC, Source:Cisco CPU Utilization] CPU Polling Completed for 10.76.91.104

If these lines do not appear, then the polling engine is hung. Restart the NmService to see if the issue gets resolved. Zip and send Cisco Technical Assistance Center (TAC) all the logs located at <INSTALLPATH>/logs/*.log.

Step 4 If the lines appear then check the device's SNMP response. Use an SNMP tool, such as MIB browser, and query the sysObjectID of the device.

Step 5 If the sysObjectID does not respond then the device is SNMP DOWN. Try to rediscover the device at a later time. You will need to repeat this step a number of times until the device changes to SNMP UP.

If the sysObjectID responds and the device is SNMP UP and particular monitors (CPU, Memory, Disk, and so on) do not show any values in the Detailed Device View, those OIDs must be queried.

If the OIDs do not respond, then it means that the device does not support the required MIBS.

JSON Parse Error Occurs

This message does not affect any application processes. It might reappear in 6 to 7 hours. Click OK to dismiss the message.

Handle Leaks Occur

Handle leaks can occur when, in addition to Cisco netManager trap and syslog receivers, third-party trap and syslog receivers run on the server.

To disable or enable the Cisco netManager trap and syslog receivers, do the following:

Step 1 Open a command prompt and go to <Installation Path>\Cisco netManager\conf; for example: 

cd Program Files\Cisco netManager\conf

Step 2 Run the command TrapReg.vbs with one of these arguments:

0—Disables traps

1—Enables traps 

TrapReg.vbs <0|1>

Step 3 Run the command SyslogReg.vbs with one of these arguments:

0—Disable syslog receiver

1—Enable syslog receiver 

SyslogReg.vbs <0|1>

Step 4 Restart Cisco netManager Engine from the task tray.

Event and Semaphore Handle Leaks Occur

A gradual handle leak may be observed from the browser window when viewing the Service Level View and Physical Connectivity View topologies. This occurs in the following cases:

•MSXML filter is installed (with Office 2003 Installation).

For more information on the symptom and workaround, visit http://support.microsoft.com/kb/841532.

Note This website is Copyright © 2008, Microsoft Corporation.

•Handle leak due to Flash Eventing mechanism.

If the Service Level View or Physical Connectivity View appears to be running slowly, close and reopen the browser window.

Changing the Hostname Causes Problems

After changing the hostname (computername) and restarting the operating system, the following problems may be seen:

•When starting the upgrade license utility, the following error message appears:

"Failed to read license files. Error:[]"

•Cisco netManager services stop after a period of time. The system tray icon turns red, indicating that the daemons have stopped.

•When attempting to launch Cisco netManager from the web browser, the following message appears:

Source:'AspForms.AspForm.1'

Line:17 Char:0

Error:0 'Failed to initialize translation object

The hostname is defined during installation and stored in the Open DataBase Connectivity (ODBC) delivery status notification (DSN). Currently netManager does not auto-detect a hostname change and cannot automatically change the DSN. If a hostname is changed, you have to manually stop all running whatsup services and change the DSN:

Step 1 Stop all netManager services:

•IpSwitch WhatsUp Engine

•IpSwitch Web Server$WhatsUp

•IPIUService

•MSSQL$WhatsUp

Step 2 From the Start menu, select Control Panel > Administrative Tools > Data Sources (ODBC).

Step 3 Select the System DSN tab.

Step 4 From the list, select WhatsUp and click Configure. The wizard that comes up has an entry which instructs the SQL server to connect to - (hostname) \WHATSUP.

Step 5 Change the hostname displayed by entering the new hostname.

Step 6 Click Next and exit the wizard without changing any default configurations.

Step 7 Restart all netManager services you have stopped (MSSQL$WhatsUp should be started first) or reboot the system.

Cisco netManager Services Stop and the System Tray Icon Is Red

Cisco netManager services stop after a period of time. The system tray icon becomes red, indicating that the daemons have stopped. This occurs when the hostname is changed. See Changing the Hostname Causes Problems.

Error Appears when Cisco netManager Is Launched

When attempting to launch Cisco netManager from the web browser, the following message appears:

Source:'AspForms.AspForm.1'

Line:17 Char:0

Error:0 'Failed to initialize translation object

This occurs when the hostname is changed. See Changing the Hostname Causes Problems.

Telnet Not Working

The Telnet protocol handler is disabled by default in Microsoft Internet Explorer 7. To use the Telnet tool in Cisco netManager, you need to re-enable the Telnet protocol.

To re-enable the Telnet protocol:

Step 1 Click Start > Run. The Run dialog box opens.

Step 2 In the Open field enter Regedit, then click OK. The Registry Editor opens.

Step 3 Go to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl.

Step 4 Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl, create a new key named FEATURE_DISABLE_TELNET_PROTOCOL.

Step 5 Add a DWORD value named iexplore.exe and set the value to 0 (decimal).

Step 6 Close the Registry Editor and restart Microsoft Internet Explorer. The Telnet protocol is enabled.

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)

OL-17958-01