Reference record for OID 1.3.6.1.4.1.3199.10


parent
1.3.6.1.4.1.3199 (shasta)
node code
10
node name
shastaExperiment
dot oid
1.3.6.1.4.1.3199.10
type
OBJECT-IDENTITY
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) shasta(3199) shastaExperiment(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) shasta(3199) shastaExperiment(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) shasta(3199) shastaExperiment(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) shasta(3199) shastaExperiment(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) shasta(3199) shastaExperiment(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) shasta(3199) shastaExperiment(10)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/shasta/shastaExperiment
  • /iso/identified-organization/dod/internet/private/enterprises/shasta/shastaExperiment
  • /iso/org/dod/internet/private/enterprise/shasta/shastaExperiment
  • /iso/org/dod/internet/private/enterprises/shasta/shastaExperiment
  • /iso/iso-identified-organization/dod/internet/private/enterprise/shasta/shastaExperiment
  • /iso/iso-identified-organization/dod/internet/private/enterprises/shasta/shastaExperiment
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/3199/10

    Description by mibdepot

    shastaExperiment provides a root object identifier
    from which experimental MIBs may be temporarily
    based. MIBs are typicially based here if they
    fall in one of two categories
    1) are IETF work-in-process MIBs which have not
    been assigned a permanent object identifier by
    the IANA.
    2) are shasta work-in-process which has not been
    assigned a permanent object identifier by the
    shasat assigned number authority, typicially because
    the mib is not ready for deployment.

    NOTE WELL: support for MIBs in the shastaExperiment
    subtree will be deleted when a permanent object
    identifier assignment is made.

    Parsed from file SHASTA-MIB.my.txt
    Company: None
    Module: SHASTA-MIB

    Description by circitor

    shastaExperiment provides a root object identifier
    from which experimental MIBs may be temporarily
    based. MIBs are typicially based here if they
    fall in one of two categories
    1) are IETF work-in-process MIBs which have not
    been assigned a permanent object identifier by
    the IANA.
    2) are shasta work-in-process which has not been
    assigned a permanent object identifier by the
    shasat assigned number authority, typicially because
    the mib is not ready for deployment.

    NOTE WELL: support for MIBs in the shastaExperiment
    subtree will be deleted when a permanent object
    identifier assignment is made.

    Parsed from file SHASTA-MIB.mib
    Module: SHASTA-MIB

    Information by oid_info

    Vendor: Shasta Networks
    Module: SHASTA-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    shastaExperiment OBJECT-IDENTITY STATUS current DESCRIPTION "shastaExperiment provides a root object identifier from which experimental MIBs may be temporarily based. MIBs are typicially based here if they fall in one of two categories 1) are IETF work-in-process MIBs which have not been assigned a permanent object identifier by the IANA. 2) are shasta work-in-process which has not been assigned a permanent object identifier by the shasat assigned number authority, typicially because the mib is not ready for deployment. NOTE WELL: support for MIBs in the shastaExperiment subtree will be deleted when a permanent object identifier assignment is made." ::= { shasta 10 }

    Information by circitor

    shastaExperiment OBJECT-IDENTITY STATUS current DESCRIPTION "shastaExperiment provides a root object identifier from which experimental MIBs may be temporarily based. MIBs are typicially based here if they fall in one of two categories 1) are IETF work-in-process MIBs which have not been assigned a permanent object identifier by the IANA. 2) are shasta work-in-process which has not been assigned a permanent object identifier by the shasat assigned number authority, typicially because the mib is not ready for deployment. NOTE WELL: support for MIBs in the shastaExperiment subtree will be deleted when a permanent object identifier assignment is made." ::= { shasta 10 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.3199)

    Alles Anthony

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.3199.10.28 ssg5000ChassisMIB 3 198 This MIB provides a means to monitor the status of a SSG
    system's health.

    Brothers (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.3199.1 shastaMgmt 0 0 shastaMgmt is the main subtree for new mib development.