Reference record for OID 1.3.6.1.4.1.2272.1.81.1.0.1

parent

1.3.6.1.4.1.2272.1.81.1.0 (rcBfdTmpNotifications)

node code

1

node name

rcBfdTmpSessUp

dot oid

1.3.6.1.4.1.2272.1.81.1.0.1

type

NOTIFICATION-TYPE

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) rapidCity(2272) rcMgmt(1) rcBfd(81) rcBfdTmpMib(1) rcBfdTmpNotifications(0) rcBfdTmpSessUp(1)}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) rapidCity(2272) rapidcityfoo(1) rcBfd(81) rcBfdTmpMib(1) rcBfdTmpNotifications(0) rcBfdTmpSessUp(1)}

...skipped...

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) rapidCity(2272) rcMgmt(1) rcBfd(81) rcBfdTmpMib(1) rcBfdTmpNotifications(0) rcBfdTmpSessUp(1)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) rapidCity(2272) rapidcityfoo(1) rcBfd(81) rcBfdTmpMib(1) rcBfdTmpNotifications(0) rcBfdTmpSessUp(1)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) rapidCity(2272) rcMgmt(1) rcBfd(81) rcBfdTmpMib(1) rcBfdTmpNotifications(0) rcBfdTmpSessUp(1)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) rapidCity(2272) rapidcityfoo(1) rcBfd(81) rcBfdTmpMib(1) rcBfdTmpNotifications(0) rcBfdTmpSessUp(1)}

...skipped...

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) rapidCity(2272) rcMgmt(1) rcBfd(81) rcBfdTmpMib(1) rcBfdTmpNotifications(0) rcBfdTmpSessUp(1)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) rapidCity(2272) rapidcityfoo(1) rcBfd(81) rcBfdTmpMib(1) rcBfdTmpNotifications(0) rcBfdTmpSessUp(1)}

iri oid

/iso/identified-organization/dod/internet/private/enterprise/rapidCity/rcMgmt/rcBfd/rcBfdTmpMib/rcBfdTmpNotifications/rcBfdTmpSessUp

/iso/identified-organization/dod/internet/private/enterprise/rapidCity/rapidcityfoo/rcBfd/rcBfdTmpMib/rcBfdTmpNotifications/rcBfdTmpSessUp

...skipped...

/iso/org/dod/internet/private/enterprise/rapidCity/rcMgmt/rcBfd/rcBfdTmpMib/rcBfdTmpNotifications/rcBfdTmpSessUp

/iso/org/dod/internet/private/enterprise/rapidCity/rapidcityfoo/rcBfd/rcBfdTmpMib/rcBfdTmpNotifications/rcBfdTmpSessUp

/iso/org/dod/internet/private/enterprises/rapidCity/rcMgmt/rcBfd/rcBfdTmpMib/rcBfdTmpNotifications/rcBfdTmpSessUp

/iso/org/dod/internet/private/enterprises/rapidCity/rapidcityfoo/rcBfd/rcBfdTmpMib/rcBfdTmpNotifications/rcBfdTmpSessUp

...skipped...

/iso/iso-identified-organization/dod/internet/private/enterprises/rapidCity/rcMgmt/rcBfd/rcBfdTmpMib/rcBfdTmpNotifications/rcBfdTmpSessUp

/iso/iso-identified-organization/dod/internet/private/enterprises/rapidCity/rapidcityfoo/rcBfd/rcBfdTmpMib/rcBfdTmpNotifications/rcBfdTmpSessUp

Description by mibdepot

This notification is generated when the
bfdSessState object for one or more contiguous
entries in bfdSessTable are about to enter the up(2)
state from some other state. The included values of
bfdSessDiag MUST both be set equal to this
new state (i.e: up(1)). The two instances of
bfdSessDiag in this notification indicate the range
of indexes that are affected. Note that all the indexes
of the two ends of the range can be derived from the
instance identifiers of these two objects. For the
cases where a contiguous range of sessions
have transitioned into the up(1) state at roughly
the same time, the device SHOULD issue a single
notification for each range of contiguous indexes in
an effort to minimize the emission of a large number
of notifications. If a notification has to be
issued for just a single bfdSessEntry, then
the instance identifier (and values) of the two
bfdSessDiag objects MUST be the identical.

Parsed from file RC-BFD-TMP-MIB.mib.txt
Company: avaya
Module: RC-BFD-TMP-MIB

Information by mibdepot

rcBfdTmpSessUp NOTIFICATION-TYPE
    OBJECTS     { rcBfdTmpSessDiag, 
                  rcBfdTmpSessDiag  
                }
    STATUS      current
    DESCRIPTION
        "This notification is generated when the
         bfdSessState object for one or more contiguous
         entries in bfdSessTable are about to enter the up(2)
         state from some other state. The included values of
         bfdSessDiag MUST both be set equal to this
         new state (i.e: up(1)).  The two instances of
         bfdSessDiag in this notification indicate the range
         of indexes that are affected.  Note that all the indexes
         of the two ends of the range can be derived from the
         instance identifiers of these two objects.  For the
         cases where a contiguous range of sessions
         have transitioned into the up(1) state at roughly
         the same time, the device SHOULD issue a single
         notification for each range of contiguous indexes in
         an effort to minimize the emission of a large number
         of notifications.  If a notification has to be
         issued for just a single bfdSessEntry, then
         the instance identifier (and values) of the two
         bfdSessDiag objects MUST be the identical."
    ::= { rcBfdTmpNotifications 1 }

First Registration Authority (recovered by parent 1.3.6.1.4.1.2272)

Sharon Chisholm

Brothers (1)