Cisco Cisco MGX 8880 Media Gateway Release Notes
23
Release Notes for Cisco MGX 8880 VXSM Software Release 5.4.21
OL-19207-01
Limitations, Restrictions, and Notes for 5.4.21
•
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-512 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-512 and MGX-RPM-XF-512 cards in the E: drive.
files of the MGX-RPM-PR-512 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-512 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
Saving Configurations
The system keeps only the two most recent copies of the saved system configuration under the C:/CNF
directory. You can use FTP to transfer all of the saved configurations under C:/CNF to their local server
for future reference. All files under C:/CNF are not replicated over to the standby controller card under
any circumstances.
directory. You can use FTP to transfer all of the saved configurations under C:/CNF to their local server
for future reference. All files under C:/CNF are not replicated over to the standby controller card under
any circumstances.
Using the clrsmcnf Command
These notes pertain to the clrsmcnf command:
•
We do not recommend executing clrsmcnf on more than one card at a time
•
For the clear service module configuration feature, if there is a controller card switchover before the
clear service module configuration operation is complete, the clrsmcnf command must be re-issued
to ensure that the configuration is completely cleared to avoid an incomplete cleanup.
clear service module configuration operation is complete, the clrsmcnf command must be re-issued
to ensure that the configuration is completely cleared to avoid an incomplete cleanup.