Representation of Juniper AE interfaces is incorrectly displayed (Doc ID 2013853.1)

Last updated on JUNE 05, 2015

Applies to:

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

Symptoms

 In a Juniper M-series device a Gigabit ethernet subinterface can be aggregated into a "ae" (type 161 "ieee8023adLag") interface. The interfaces in the MIB map as follows;

Interfaces
public .1.3.6.1.2.1.2.2.1.2.25 OCTETSTRING 'ge-0/1/0'
public .1.3.6.1.2.1.2.2.1.2.26 OCTETSTRING 'ge-0/1/0.32767'
public .1.3.6.1.2.1.2.2.1.2.28 OCTETSTRING 'ge-1/1/0'
public .1.3.6.1.2.1.2.2.1.2.29 OCTETSTRING 'ge-1/1/0.32767'
public .1.3.6.1.2.1.2.2.1.2.33 OCTETSTRING 'ge-1/1/0.2'
public .1.3.6.1.2.1.2.2.1.2.102 OCTETSTRING 'ae0.32767'

Mapping
public .1.3.6.1.2.1.31.1.2.1.3.25.0 INTEGER 1
public .1.3.6.1.2.1.31.1.2.1.3.26.25 INTEGER 1
public .1.3.6.1.2.1.31.1.2.1.3.28.0 INTEGER 1
public .1.3.6.1.2.1.31.1.2.1.3.29.28 INTEGER 1
public .1.3.6.1.2.1.31.1.2.1.3.33.28 INTEGER 1
public .1.3.6.1.2.1.31.1.2.1.3.102.26 INTEGER 1
public .1.3.6.1.2.1.31.1.2.1.3.102.29 INTEGER 1


It can be seen that the interfaces are mapping as follows;

ge-0/1/0 -----> ge-0/1/0.32767  --------
                              |---> ae0.32767
ge-1/1/0 -----> ge-1/1/0.32767 --------

 

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