IPSA Is Not Using The Primary Preferred Loopback Address For a New Juniper Router (Doc ID 1904639.1)

Last updated on JULY 08, 2014

Applies to:

Oracle Communications IP Service Activator - Version 7.2.0 and later
Information in this document applies to any platform.

Symptoms

We have added a new node in deviceX and strangely, even if we used the primary loopback address when we added the node after discovery, the one showing in IPSA is still the third loopback which is 3.3.3.3.

oracle@deviceX> show configuration interfaces lo0
unit 0 {
  family inet {
  filter {
  input protect-RE;
  }
  address 1.1.1.1/32 {
  primary;
  preferred;
  }
  address 2.2.2.2/32;
  address 3.3.3.3/32;
  }

 

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