Last updated on JULY 21, 2016
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
Users want to redesign a new GLR using a CUST_SITE to ROUTER connection spec.
Based on reading the enhancement in the last release we should be able to do this.
The release notes didn’t specify conditions where this will not work with exception of the circuit not being on multiple open orders.
Prod Mgmt: the application should allow this modification.
1. Example is a UNI circuit that hasn’t been designed.
2. The user initially chose a Cust_Site to Router Connection Spec.
3. He then wanted to change it to Cust_Site to Eth_Device.
4. But MSS doesn’t allow the change even when no Elements have been associated.
The expectation is that we can redesign the EVC using the new RUID which has an ETH_DEVICE to Router Connections Spec.
This requires the EVC Connection Spec to be changed to CUST_SITE to Router.
User is not able to make the changes needed for the Connection Specification.
Prod Mgmt Comments
When changing the spec of a connection, both the originating and terminating component types must be the same as those for the existing connection spec.
In procedure above, the connection has already been designed between to customer site components within the network, so allowing you to select any of the
other available specs, which do not go between two customer sites, would invalidate the current design, so it is not allowed.
If you configure another spec between two CUST SITE components, you will be able to select that one to modify the existing spec.
If you are truly trying to change one or both of the component types, this will require a redesign/re-order based upon how this connection was ordered.
As mentioned before, both the Network Rehome and Indirect Rehome capabilities will update the terminating component, along with its type if necessary,
as part of the automated design updates. For either of these features to be successful, the existing template(s) which currently define the service must
support the updated spec as well. For example, in order to update the virtual connection spec from its current CUST SITE to CUST SITE relationship to the
new CUST SITE to ROUTE relationship, the template must be configured to allow this type of relationship for the existing virtual.
This is no different than if you were performing these updates manually with a complete redesign or disc/add, but the template must allow this prior to the
application automatically making these updates for you.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms