Inconsistency in Virtual Circuit Element Assignment Process
(Doc ID 2520395.1)
Last updated on SEPTEMBER 12, 2019
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
There appears to be a hole in the validation process when designing a Virtual Circuit that allows you to bypass the assignment of the Cust_Site component under specific conditions. We have been able to duplicate this behavior when ordering a SIP Virtual Circuit whose connect spec is ETH element to Cust_Site element. Normally, this type of circuit would be built in conjunction with an existing bandwidth circuit, or a new bandwidth being ordered on the same order. In this test scenario, however, we treated it as if there was an existing bandwidth circuit at the Customer's site (EUL), but in reality, no such circuit exists. When designing the Virtual Circuit, we are allowed to select a standard network systems "ETH" element for both the Orig and Term elements.
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