SONET Rings Assignments Are Not Staying At Their Designed Positions in Connection Design
(Doc ID 1940838.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
Issue Reported on MSS Version 6.2.1build 348:
On a SONET Network System with ring topology, when a connection is assigned at a specific position in one of the ring segments, the application does not assign the connection to the same position in the other segments.
E.g When making a DS3 assignment on position 2 with a vacant position 1 on the 201(facility designation) connection, the SONET connection is getting the DS3 in the next available vacant position (1) on the 101(facility designation) connection, rather than on the position that was assigned on the 201 connection.It seems that MSS is not keeping the the 101 and 201 connections in sync with the DS3 assignments on each position.
This was working as expected in earlier MSS versions like 6.0.16.
Changes
MSS version change from 6.0.to 6.2
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 |
| Changes |
| Cause |
| Solution |
| References |