Cisco MGX 8850 PXM45 Release Notes page 35

•
•
•
•
•
•
•
•
•
•
•
•
•
•
Disk Space Maintenance
•
OL-2914-01 Rev D0, July 3, 2003
If LMI is configured, port header length cannot be changed.
–
Single ended connections can only originate from FRSM12. Single-ended connections
–
terminating on FRSM12 are not supported.
Single-ended SPVC can only originate from FRSM12-T3E3. Termination on SPVC of
–
single-ended SPVC is not supported.
– chanType cannot be modified.
– If Port header length is 2 bytes, the maximum DLCI number is 1023.
If Port header length is 2 bytes, the restricted DLCIs are 0, 1007, and 1023.
If Port header length is 4 bytes, the restricted DLCIs are 0 and 8257535.
To add Frame Forward connection, the port should be of type Frame Forward.
For Frame Forward port, the maximum connections is 1.
For Frame Relay port, the maximum connections is 4000.
The maximum number of frame relay connections is 16K.
If the connection is in loopback, it cannot be modified.
CIR can only be 0 for uBR connections.
If CIR == 0, BC should also be zero, BE, and zeroCirConEir should be nonzero.
If CIR != 0, BC should be nonzero.
If chanType is Frame Forward, chanFECNconfig should be setEFCIzero, chanCLPtoDEmap should
be ignoreCLP, chanDEtoCLPmap should not be mapCLP.
If chanType is NIW or NIWReplacem chanFECNconfig should be setEFCIzero, chanCLPtoDEmap
should not be setDEzero or setDEone.
If chanType is frSIW_transparent or frSIW_translate, chanCLPtoDEmap should not be ignoreCLP.
Maximum connections depending on LMI type:
– Annex A/D LMI, 2-byte header, FRF 1.2 not enabled: 898 conns
– Annex A/D LMI, 2-byte header, FRF 1.2 enabled: 1000 conns (port max)
– Annex A/D LMI, 4-byte header, FRF 1.2 not enabled: 640 conns
– Annex A/D LMI, 4-byte header, FRF 1.2 enabled: 4000 conns (port max)
Strata LMI, 2-byte header, FRF 1.2 not enabled: 560 conns
–
Strata LMI, 2-byte header, FRF 1.2 enabled: 1000 conns (port max)
–
As the firmware does not audit the disk space usage and remove unused files, the disk space in C:
and E: drives should be manually monitored. Any unused saved configuration files, core files and
firmware files, and the configuration files of the MGX-RPM-PR-256/512 and MGX-RPM-XF-512
cards should be promptly deleted manually. Following this procedure allows you to avoid shortage
of disk space to successfully store event logs, configuration upload files in the C: drive and the
configuration of MGX-RPM-PR-256/512 and MGX-RPM-XF-512 cards in the E: drive.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
Limitations, Restrictions, and Notes
35