Known issues

The following information details existing device issues that have been discovered within other releases. In most cases, a resolution is included to address the issue.

• The following hardware information is not reported by the device; memory and file system information are disabled in the device package:

  • Memory

  • File system information

  • Inventory (SNMP)

  • IP addresses (SNMP)

• The model name is now obtained from the GIGAMON-SNMP-MIB for SNMP (falling back to standard oids for pre 8.x firmware), and the device banner for terminal. If the banner is customized, this may prevent mapping to a sysObjectID value in the GigamonModels.xml, and fail device discovery via terminal protocols.

• If the device is completely unmanaged and later rediscovered, the startup file set for the current management instance will change. The previous file must be deleted manually after a successful push to startup following rediscovery, since the Device ID (which is part of the filename) will have changed. This approach is required due to the lack of vendor support for specifying the source and destination filenames for the install –cfg command.

• Configlets and remediation are not supported by this device class, since the text representation of the configuration cannot be pushed to the device, which is a preprequisite for configlet pushes.

• The managed device model(s) appear to only support a single read-only community string.

• The show diag command has been observed to disconnect communication sessions with the device after partial output. As a result, some diagnostic information that may assist with resolving missing hardware information is currently unavailable to the driver.