Cisco Cisco ONS 15454 SDH Multiservice Provisioning Platform (MSPP) Notas de publicación

Descargar
Página de 38
 
3
Release Notes for Cisco ONS 15454 SDH Release 4.7
OL-5946-01
  Caveats
DWDM Cards
DDTS # CSCef15415
RMON TCAs are not raised on the TXPP_MR_2.5G client port after a hardware reset. To see this issue, 
provision two nodes with TXPP_MR_2.5G (TXP-1 and TXP-2) as follows.
Step 1
Connect the TXP-1 DWDM-A trunk to the TXP-2 DWDM-A trunk.
Step 2
Connect the TXP-1 DWDM-B trunk to the TXP-2 DWDM-B trunk.
Step 3
Create an external fiber loopback on the TXP-1 client.
Step 4
Connect the TXP-2 client to a traffic generator.
Step 5
Provision 1G FC payload on the TXP-1 and TXP-2.
Step 6
Ensure that traffic is running smoothly.
Step 7
Provision RMON thresholds using TL1 for all TXPP_MR_2.5G ports (client and trunks).
Step 8
Apply a hardware reset to the TXPP_MR_2.5G.
After the card reboots, only DWDM-A and DWDM-B (trunk) port RMON TCAs are raised in the CTC 
History pane. RMON TCAs for port 1 (client) are not raised. This issue will not be resolved.
DDTS # CSCef15452
RMON TCAs are not raised when the RMON history is cleared on TXPP_MR_2.5G card. To see this 
issue, provision two nodes with TXPP_MR_2.5G (TXP-1 and TXP-2) as follows.
Step 1
Connect the TXP-1 DWDM-A trunk to the TXP-2 DWDM-A trunk.
Step 2
Connect the TXP-1 DWDM-B trunk to the TXP-2 DWDM-B trunk.
Step 3
Create an external fiber loopback on the TXP-1 client.
Step 4
Connect the TXP-2 client to a traffic generator.
Step 5
Provision 1G FC payload on the TXP-1 and TXP-2.
Step 6
Ensure that traffic is running smoothly.
Step 7
Provision RMON thresholds using TL1 for all TXPP_MR_2.5G ports (client and trunks).
Step 8
While the traffic is running reset the RMON history by clicking the Clear button in the CTC Payload PM 
pane.
RMON TCAs are not raised for any port. This issue will not be resolved.
DDTS # CSCef18649
LDCC and MS-DCC do not work at OC12/STM4 line rates (client and trunk side). Use SDCC or 
RS-DCC (D1..D3) at OC12/STM4 line rates. This issue will be resolved in a future release.