Guest

Preview Tool

Cisco Bug: CSCul91511 - [WSE] OTU clients doesn't squelch for alarms if trunk s/w lpbked

Last Modified

Mar 06, 2014

Products (1)

  • Cisco ONS 15454 Series Multiservice Provisioning Platforms

Known Affected Releases

9.810

Description (partial)

Symptom:
OTU clients doesn't Squelch for alarms if trunk has s/w(terminal) loopback

Conditions:
Observed in the below condition:

1. Have a OTU1e P2P setup with client Squelch mode set to Squelch.
Test==OTU1e(WSE)======WSE(OTU1e)---loopback.
2.From testset inject alams(LOS/LOF) on N.end client, N.end client will squelch due to trunk AIS(as expected)
3. now with alarm on N.end client, apply terminal loopback on N.end trunk.
4. Squelch alarm clears and client starts sending power.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.