365-575-102 TroubleClearing:
Issue 8.0, July 2002 Page 1 of 2
TAP-153
Clear ‘STS3 Squelch Map Conflict’, ‘STS1 Squelch
Map Conflict’, or ‘Squelch Map Conflict’
NOTE:
An STS3 (or STS1) squelch map conflict (Release 5 and later) or
squelch map conflict (Release 4.1) condition is most likely caused by the
controller circuits being unable to associate any network element's target
identifier (TID) with the value supplied for a source or destination node of a
cross-connection.
NOTE:
The Destination/Source(s) with an STS3 (or STS1) squelch map
conflict or squelch map conflict condition are indicated by an asterisk
(*) appearing immediately before the TID in the report.
NOTE:
The following are possible causes of the STS3 (or STS1) squelch map
conflict or the squelch map conflict condition:
• A condition could have been caused when the network was being
upgraded from Release 3 or 4 to Release 4.1 or later. The pre-upgrade
cross-connections had nonexistent NIDs with their Source/Destination.
• A possible cause is the user entered a nonexistent TID while executing
the CONFIGURATION-Enter-Crossconnect-STS3 (or STS1) or
the CONFIGURATION-Enter-Roll-STS3 (or STS1) command.
• A node was deleted from the ring but not the cross-connections to that
node from the remaining nodes in the ring.
• A possible cause of this condition is that the wrong TID/NID has been
entered when executing the SECURITY-Set-Network Element com-
mand.
1. At the CIT, select the CONFIGURATION-Retrieve-Crossconnec-
tion-STS3 (or STS1) command and execute to obtain an STS-3 (or
STS-1) Cross-Connection Map Report. An example of this report with a
description of the output parameters is provided in Section 11 of this manual.
2. Find the cross-connection with the invalid flag (invalid flag is specified with
*TID).
To Next Page
Loading...
Need help?
General