The following details existing device issues that have been discovered with other releases. A resolution is included to address the issue, if available.

  • Non-volatile storage and filesystem information are not obtainable using SNMP or the command line interface for the 8.1.0.22 software version. A placeholder is returned with the flash partition name, but size and usage are not listed.

  • The configuration restore-defaults command is not used as part of pushing a text configuration, since in almost all cases the managing Device Server will not be on the same subnet as the device. This command clears all settings except for the in-band IP address, which can result in loss of connectivity. As a result, some configuration commands may be listed with warnings in the job results, since these settings are already present.

  • Certain commands in the mgmt category are listed with a # prefix in the resulting text configuration, although these commands are legal from the command line interface when the prefix is omitted. These commands are skipped during a configuration push because the device treats this character as an invalid command.

  • An FTP transfer service must be configured for this device.

  • The binary configuration push is service-affecting, since the configuration restore-remote command reboots the device after receiving the configuration from the Device Server.

  • The managing account for the device must have an access-level of security or SNMP/Account Rolls cannot be performed.

  • Account rolls transfer the access level of the original account to the new one when the names change.

  • Default accounts cannot be removed. This impacts account credential rolls in the following ways:

    • Jobs that define new, equivalent accounts will show a message in the scheduler that the old account cannot be removed.

    • Jobs that use a default account as the new account name will simply change the password of this account before removing the non-default account.