Reference record for OID 1.3.6.1.4.1.9.9.498

parent

1.3.6.1.4.1.9.9 (ciscoMgmt)

node code

498

node name

ciscoEntityRedunMIB

dot oid

1.3.6.1.4.1.9.9.498

type

OBJECT IDENTIFIER

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoEntityRedunMIB(498)}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoEntityRedunMIB(498)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoEntityRedunMIB(498)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoEntityRedunMIB(498)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoEntityRedunMIB(498)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoEntityRedunMIB(498)}

iri oid

/iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoEntityRedunMIB

/iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoEntityRedunMIB

/iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoEntityRedunMIB

/iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoEntityRedunMIB

/iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoEntityRedunMIB

/iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoEntityRedunMIB

iri by oid_info

/ISO/Identified-Organization/6/1/4/1/9/9/498

Description by circitor

This management information module supports
configuration, control and monitoring of redundancy
protection for various kinds of components on
Cisco managed devices.

It is meant to be generic enough to handle basic
redundancy control and monitoring for many types of
redundant member components and redundancy architectures
as long as there is an Entity MIB entPhysicalIndex and
entPhysicalVendorType assigned to each member component.

It is designed so that the tables can be augmented in
other extension MIBS which build upon this MIB by
adding additional objects that may be specific to a
particular type of redundancy or member component.

This MIB can also be used in cases where some types of
redundancy groups and members don't require explicit
user configuration. One example may be redundant fan
assemblies. In those cases, the managed system should
internally assign group and member indexes, so that
it can provide read-only access to the group and member
tables. This allows MIB monitoring for these types of
redundant entities.

Parsed from file CISCO-ENTITY-REDUNDANCY-MIB.mib
Module: CISCO-ENTITY-REDUNDANCY-MIB

Description by mibdepot

This management information module supports
configuration, control and monitoring of redundancy
protection for various kinds of components on
Cisco managed devices.

It is meant to be generic enough to handle basic
redundancy control and monitoring for many types of
redundant member components and redundancy architectures
as long as there is an Entity MIB entPhysicalIndex and
entPhysicalVendorType assigned to each member component.

It is designed so that the tables can be augmented in
other extension MIBS which build upon this MIB by
adding additional objects that may be specific to a
particular type of redundancy or member component.

This MIB can also be used in cases where some types of
redundancy groups and members don't require explicit
user configuration. One example may be redundant fan
assemblies. In those cases, the managed system should
internally assign group and member indexes, so that
it can provide read-only access to the group and member
tables. This allows MIB monitoring for these types of
redundant entities.

Parsed from file CISCO-ENTITY-REDUNDANCY-MIB.my.txt
Company: None
Module: CISCO-ENTITY-REDUNDANCY-MIB

Description by cisco

This management information module supports
configuration, control and monitoring of redundancy
protection for various kinds of components on
Cisco managed devices.

It is meant to be generic enough to handle basic
redundancy control and monitoring for many types of
redundant member components and redundancy architectures
as long as there is an Entity MIB entPhysicalIndex and
entPhysicalVendorType assigned to each member component.

It is designed so that the tables can be augmented in
other extension MIBS which build upon this MIB by
adding additional objects that may be specific to a
particular type of redundancy or member component.

This MIB can also be used in cases where some types of
redundancy groups and members don't require explicit
user configuration. One example may be redundant fan
assemblies. In those cases, the managed system should
internally assign group and member indexes, so that
it can provide read-only access to the group and member
tables. This allows MIB monitoring for these types of
redundant entities.

Information by circitor

ciscoEntityRedunMIB MODULE-IDENTITY
    LAST-UPDATED    "200510010000Z"
    ORGANIZATION    "Cisco Systems, Inc."
    CONTACT-INFO
                    "Cisco Systems, Inc.
                     Customer Service
                     Postal: 170 W. Tasman Drive
                             San Jose, CA  95134-1706
                             USA
                     Tel: +1 800 553-NETS
                     Email: [email protected]"

    DESCRIPTION
        "This management information module supports 
         configuration, control and monitoring of redundancy 
         protection for various kinds of components on 
         Cisco managed devices. 

         It is meant to be generic enough to handle basic 
         redundancy control and monitoring for many types of 
         redundant member components and redundancy architectures
         as long as there is an Entity MIB entPhysicalIndex and 
         entPhysicalVendorType assigned to each member component.

         It is designed so that the tables can be augmented in
         other extension MIBS which build upon this MIB by 
         adding additional objects that may be specific to a 
         particular type of redundancy or member component.

         This MIB can also be used in cases where some types of
         redundancy groups and members don't require explicit 
         user configuration. One example may be redundant fan
         assemblies. In those cases, the managed system should 
         internally assign group and member indexes, so that 
         it can provide read-only access to the group and member 
         tables. This allows MIB monitoring for these types of 
         redundant entities.
        "
    REVISION      "200510010000Z"
    DESCRIPTION
         "The initial version of this MIB module."
    ::= { ciscoMgmt 498 }

Information by cisco_v1

ciscoEntityRedunMIB OBJECT IDENTIFIER ::= { ciscoMgmt 498 }

Information by oid_info

Vendor: Cisco
Module: CISCO-ENTITY-REDUNDANCY-MIB

[Automatically extracted from oidview.com]

Information by mibdepot

ciscoEntityRedunMIB MODULE-IDENTITY
    LAST-UPDATED    "200510010000Z"
    ORGANIZATION    "Cisco Systems, Inc."
    CONTACT-INFO
                    "Cisco Systems, Inc.
                     Customer Service
                     Postal: 170 W. Tasman Drive
                             San Jose, CA  95134-1706
                             USA
                     Tel: +1 800 553-NETS
                     Email: [email protected]"

    DESCRIPTION
        "This management information module supports 
         configuration, control and monitoring of redundancy 
         protection for various kinds of components on 
         Cisco managed devices. 

         It is meant to be generic enough to handle basic 
         redundancy control and monitoring for many types of 
         redundant member components and redundancy architectures
         as long as there is an Entity MIB entPhysicalIndex and 
         entPhysicalVendorType assigned to each member component.

         It is designed so that the tables can be augmented in
         other extension MIBS which build upon this MIB by 
         adding additional objects that may be specific to a 
         particular type of redundancy or member component.

         This MIB can also be used in cases where some types of
         redundancy groups and members don't require explicit 
         user configuration. One example may be redundant fan
         assemblies. In those cases, the managed system should 
         internally assign group and member indexes, so that 
         it can provide read-only access to the group and member 
         tables. This allows MIB monitoring for these types of 
         redundant entities.
        "
    REVISION      "200510010000Z"
    DESCRIPTION
         "The initial version of this MIB module."
    ::= { ciscoMgmt 498 }

Information by cisco

ciscoEntityRedunMIB MODULE-IDENTITY
    LAST-UPDATED    "200510010000Z"
    ORGANIZATION    "Cisco Systems, Inc."
    CONTACT-INFO
                    "Cisco Systems, Inc.
                     Customer Service
                     Postal: 170 W. Tasman Drive
                             San Jose, CA  95134-1706
                             USA
                     Tel: +1 800 553-NETS
                     Email: [email protected]"

    DESCRIPTION
        "This management information module supports 
         configuration, control and monitoring of redundancy 
         protection for various kinds of components on 
         Cisco managed devices. 

         It is meant to be generic enough to handle basic 
         redundancy control and monitoring for many types of 
         redundant member components and redundancy architectures
         as long as there is an Entity MIB entPhysicalIndex and 
         entPhysicalVendorType assigned to each member component.

         It is designed so that the tables can be augmented in
         other extension MIBS which build upon this MIB by 
         adding additional objects that may be specific to a 
         particular type of redundancy or member component.

         This MIB can also be used in cases where some types of
         redundancy groups and members don't require explicit 
         user configuration. One example may be redundant fan
         assemblies. In those cases, the managed system should 
         internally assign group and member indexes, so that 
         it can provide read-only access to the group and member 
         tables. This allows MIB monitoring for these types of 
         redundant entities.
        "
    REVISION      "200510010000Z"
    DESCRIPTION
         "The initial version of this MIB module."
    ::= { ciscoMgmt 498 }

First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Children (3)

Brothers (645)

To many brothers! Only 100 nearest brothers are shown.