Cisco Cisco ONS 15600 Multiservice Switching Platform (MSSP)
7
Release Notes for Cisco ONS 15600 Release 7.0.4
OL-12391-01
Resolved Caveats for Release 7.0.x
Resolved Caveats for Release 7.0.x
The following caveats were resolved in Release 7.0.x.
Maintenance and Administration
CSCsc91343
A new command to set a card's ESM Admin State was added to CTS for MFG testing requirements given
it was not added in Maverick when the ESM feature was originally developed.
it was not added in Maverick when the ESM feature was originally developed.
CSCei44592
You can have no more than 113 DCC links in one area ID. For example, with 128 DCC Links provisioned
within one area ID, 14 DCC links gray out in CTC. To avoid this issue divide the 128 DCCs into multiple
area IDs (at least two). This issue is resolved in Release 7.0.
within one area ID, 14 DCC links gray out in CTC. To avoid this issue divide the 128 DCCs into multiple
area IDs (at least two). This issue is resolved in Release 7.0.
CSCei14295
After restoring a previously backed up database, the restoral of the PM history database is not
time-based, but rather, position-based. The PM history database is stored or retrieved to or from
position-dependent time slots from the present PM period. Thus, PM history backed up 24 hours prior
to the restore will show the PM history without acknowledging the missing day. This issue is resolved
in Release 7.0.
time-based, but rather, position-based. The PM history database is stored or retrieved to or from
position-dependent time slots from the present PM period. Thus, PM history backed up 24 hours prior
to the restore will show the PM history without acknowledging the missing day. This issue is resolved
in Release 7.0.
CSCei37179
Rarely, when an ASAP card is participating in a DCC tunnel, and working and protect spans both fail,
the ASAP card might stop responding, sometimes followed by a reset. When this occurs there is no
resulting traffic loss, and protection switching continues to function. To recover ASAP card
responsiveness a soft reset of the card might be necessary. This issue is resolved in Release 7.0.
the ASAP card might stop responding, sometimes followed by a reset. When this occurs there is no
resulting traffic loss, and protection switching continues to function. To recover ASAP card
responsiveness a soft reset of the card might be necessary. This issue is resolved in Release 7.0.
CSCsb46157
When the first and second ports of a PIM are provisioned as GIGE and, at a minimum, the second port
is in a circuit, or, when the third and fourth ports of a PIM are provisioned as GIGE and, at a minimum,
the fourth port is in a circuit, packets might be dropped on a soft reset of the associated ASAP card. To
prevent this, avoid provisioning a GIGE port next to another GIGE port. This issue is resolved in
Releases 6.1 and 7.0.
is in a circuit, or, when the third and fourth ports of a PIM are provisioned as GIGE and, at a minimum,
the fourth port is in a circuit, packets might be dropped on a soft reset of the associated ASAP card. To
prevent this, avoid provisioning a GIGE port next to another GIGE port. This issue is resolved in
Releases 6.1 and 7.0.