Discovery of a CE device changes Site ASN and silently changes Site SOO config

(Doc ID 961597.1)

Last updated on AUGUST 31, 2016

Applies to:

Oracle Communications IP Service Activator - Version: 5.2.1
Information in this document applies to any platform.

Symptoms

Overview:
When a CE device linked to a Layer 3 site is discovered it changes the site's ASN to the ASN of the CE device. If the L3 site has two or more interfaces with SOO configured to auto-generate, the SOO community is changed and config is pushed out without a transaction record

Steps To Reproduce:
1. Create a L3 VPN and a Site with two or more interfaces, EBGP connectivity, and ensure the SOO route map is set to "generate", and commit
2. Ensure the config goes installed on the PE device(s)
3. Drag a CE device into the Site that has a different ASN to the Site, and commit
4. Re-discover the CE device, note that the Site ASN has now changed
5. Monitor the audit trails, the new soo community string will be pushed out to the PE device(s)

Business Impact:
This scenario caused an unexpected service outage for a customer

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms