Cisco Cisco MGX 8880 Media Gateway Release Notes
22
Release Notes for Cisco MGX 8880 VXSM Software Release 5.4.21
OL-19207-01
Limitations, Restrictions, and Notes for 5.4.21
•
The VXSM cards, when installed for the first time or after clearing the slot configuration, create a
default configuration. The creation of a default configuration involves writing large amount of data
to the hard disk in the node.
default configuration. The creation of a default configuration involves writing large amount of data
to the hard disk in the node.
When multiple VXSM cards are installed simultaneously or the configuration of multiple VXSM
slots are cleared simultaneously, one or more VXSM cards could fail to be installed. This potential
failure results in following recommendations (refer to CSCed12646):
slots are cleared simultaneously, one or more VXSM cards could fail to be installed. This potential
failure results in following recommendations (refer to CSCed12646):
–
Install VXSM cards, using the setrev command, one at a time. Install another VXSM after the
earlier one is completely installed and is Active.
earlier one is completely installed and is Active.
–
Clear the VXSM slot configuration using the clrsmcnf command (with no option where the slot
primary software version is preserved) one at a time. Wait until the VXSM rebuilds after
clearing its slot configuration (without clearing the slot primary software version) before
clearing the slot configuration of another VXSM slot.
primary software version is preserved) one at a time. Wait until the VXSM rebuilds after
clearing its slot configuration (without clearing the slot primary software version) before
clearing the slot configuration of another VXSM slot.
Upgrading the VISM-PR Image
If you are upgrading the VISM-PR image to Release 3.2.1x or later and the PXM1E or PXM45 image
from Release 4.x or earlier to Release 5.x, first upgrade the VISM-PR cards. Then, upgrade the PXM1E
or PXM45 cards in the same node.
from Release 4.x or earlier to Release 5.x, first upgrade the VISM-PR cards. Then, upgrade the PXM1E
or PXM45 cards in the same node.
Do not configure the new VISM features until you have fully upgraded the network. After you upgrade
your network to PXM1E or PXM45 Release 5.x or later and VISM-PR to Release 3.2.1x or later, apply
the standard upgrade process.
your network to PXM1E or PXM45 Release 5.x or later and VISM-PR to Release 3.2.1x or later, apply
the standard upgrade process.
Higher Level Logical Link Limits
The numbers of logical links in the higher levels of the PNNI hierarchy is limited to 30 per level when
the complex node configuration is turned on. The limit is essential to reduce the processing time involved
in finding the bypasses between the logical links. Each time a significant change occurs in bandwidth in
one of the links within the peer group, the bypass calculation is triggered and the bypasses are usually
found from one logical link to another.
the complex node configuration is turned on. The limit is essential to reduce the processing time involved
in finding the bypasses between the logical links. Each time a significant change occurs in bandwidth in
one of the links within the peer group, the bypass calculation is triggered and the bypasses are usually
found from one logical link to another.
If there are n logical links, the calculation involves finding n*n bypasses.
If the number of logical links n is large, a lot of processing time is used to calculate the bypasses. Limit
the number of logical links per level to 30. To control the number, configure the appropriate number of
aggregation tokens for the outside links for that peer group.
the number of logical links per level to 30. To control the number, configure the appropriate number of
aggregation tokens for the outside links for that peer group.
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.