SONET Assignments Getting Merged Together on Change Order Assignment
(Doc ID 2104344.1)
Last updated on MARCH 14, 2019
Applies to:
Oracle Communications MetaSolv Solution - Version 6.2.1 and laterInformation in this document applies to any platform.
Symptoms
In 6.2.1
ACTUAL BEHAVIOUR:
Some SONET assignments blocks are getting merged together. They are assigned to the same ring, but should not be showing as locked together and appear on the CLR as one block.
This works correctly on new designs where the circuit is brand new. However, when a change order comes through on the circuit which has in-service SONET assignments and a user adds another one, the VTs lock, regardless of whether or not add new facility is used.
EXPECTED BEHAVIOUR:
On a change order when new SONET assignment/s is made for a circuit which is already having some SONET assignments the previous assignments should not merge/lock with the new assignment and the new assignment should come as a separate SONET block. The previous blocks should not get disturbed.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |