Troubleshooting guide

10
Special Considerations
LSCle00509 PVC
Deleting one PVC hangs up MMA when hundreds of PVCs are used.
If hundreds of PVCs are created on a single port, the deleting of one PVC can take a long time. The
result will be an SNMP timeout to the Net Management tool that you are using to delete the PVC.
The delay could be several minutes when over 100 PVCs are created on a given port.
LSCle01083 HP OpenView
A bug in HP OpenView limits collections to less than 20 variables.
Data collection fails with collections set up for more than 20 variables. In compliance with the
SNMP standard, the LightStream 2020 software drops such requests.
Workaround: When setting up a data collection by using HP OpenView, limit the collection to
fewer than 20 variables.
LIGle00038 LynxOS
The tar utility is usable with floppy disk, but it generates errors.
If you attempt to use tar on a floppy drive (for example tar xvf /dev/sd1) when no diskette is
present in the drive, various uninformative error messages appear on the console. Similar error
messages appear when you use a disk that has not been formatted for an IBM PS/2 (Models 50, 60,
70, 80 and compatibles). Furthermore, if you use a floppy disk with media errors, the software
process using the device may hang, preventing access to the floppy or terminal where the tar
command is being run.
Workaround: Reboot the network processor.
LIGle00117 Bandwidth Allocation
Bandwidth allocation does not check egress port capacity.
LSCle00500 Release 1 Medium-Speed Control Processors
Release 1 medium-speed card counts receive errors when a cable is not attached.
When the receive port on a Release 1 medium-speed card has no cable attached or is attached to an
unterminated cable, the receive error counts are incremented (if that port is configured, high
error-rate traps appear on the console).
LSCle00645 Install
The ckswinstall command (for verifying a software installation) has two confusing aspects.
1 The ckswinstall utility reports spurious permission mismatches on directories under /usr/app.
2 When you use the ckswinstall command to verify an update distribution (for instance
Release 2.0.8), ckswinstall only verifies the software in the update. On a system running an
update, most of the software in use is from the original release, so ckswinstall should also be run
on that original release (for example, Release 2.0.7). When you run ckswinstall on the underlying
release, spurious errors are reported against software that was upgraded as part of the update.