|
|
This document discusses the CiscoWorks 2.1(2) Release supporting NetView for AIX. It includes information on modifications and improvements to CiscoWorks 2.1(1), as well as other per material.
This release note describes the following:
Before installing CiscoWorks, we recommend that you install the GA version of IBM NetView for AIX on your workstation.
In addition, the following items are necessary in order to work with CiscoWorks applications:
To find out if you either APAR is installed, as root enter the following at the prompt:
hostname# lslpp -A | grep <APAR number>
If the APAR number and explanatory note is returned, you do not need the specified APAR.
If you do need the APAR, call IBM at 800 225-5249 and ask for the previously named items.
The CiscoWorks Administration and Installation Guide on NetView for AIX states that the required disk space is 1000 MB. The required disk space for CiscoWorks is 340 MB. The recommended disk space for CiscoWorks (including polling and logging activity) is 1000 MB.
If you experience difficulty with Sybase during installation, ensure that your system name is set using the uname command. To view your system name, use uname -n. To set your system name, use uname -S. Your system name should be less than nine characters in length and match the IP address via nslookup.
The following information was unavailable when the documentation was printed. This information supersedes the CiscoWorks documentation in print and will be updated on the next version of the UniverCD.
The following additions were finalized after the documentation set went to publication.
In the CiscoWorks Administration and Installation Guide on NetView for AIX, page 4-2, the .cshrc file is mentioned. The guide uses C-shell references as a standard way to refer to this type of file. If you are using the Korn shell or K-shell, edit your .profile file.
For your convenience, copy the following information into your profile to use the Korn shell references:
#set environment variable for NetView, CiscoWorks and sybase. export NMSROOT=/usr/nms export SYBASE=/usr/nms/sybase #Set path for CiscoWorks and Sybase executables export PATH=$PATH:$NMSROOT/bin:$NMSROOT/etc:$SYBASE/bin:/usr/OV/bin #set path for CiscoWorks man pages. if [ "$MANPATH" = "" ] ; then export MANPATH=/usr/nms/man else export MANPATH=$MANPATH:/usr/nms/man fi
The following features were added to installation, configuration, and deinstallation after publication of the manual set:
These features enable users retain their existing Sybase database and install a later version of CiscoWorks base product. If you buy a separate Sybase package at a later date and want to use it instead of the CiscoWorks Sybase, you can deinstall the Sybase supplied with CiscoWorks.
To reconfigure an existing Sybase to work with CiscoWorks, specify the directory name where the nms master database needs to be created. The SYBASE environmental variables defaults to /usr/nms/sybase. Set the environmental variable if required.
Use the following guidelines for the options:
Some restrictions regarding the previous options follow:
The CiscoWorks Software Release 2.1(2) reinforces much of the functionality of preceding releases including the following:
This section lists notes and restrictions that apply to the CiscoWorks Software Release 2.1(2).
General caveats are noted first, followed by application-specific caveats listed alphabetically.
This section describes general caveats associated with CiscoWorks applications. These caveats include database issues.
AutoInstall Manager, Software Inventory Manager, Software Library Manager, and Device Software Manager do not currently support the Cisco 4500. To upgrade Cisco 4500 software, refer to your Router Products documentation and manually upgrade the software. [CSCdi24142]
A modified registration file is available on FTP if you wish to see all CiscoWorks applications preceded with a CW-prefix. If you prefer to see this type of menu structure, copy this file from /ftp/pub/CiscoWorks/PATCHES/aix-netview directory. The README file is updated if you would like more information. This file will also be made available on CIO.
With CiscoWorks 2.1(2), when you run Configure CiscoWorks from the SMIT interface, a CiscoWorks group called cscworks is automatically created. However, if you have a group called CscWorks, the configuration script neither deletes nor uses this existing group. Instead, a new group called cscworks is always created.
If you are performing a new installation, you will not experience this problem. However, if the target computer already has Ciscoworks installed, you may encounter various problems. For example, the existing passwd file will have an entry for the user cscworks and a group ID of 56. The new group called cscworks will have an ID of 57. This is a known defect and expected to be fixed in a subsequent release of CiscoWorks. [CSCdi24837]
When deinstalling CiscoWorks, you may see the icon of the CiscoWorks Autoinstall Manager remaining in your network map. You can delete the icon manually. This is a known defect and is expected to be fixed in a subsequent release of CiscoWorks. [CSCdi24264, CSCdi24395]
The Cisco 2500 router may display as a Cisco 3000 or a CS-500. This occurs on Cisco 2500 routers with software releases before 9.21. If your Cisco 2500 has version 9.21 or later, your device displays correctly. To correct this problem, upgrade your Cisco router to 9.21 or later, or use the Change Symbol Type command on NetView for AIX to correctly display the device as a Cisco 2500. [CSCdi20033]
In some isolated cases, you may be unable to download a command set in a foreign domain even though you logged into that domain as a user with the needed privileges. By selecting the Change User command from the CiscoWorks Security menu, you can normally login as another user as a means to temporarily expand your access privileges. However, if you select the Change User command to login as a user in a different domain, you may find that you are unable to download a command set. In this case, the application does not update the user privilege. To overcome this problem, try logging in with a different username. [CSCdi24585]
When PTF - U434186 for NetView 3.1 is installed, the Cisco specific icons in your map will revert back to generic icons. The PTF process replaces two files: oid_to_sym and oid_to_type which cause this problem. The PTF process makes a backup of the these files to /usr/OV/conf/oid_to_type.U434186 and /usr/OV/conf/C/oid_to_sym.U434186.
To overcome the problem, perform the following steps:
Step 1 Do a diff -c between the current file /usr/OV/conf/C/oid_to_sym with /usr/OV/conf/C/oid_to_sym.U434186 and append the differences to /usr/OV/conf/C/oid_to_sym.
Step 2 Do a diff -c between the current file /usr/OV/conf/oid_to_type with /usr/OV/conf/oid_to_type.U434186 and append the differences to /usr/OV/conf/oid_to_type.
While using any of the database-related applications, such as the Configuration Management application, the following message may occasionally appear:
Confman Init Error!Unable to verify user login.Unable to login as <nms>No database table named domains
To correct this problem, stop Sybase and then restart it. Although restarting the database will solve the immediate problem, the Init Error message suggests that you are running out of user connections. The maximum number of connections is currently set to 100. If you need more connections, increase the number by using the sp_configure command. For example, to increase the number of user connections to 150, enter the following command at the UNIX prompt:
isql -Usa -P <SA password>sp_configure user 150goreconfigurego
To make the additional user connections available, restart CiscoWorks using the shutdown_nms and nmstartup commands. [CSCdi18996]
CiscoWorks can only be installed in the /usr/nms directory. If you already have a directory named /usr/nms, you must rename it in order to install CiscoWorks or your directory contents will be overwritten. [CSCdi24262]
When the pointer is busy (hourglass state), you may observe that you can perform other operations with your mouse. However, the hourglass state indicates that you should wait until the current process is complete before starting another one. To avoid problems with your use of CiscoWorks, do not perform multiple-mouse operations even when some applications incorrectly indicate this is possible. [CSCdi23748, CSCdi20005]
If your transaction log is full and you attempt to run nmlogreset, the script fails. This failure may only remove some or no log entries. However, the script will run successfully if your log is not full. You can clear the transaction log manually using the following isql command procedure at the UNIX prompt:
#$SYBASE/bin/isql -Usa -P <SA password>1dump tran nms with no_log2go1usenms2go1checkpoint2go1usemaster2dump tran master with no_log3go1checkpoint2go1quit
The nmlogreset script will not work if Sybase is installed elsewhere other than /usr/nms/sybase. The workaround is to specify SYBASE to point to $SYBASE instead of $NMSROOT.[CSCdi27995]
Depending on your particular system configuration, you may note some changes in the performance of some CiscoWorks applications. In general, you can expect an increase in performance as you increase the memory allocation and swap space of your system. [CSCdi15368]
After configuring CiscoWorks, you need to manually add NMSROOT and SYBASE environmental variables to your .cshrc or .profile file. You should also add NMSROOT/bin and SYBASE to your path statement. This ensures that your NetView for AIX platform can recognize CiscoWorks. Look into install.cshrc or install.profile and add the contents of the file as appropriate to your initialization files. The install.cshrc and install.prof are found in the /usr/nms/install directory. This problem is observed when the version of Netview for AIX installed is different from the version used to build the CiscoWorks product. [CSCdi24972]
This caveat applies to Cisco routers, but is pertinent to CiscoWorks users.
When defining a community string for a router, enter the community string without quotation marks around it. For example, to define the community string as "public," enter the following command:
snmp-server community public RODue to a conflict in the number of supported bits between the router (32 bits) and the Sybase database (31 bits), when data collected on MIB (Management Information Base) variables exceeds the 31-bit limit, the numbers stored in the Sybase database become negative. Note that the exporting feature of the Polling Summary application recovers the unsigned 32-bit values even when they appear negative in Sybase. [CSCdi12372]
The Log daemon (nmlogd) establishes a connection with the Sybase server. If the Sybase dataserver dies, the Log daemon attempts to reestablish the connection with the Sybase dataserver once every 60 seconds until it succeeds. If the Log daemon is unable to connect to the Sybase dataserver after continuous attempts, it displays a Sybase error message that explains the reason for the error.
A typical example of an error message follows:
Nmlogd: Sybase error_handler: General SQL server error: Check messages from SQL error.
Refer to your Sybase documentation for an explanation of the Sybase error message and for instructions on how to prevent this message from reappearing. [CSCdi08183]
When running nmadd (Add to database application) from the command line, the specified device will have a community string of "public" even though you may have specified read or read/write. To correct this problem, open the Device Information window from within Device Management and manually reset the community string. [CSCdi24967]
Caveats for the AutoInstall Manager application follow.
If you enable a device entry and the TFTP data transfer to the neighbor router fails, the AutoInstall Manager currently displays an alert message declaring that TFTP failed. However, AutoInstall Manager continues to declare the device entry as enabled. Consequently, you currently cannot distinguish between the situations where this TFTP transfer failed or succeeded. This is a known defect and is expected to be fixed in a subsequent release of CiscoWorks. [CSCdi24607]
If device information already exists in the NetView for AIX database, the AutoInstall Manager presently cannot be used on that device. If you attempt to use AutoInstall Manager on such a device already, you will receive the following error message when you click on the Apply button after entering all the information:
Device hostname or IP address not unique.
In order to use AutoInstall Manager on this device, you must remove its reference from the database (from all the maps in which it exists). [CSCdi24503]
The autoinstall feature requires IP forward protocol to be added to a remote router configuration. If you already have an IP forward protocol statement, such as UDP <port number> (a non-default port), on the remote router, CiscoWorks is not aware of it and adds another IP forward protocol statement to the router.
The previous forward-protocol UDP statement is lost and the router stops forwarding UDP packets destined for port xxx to the helper address. The AutoInstall Manager overrides the neighbor device configuration file in the following manner:
ip forward-protocol udp 285 --> Original configuration of the neighbor device ip forward-protocol udp --> Ciscoworks sticks this in the config file.
This effectively nullifies the first command. To resolve this problem, once the new device is up and running, Use the telnet command to connect to the neighbor device and manually remove the command ip forward-protocol udp. [CSCdi22012]
When working with AutoInstall Manager, be careful to select only serial devices for the Neighbor router, even though the application may permit you to select other interfaces. The current version of AutoInstall Manager supports only devices attached to serial interfaces. [CSCdi24605]
Caveats for the Configuration Management application follow.
Configuration Management exits with a core file if you attempt to save a device configuration comment file larger than 131 kilobytes (KB). After restarting the application, Configuration Management will exit again while trying to get the same device configuration for the comment file of more than 131 K. To resolve this problem, reduce the comment file to under 131 KB, or remove the configuration file that the large comment file is associated with. Then restart the application. This problem will be fixed in a future release. [CSCdi25060] [CSCdi26797]
It is possible to download a configuration file containing syntax errors. If you suspect this is the case, log in to the router Console, then initiate a TFTP (Trivial File Transfer Protocol) configuration file download from the router. The errors will be displayed on your router Console screen. [CSCdi02187]
This defect appears to be caused by defect CSCdi26797. After running nmconfig via the command line with several options, under unusual circumstances, you may see an L status displayed for the same device for two different versions. The cause of this defect is unknown at this time and will be fixed in future releases. [CSCdi26801]
When working with Configuration Management, if you restart a device when a TFTP transfer is taking place, the TFTP transfer fails. If you encounter this problem, retry the operation being careful not to restart the device until the data transfer is complete. [CSCdi24953]
Caveats for the Configuration Snap-In Manager application follow.
If you did not set umask correctly in your UNIX account, the Configuration Snap-In Manager may not be able to read temporary files generated by itself. Consequently, the application cannot download the file by clicking on the DoItNow button. If you try this operation, you might see an error message in the status window saying "Invalid file" and TFTP failed. In order to run the Configuration Snap-In Manager correctly, add the following line to your .cshrc or .profile file:
umask 2
Without this line in your .cshrc file, Configuration Snap-In Manager may not execute properly and display the error message after you click on the DoItNow button. You may find that other values, besides umask 2, will make Configuration Snap-In-Manager execute properly; however umask 2 is usually the default recommended value. [CSCdi20386]
When downloading a partial configuration file to a router, an error message list may appear. The following error message list may appear when you create a partial command, select a router, and then click on the DoItNow button to download the partial configuration file:
Toolkit getting configuration error.TFTP Transfer failedPossible errors:Tftp server is not running.Directory protection error.No RW community string.Please check tftp server setupand community string.
If you see this message for an incorrect reason, you can get past the problem by checking the router to see if the configuration has already been updated; otherwise, repeat the downloading procedure. [CSCdi16790]
When running Configuration Snap-In Manager, you may receive an error message indicating that the Line command set for the aux password is invalid, even though you correctly set the Line Type/Password. Currently, if you encounter this problem you are not able to download the line command set for the aux password. This is a known problem and is expected to be fixed in a subsequent release of CiscoWorks. [CSCdi24588]
If you download a file to a router running Cisco Systems Software Release 8.3 or earlier, the original banner in the router configuration is removed. To avoid the problem, upgrade your software to Release 9.x or later. [CSCdi16927]
The Configuration Snap-In Manager uses nms as the default user when scheduling commands. When the scheduled command is executed by the Global Command Scheduler, the following error displays:
nmpccmdb: Security check error! User name <nms> is not assigned to any group. Please run NMADMIN and add this user to a group. No rows found in the users table
The workaround is use some other user, instead of nms, who is assigned to some group and created using Security Manager. [CSCdi27953]
Caveats for the Device Management application follow.
Immediately after initializing a device, if you attempt to add contact names from the Contacts List, you may notice that the names do not appear in the Contacts column of the Device Management window. Currently, the Add Contacts command is temporarily disabled after selecting the Initialize command from the Options menu. If you encounter this problem, try adding contacts again by reselecting the names from the Contacts List. The second attempt will be successful. [CSCdi24895]
The Device Information window contains specific data obtained from the network device or database, as well as what is physically entered by a network administrator. As such, not all the fields in the Device Information window are editable. If you want to edit data in the Device Information window and find that a field is not immediately editable, use the Options or Edit menu to find the source of the editable data. [CSCdi17321]
By using the Find command from the Search menu, you can locate a specified network device and then remove it permanently by clicking on the Delete button. If you use this method to delete a network device, the following message appears: No records found that match the search pattern xxxx. Although the command you issued was "delete" not "search," the selected device is deleted successfully. [CSCdi15678]
At times you may experience a failure of the Device Management forms after attempting to add entries into several forms randomly. The Device Management application will work properly when you restart it. [CSCdi22123]
The Device Management application provides many windows for entering or accessing information. The windows are related to each other just as network devices are related to each other and to the people who maintain them. Many Device Management fields are filled in with information supplied by the forms windows. So, you should first enter the data required in the windows from the Forms menu (People, Vendors, Contacts, Location, and so forth); then, fill in the remainder of the Device Management windows. For a graphical representation of these relationships, refer to Appendix C, "CiscoWorks Database Tables," in the CiscoWorks User Guide. [CSCdi17318]
The Locations form is designed to accept common combinations of alphanumeric characters. Consequently, if you enter only a blank space for a location name (or some other unlikely name for a location), you may find that you are later unable to select the blank-space name and modify it. Furthermore, if you double-click on the blank-space name in the Locations window, the Details Locations window of the first name in the Locations list will open instead of the Details Locations window of the blank-space. If you encounter this problem, delete the blank-space name; then try entering a new Locations name being sure to enter only alphanumeric characters. [CSCdi24872]
Caveats for the Device Polling application follow.
If you use isql to destroy a device polling table that is being actively polled, the CiscoWorks Device Polling daemon (nmpolld) displays a series of error messages in the Log Manager window. Device polling is unable to continue, and the poll group in the table remains disabled until you restart the Device Polling daemon. [CSCdi08292]
After a new installation of CiscoWorks on NetView for AIX, if you select Monitor>Device Polling>Options>Activate Changes, the Device Polling daemon, nmpolld, fails. To restart the daemon, select Administer>System>Process Manager. When the Process Manager window displays, click on Off to disable the Device Polling daemon. Then click on On to enable the Device Polling daemon. [CSCdi23097]
The Device Polling daemon fails if the database is full and you select the Activate Changes option. Use the SQL command, alter database, to increase the disk space for the database. [CSCdi23182}
The Export Data user interface does not properly acknowledge duplicate columns in a polling table. As a result, the interface does not allow the duplicate column to be deselected in the columns list. To deselect the duplicate column, remove the column data from the file after the column data is exported. [CSCdi16915]
When using the Global Commands Scheduler application to schedule device polling, make sure that you specify when to stop, as well as start, polling. Otherwise, polling will continue indefinitely and, consequently, will occupy disk space for the storage of polled data. When you finish device polling, always set the poll rate to zero to terminate polling. To automate the process, use the Global Commands Scheduler to create two distinct poll commands: one to start polling and another one to stop polling. (Stop polling by resetting the polling table poll rate to zero.)
To start and stop polling within the Global Command Scheduler window, enter the nmpollactivate command in the Cmd Name field. To automate the process of setting up poll scheduling, select the Schedule Polling command from the Tools menu of the Polling Summary application.
Caveats for the Device Software Manager application follow.
The Device Software Manager application cannot find the fully qualified device (FQD) name in the database if the device name was added incorrectly. If you use FQD, make sure the network entity (device name) can respond to the domain name MIB object. In other words, if you use a domain name in the database, make sure the network entity is configured with a domain name. To correctly add a device so that it can be recognized by the database, enter the following command:
ip domain-name name.com
After you correctly add the FQD, you should run the Sync w/Sybase application to copy the device name to the CiscoWorks database. [CSCdi15358]
Domain Manager may not work properly if you attempt to create domains one after another and then add devices to those existing domains. [CSCdi27563]
The Device Software Manager application uses the Flash Image Manager to upgrade run-from-Flash devices (for example, a Cisco 2500). The Flash Image Manager requires the last hop address for the interface which is used for upgrading the image on the device. When the Flash Image Manager runs trace on the router, it may not find the last hop address for the interface selected.
If only one route exists from the router to the TFTP server (workstation), then the last hop address is determined by the Flash Image Manager. If multiple routes exist from the router to the TFTP server, then the last hop address is determined only 50% of the time. If the application is unable to determine the last hop address, it requires you to manually enter the information. [CSCdi24097]
Device Software Manager requires tacacs.access file to be in $NMSROOT/etc even if TACACS is not configured. The tacacs.access file is used only if you specify yes to the TACACS configuration. The work around is to manually create the file. The file contains the following lines:
cisco cisco $enable$ cisco
[CSCdi27840]
In some isolated cases, after you click the Upgrade button in the Device Software Manager window, you may find that the application suddenly quits and a core file is left in your directory. However, the domain is successfully added to the database. If you encounter this problem, retry the operation. You may want to share the core file with TAC for analysis.
[CSCdi25129]
When the Device Software Manager application collects critical information for upgrading the device software, it uses the first VTY line password found in the configuration file. When a device has several VTY lines, you need to ensure that all VTY line passwords are the same (since CiscoWorks cannot differentiate between lines). The console line does not have to have the same password as the VTY password. [CSCdi24455]
Caveats for the Domain Manager application follow.
Copying device information from the Associate Domains list can be troublesome depending on the memory, space, and database configuration of your system. In some cases if you create a new domain and copy devices from an existing domain by selecting them from the Associate Domains list, only the first domain in the list is copied. If you encounter this problem, try copying one domain at a time. [CSCdi24850]
If you create a new domain and attempt to copy multiple existing domains into it, you see the error message:
Could not write to Database - click onClose to exit
However, the only option available to you is to click on a button, called "OK." When you click on the OK button, the application quits. If you encounter this problem, restart Domain Manager. Create a new domain and try copying one domain at a time into the newly created one. This is a known defect and is expected to be fixed in a subsequent release of CiscoWorks. [CSCdi24624]
Caveats for the Environmental Monitor application follow.
The window title of the Environmental Monitor is designed to display the full name of the device being monitored. If the device name is too long and the font for the window title is too large, the text for the device name is truncated in the window. To resolve this issue, you can define a smaller font to be used for the window title. For instructions on changing window fonts, refer to your CiscoWorks User Guide. [CSCdi22121]
Avoid resizing the Help window if you will need ready access to the command buttons of Environmental Monitor. The enlarged Help window overlaps the Environmental Monitor window and clips or obscures the buttons. [CSCdi24947]
Caveats for the Global Command Scheduler follow.
When starting Global Command Scheduler from NetView, the application always lists cscworks as the user. This causes any scheduled job to be owned by the user cscworks and consequently written to the cscworks file in crontabs. However, when you invoke the scheduler from within the Global Command Manager, you see that all scheduled jobs are owned by your own user ID. As a result, you can only delete scheduled jobs by invoking the application in the same way as when you first scheduled them. For example, if you scheduled a job by invoking Global Command Scheduler directly from NetView, you must invoke the application the same way to delete the job. [CSCdi24927]
If you click on the View Cmd button many times, you will see multiple View Cmd windows. Only the topmost of these multiple windows can be exited. Furthermore, the Global Command Scheduler window becomes unusable. If you encounter this problem, quit the application; then retry the operation being careful to click the View Cmd button only once. [CSCdi24852]
The Global Command Scheduler, nmgcmd, will not make a cron file to schedule an event if the file with the user's name is not present in /usr/spool/cron/crontabs. To solve this problem, create a dummy file using the following command:
cat /dev/null > /usr/spool/cron/crontabs/<user-id>
[CSCdi27963]
A caveat for the Health Monitor application follows.
The top panel of the Health Monitor window displays three CPU dials: Now, 1 Min, and 5 Min. Each of these dials is designed to display the CPU load over time. However, in some isolated cases, the 1 Min dial continuously displays 0. This known deficiency is expected to be fixed in a subsequent release. [CSCdi17641]
Caveats to the installation and configuration of CiscoWorks Release 2.1(2) follow.
During installation, the following files are installed into the /usr/lib directory if they are not already there: /X11R5/libXmu.sl, /X11R5/libXaw.sl, /libC.sl, /libC.ansi.sl. These files require less than 0.9 MB of disk space on the device that has /usr/lib mounted on it. Ensure that the device or partition in which /usr/lib is located has enough disk space for these files.
Before installing Sybase as part of your default configuration, confirm that you have enough disk space. When installing Sybase in /usr/nms/sybase, Sybase requires 115 MB of disk space. [CSCdi24637]
If you are performing a new CiscoWorks installation, and a Sybase user entry is already in the
/etc/passwd file, the sybconfig utility will require that the SYBASE environment variable be set to the home directory given in the /etc/passwd entry. If this condition is not met, the sybconfig utility will exit. The sybconfig utility will cause load_nms, and consequently the configuration process will fail on a new installation. The workaround is to remove the Sybase user entry from the /etc/passwd file when installing CiscoWorks and replace it after the installation. [CSCdi16864]
If the Device Polling daemon (nmpolld) is running after a new installation and you attempt to activate changes, the daemon stops. To resolve this problem, access the Process Manager application (Administer>System>Process Mgr) and turn the Device Polling daemon off by clicking on Off. Then turn the daemon back on by clicking the On button. [CSCdi22950]
If the DSQUERY environment variable is set, you will encounter installation problems while creating the database. To avoid installation errors, unset this variable by entering:
For C-shell:
% unsetenv DSQUERY
For K-shell:
$ unset DSQUERY
or set it to SYBASE by entering:
For C-shell:
% setenv DSQUERY SYBASE.
For K-shell:
DSQUERY=<whatevername>export DSQUERY ---(under ksh)
[CSCdi23960]
A caveat for the Login Manager application follows.
When invoking the Change User command within Login Manager, an incorrect login record may appear in the logins table. [CSCdi13536]
Caveats for the Log Manager application follow.
Log Manager may display duplicate records after you rearrange columns in the Log Manager window. If you experience this problem, restart the Log Manager. [CSCdi20624}
If the Sybase dataserver is stopped and restarted after you start the Log Manager application, the Refresh button does not display new messages. The Log Manager does not reestablish the connection to the database once it has been stopped. Restart the Log Manager application to connect to the database. [CSCdi20853]
Caveats for the Path Tool application follow.
In some cases, Path Tool loops several times between two devices that were specified either as source or destinations or found in the middle of a path between two devices. [CSCdi24511]
Network numbers appear in the source and destination list while you are using the resolv+ library. CiscoWorks does not support resolv+. To get past this problem, use a different name resolver with CiscoWorks. [CSCdi16541]
With CiscoWorks 2.1(2), starting Path Tool may take longer than in previous releases. Typically, you may notice the device selection list to be notably slower. In addition, Path Tool may only remain open when it detects a problem discovering a device; otherwise it simply displays the path and quits. [CSCdi24351]
Caveats for the Polling Summary application follow.
Currently, you cannot delete objects from a selected device by using the Delete button. However, you can delete the device name itself. [CSCdi25030]
You may experience unusual behavior while using Device Polling and Polling Summary applications in the following situations:
This behavior occurs when the database transaction log segment is full. However, no error message appears to indicate the log is full. To resolve this problem, exit the application and increase the size of the transaction log segment by running $NMSROOT/etc/enlarge_nms. For more information on enlarge_nms, refer to the CiscoWorks User Guide. [CSCdi23149]
If you move a line to a new interface, the database will not immediately recognize devices on that interface. For example, you may have moved the telephone line that leads to a remote site, from Serial1 to Serial3. If you move a line and want to accurately poll its devices, first run Sync w/Sybase to acknowledge the new devices in the database, then retry the polling operation. [CSCdi17326]
If a device restarts (for example, a router reboots) while it is being polled, an extra data entry might appear and disappear in the Polling Summary window.
Follow these steps to resolve this problem:
Step 1 Quit the Polling Summary application.
Step 2 Select Polling Summary to restart the application.
The problem should not occur again.
If the problem does occur again, follow these steps:
Step 1 In the Device Polling window, select the Poll Rate field and select the pick menu to select a poll rate of 0.
Step 2 Select Options>Activate Changes to send the changes to the device polling daemon.
Step 3 Select File>Quit to quit from Device Polling.
Step 4 Select Device Polling to restart the application.
The extra data entry will not appear in the Polling Summary window. [CSCdi09606]
In order to run reports using the Polling Summary, the tables being polled must be valid, meaning they must contain all the needed MIB objects required to run a specified report. The polling tables used in report generating were created when you initially set up Device Polling.
If you attempt to run a report from the command line, you might encounter an error if the polling table is invalid. Try running reports from the graphical user interface where the various reports are listed in the Tools menu. If the menu item is enabled, the polling table is valid, so the report can be run. If the menu item is disabled, the polling table is invalid. In this case, you must first add the needed MIB objects to the polling table by using the Device Polling application. [CSCdi17323, CSCdi17324, and CSCdi17325]
Caveats for the Security Manager application follow.
The Security Manager application, nmadmin, uses nms as the login id for logging into Sybase. It expects a predefined password for the nms login. If the password is changed for the nms login, it core dumps. To solve the problem, change the password for nms login using following isql commands:
$SYBASE/bin/isql -Usa -P <SA password>
sp_password <existing password>,pZLwutrIqpo,nms
go
[CSCdi27955]
Caveats for the Software Library Manager application follow.
The Software Library Manager and Device Software Manager applications require the following minimal disk space in order to run properly: at least 6 MB (6144 KB) of free space for the /tmp directory and 6 MB (6144 KB) of free space for the /tftpboot directory. To confirm that your system meets the minimal requirements, perform the following steps:
Step 1 Enter the following at the UNIX prompt:
% df
A list of the files on your system and the corresponding available space, similar to the following, will appear:
Step 2 Confirm that you have at least 6 MB (6144 KB) of free space for /tmp and 6 MB free space for /tftpboot.
If, for example, both /tmp and /tftpboot are in the same partition (in other words, /), you need at least 12 MB (12,288 KB) of free space on that file system.
Step 3 If you do not have enough space in the file system, you must find another partition that has enough space and make a symbolic link from that partition to /tmp or /tftpboot.
Step 4 Depending on what you are currently running on your system, if you change the /tmp location, you may need either to reboot your system or to restart your network management platform.
The Software Library Manager application supports only one software image per platform per software version. Cisco recommends importing the enterprise image into the library. Enterprise images include a -k in the release name. If you attempt to import duplicate versions/platform images, the Software Library Manager will request you confirm the image deletion from the library. [CSCdi23795]
When you run the Import from Flash command, you may see an error message indicating that there is inadequate space in the /tftp boot directory even though the directory may have more than sufficient space.
Currently, Flash Image Manager brings the image onto the /tftpboot, moves it to /tmp and then onward to /usr/nms/software but does not release the file handle in /tmp. Unfortunately, this problem is incorrectly conveyed as no space under /tftpboot while it is /tmp.
This is a known defect and is expected to be corrected in a subsequent release of CiscoWorks. [CSCdi24758]
The Software Library Manager does not keep a historical record of the comments field. Consequently, you see only the most recently saved comments field when you open the Software Library Manager window. If you want a permanent record of all the data entered in the Comments field, you need to develop and maintain a separate log. [CSCdi20041]
Caveats for the Sync w/Sybase application follow.
You may see the following error messages when synchronizing your devices using Sync w/Sybase: "ERROR: Could not connect to Sybase server." This error has been observed on several occasions. This message does not cause any problems during the synchronization. After the message comes up, the synchronization continues until completed. [CSCdi25749]
In some cases, Sync w/Sybase may enter a looping sequence in an attempt to synchronize devices. In these cases, Sync w/Sybase is unresponsive because a device did not respond to SNMP queries. If you encounter this problem, try restarting Sync w/Sybase. [CSCdi24288]
When running Sync w/Sybase on a device you added with the AutoInstall Manager application may appear listed as devicename:Serial0 instead of the actual device name. If you encounter this problem, try running Sync w/Sybase again. [CSCdi24789]
Caveats for the TACACS Manager application follow.
Device Software Manager requires tacacs.access file to be in $NMSROOT/etc even if TACACS is not configured. The tacacs.access file is used only if you specify yes to the TACACS configuration. The work around is to manually create the file. The file contains the following lines:
cisco cisco $enable$ cisco
[CSCdi27840]
This section contains some frequently asked questions about CiscoWorks issues. Before contacting a technical support representative, read this section to see if your questions are addressed.
select text1+text2+text3+text4 from ciscolog
where netaddr = z
|
|