Примечания к выпуску для Cisco Cisco MGX 8880 Media Gateway
10
Release Notes for Cisco MGX 8880 Media Gateway Release 5.6.20
OL-23363-04
Limitations, Restrictions, and Notes for 5.6.20
Command Line Interface Access Levels
The following notes pertain to configuring command access levels:
•
Not all command line interface (CLI) commands are changeable, and a command cannot be changed
to CISCO_GP group access level.
to CISCO_GP group access level.
•
Only the switch software is allowed to generate the binary file. This binary file has an authentication
signature which has to be validated before the binary file can be used. Any manual changes to the
file make the file void.
signature which has to be validated before the binary file can be used. Any manual changes to the
file make the file void.
•
If the binary file becomes corrupted, then the command access levels revert back to the default
values during the card bring-up. To recover, repeat the installation process or retain a copy of the
binary file and execute a cnfcli accesslevel install command on that service module.
values during the card bring-up. To recover, repeat the installation process or retain a copy of the
binary file and execute a cnfcli accesslevel install command on that service module.
•
Currently, command names are verified, but an invalid command name might be parsed and added
to the binary file. However, this invalid name is ignored later.
to the binary file. However, this invalid name is ignored later.
•
If replication to standby failed, the installation process failed.
•
The cnfcli accesslevel default command restores all command access levels to default for the
service module that this command is executed on. This command does not remove the binary file,
and this change is not persistent. If the command is executed on the active card of a redundancy pair,
the standby card is not affected. When the card is reset and the binary file exists, it configures from
the binary file when it is brought up.
service module that this command is executed on. This command does not remove the binary file,
and this change is not persistent. If the command is executed on the active card of a redundancy pair,
the standby card is not affected. When the card is reset and the binary file exists, it configures from
the binary file when it is brought up.
Disk Space Maintenance
Because the firmware does not audit the disk space usage nor remove unused files, the disk space in C:
and E: drives must be manually monitored.
and E: drives must be manually monitored.
Manually delete any unused saved configuration files, core files and firmware files, and the configuration
files of the MGX-RPM-PR and MGX-RPM-XF-512 cards to avoid a shortage of disk space required to
store event logs: configuration upload files in the C: drive and the configuration of MGX-RPM-PR and
MGX-RPM-XF-512 cards in the E: drive.
files of the MGX-RPM-PR and MGX-RPM-XF-512 cards to avoid a shortage of disk space required to
store event logs: configuration upload files in the C: drive and the configuration of MGX-RPM-PR and
MGX-RPM-XF-512 cards in the E: drive.
The following steps are recommended to remove files on the system from the active controller card:
Step 1
Change to the directory that needs grooming.
CLI: cd <directory_name>
Step 2
List the directory to identify old files that can be removed and available disk space.
CLI: ll
Step 3
Remove any old files (you might also use wild cards in the filename).
CLI: rm <complete_filename>
Step 4
List the directory to see if the file was removed and disk space is available.
CLI: ll