Cisco Cisco MGX 8880 Media Gateway
15
Release Notes for Cisco MGX 8880 Software Release 5.3.00
Part Number OL-8892-01 Revision B0, October 23, 2006
Limitations, Restrictions, and Notes for 5.3.00
•
PORT SCT 6—Policing disabled, used for PNNI ports.
•
CARD and PORT SCT 52—Policing enabled on PNNI, disabled on MPLS
•
PORT SCT 53—Policing disabled on PNNI and MPLS
•
PORT SCT 54— Policing enabled on PNNI, disabled on MPLS
•
PORT SCT 55—Policing disabled on PNNI and MPLS
The following are checksums for the new AXSM-E SCT file:
•
AXSME_SCT.PORT.5.V1: Checksum is = 0x793c56d0= 2033997520
•
AXSME_SCT.PORT.6.V1: Checksum is = 0xe92db9a5= 3912087973
•
AXSME_SCT.PORT.52.V1: Checksum is = 0x51241b7a= 1361320826
•
AXSME_SCT.PORT.53.V1: Checksum is = 0x34bdf8b9= 884865209
•
AXSME_SCT.PORT.54.V1: Checksum is = 0xb5df2c5c= 3051301980
•
AXSME_SCT.PORT.55.V1: Checksum is = 0xc5d355c8= 3318961608
•
AXSME_SCT.CARD.5.V1: Checksum is = 0x793c56d0= 2033997520
•
AXSME_SCT.CARD.52.V1: Checksum is = 0x972810ac= 2535985324
Limitations, Restrictions, and Notes for 5.3.00
This section includes information about limitations, restrictions, and notes pertaining to MGX
Release 5.3.00.
Release 5.3.00.
•
Due to granularity limitations in the AXSM-E hardware, cell traffic does not reach the configured
peak cell rate (PCR) rate when weighted fair queuing (WFQ) is enabled. You must configure
connections that have WFQ enabled with a PCR of 101 percent of the actual required rate. Available
bit rate (ABR) has the same Qbin priority as the unspecified bit rate (UBR) in the SCT tables. In this
case, ABR and UBR share excess bandwidth if WFQ is enabled.
peak cell rate (PCR) rate when weighted fair queuing (WFQ) is enabled. You must configure
connections that have WFQ enabled with a PCR of 101 percent of the actual required rate. Available
bit rate (ABR) has the same Qbin priority as the unspecified bit rate (UBR) in the SCT tables. In this
case, ABR and UBR share excess bandwidth if WFQ is enabled.
•
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.