XEDIA-SECURITY-MIB
File:
XEDIA-SECURITY-MIB.mib (12783 bytes)
Imported modules
Imported symbols
Defined Types
| XsecurityObjConfEntry |
|
| SEQUENCE |
|
|
|
| |
xsecurityObjID |
OBJECT IDENTIFIER |
|
| |
xsecurityObjName |
DisplayString |
|
| |
xsecurityObjInstance |
DisplayString |
|
| |
xsecurityObjReadAdmin |
INTEGER |
|
| |
xsecurityObjWriteAdmin |
INTEGER |
|
| |
xsecurityObjReadFunctAdmin |
INTEGER |
|
| |
xsecurityObjWriteFunctAdmin |
INTEGER |
|
| |
xsecurityObjReadLevels |
BIT STRING |
|
| |
xsecurityObjWriteLevels |
BIT STRING |
|
| |
xsecurityObjRowStatus |
RowStatus |
|
Defined Values
| xediaSecurityMIB |
1.3.6.1.4.1.838.3.8 |
| This module defines objects for management of the 'Security'
mechanism in Xedia devices.
Security Model:
In all cases, a top level, 'object-wide' security check is performed,
followed by the 'instantiated object' (particular instance or row) check,
if specified, followed by the security function (when appropriate),
followed by the required 'parent' security checks, in the same order. |
| MODULE-IDENTITY |
|
|
|
| xsecurityAdmin |
1.3.6.1.4.1.838.3.8.1.1.1 |
| The administrative status of the 'Security mechanism' in the router.
The value 'enabled(1)' indicates that the appropriate security
checks will be performed on all configured objects. The value
'disabled(2)' indicates that no security checks will be performed
on any objects. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
enabled(1), disabled(2) |
|
| xsecurityParentDepth |
1.3.6.1.4.1.838.3.8.1.1.2 |
| The number of 'parent' nodes inwhich the security checks are
performed for any given object. The security checks start at
the endpoint (the actual object requested) and traverse upwards,
checking the immediate parent node, then that parent's parent,
etc., until the maximun number of parents is reached, or there
are no more parents. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
2..32 |
|
| xsecurityFunctionID |
1.3.6.1.4.1.838.3.8.1.1.3 |
| The textual string ID used to determine a specific set of
special customer security functions, when appropriate. Only
OS builds containing customized security functions will take
advantage of this object. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| xsecurityObjConfTable |
1.3.6.1.4.1.838.3.8.1.2.1 |
| A list of security object configuration entries. The number
of entries is representative of the number of objects defined
in the supported mib. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
XsecurityObjConfEntry |
|
| xsecurityObjConfEntry |
1.3.6.1.4.1.838.3.8.1.2.1.1 |
| An entry containing additional management information
applicable to a particular Rip2 interface. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
XsecurityObjConfEntry |
|
|
| xsecurityObjID |
1.3.6.1.4.1.838.3.8.1.2.1.1.1 |
| The Object Identifier of a known object, or a particular instance
of the object. Objects can be end nodes, which contain readable
data, or they can be inner nodes which are only used to identify
the end points. The object ID can be secified by using the complete
OID of an object, with the exact OID digits making up the instance
portion of the object when needed. In all cases, an 'end of ID'
marker of decimal '999' will be used to separate the base objectID
from the instance portion of the whole OID.
When '.0' instance information is specified, the 'object-wide' security
levels of the object are modified. But, when specific instance
information is specified, the security levels of a particular instance
are modifed. Then,only requests with exactly matching instance
information are validated against the specified levels.
The '.0' also indicates where the 'base' oid ends and the instance
information (if any) begins. This way, it is possible to identify
high level nodes with specific instances matching lower level nodes.
ie: ifEntry.1 --> ifEntry.999.1 filters out all instances of '1'.
The '999' is necessary since ifEntry.1 looks exactly the same
as ifIndex.
1.3.6.1.2.1.2.2.1 ifEntry
1.3.6.1.2.1.2.2.1.1 ifIndex |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
OBJECT IDENTIFIER |
|
|
| xsecurityObjName |
1.3.6.1.4.1.838.3.8.1.2.1.1.2 |
| The mib name of the specificed object. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| xsecurityObjInstance |
1.3.6.1.4.1.838.3.8.1.2.1.1.3 |
| The instance portion of the specified object. The
OID digits are represented in a readable string format. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| xsecurityObjReadAdmin |
1.3.6.1.4.1.838.3.8.1.2.1.1.4 |
| The 'Read' administrative status of the 'Security mechanism' for
an individual object. The value 'enabled(1)' indicates that the
appropriate security checks will be performed on all access to
the spcified object. The value 'disabled(2)' indicates that
no security checks will be performed for the specified object,
although, all expected 'parent' security checks will still be
performed. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
enabled(1), disabled(2) |
|
| xsecurityObjWriteAdmin |
1.3.6.1.4.1.838.3.8.1.2.1.1.5 |
| The 'Write' administrative status of the 'Security mechanism' for
an individual object. The value 'enabled(1)' indicates that the
appropriate security checks will be performed on all access to
the spcified object. The value 'disabled(2)' indicates that
no security checks will be performed for the specified object,
although, all expected 'parent' security checks will still be
performed. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
enabled(1), disabled(2) |
|
| xsecurityObjReadFunctAdmin |
1.3.6.1.4.1.838.3.8.1.2.1.1.6 |
| The 'Read' administrative status of the 'Security Function mechanism'
for an individual object. The value 'enabled(1)' indicates that the
appropriate security functions will be called on all access to
the spcified object. The value 'disabled(2)' indicates that
no security functions will be called for the specified object. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
enabled(1), disabled(2) |
|
| xsecurityObjWriteFunctAdmin |
1.3.6.1.4.1.838.3.8.1.2.1.1.7 |
| The 'Write' administrative status of the 'Security Function mechanism'
for an individual object. The value 'enabled(1)' indicates that the
appropriate security functions will be called on all access to
the spcified object. The value 'disabled(2)' indicates that
no security functions will be called for the specified object. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
enabled(1), disabled(2) |
|
| xsecurityObjReadLevels |
1.3.6.1.4.1.838.3.8.1.2.1.1.8 |
| The bit mask associated with a particular object for 'reading'
and 'viewing'. The levels of security indicate which community
entries have read access to the variable. The level matches
the index, or entry number of the community table. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
BIT STRING |
s10(0), s9(1), s8(2), s7(3), s6(4), s5(5), s4(6), s3(7), s2(8), s1(9) |
|
| xsecurityObjWriteLevels |
1.3.6.1.4.1.838.3.8.1.2.1.1.9 |
| The bit mask associated with a particular object for 'writinging'
and 'setting'. The levels of security indicate which community
entries have read access to the variable. The level matches
the index, or entry number of the community table. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
BIT STRING |
s10(0), s9(1), s8(2), s7(3), s6(4), s5(5), s4(6), s3(7), s2(8), s1(9) |
|
| xsecurityObjRowStatus |
1.3.6.1.4.1.838.3.8.1.2.1.1.10 |
| This object is used to add and remove entries from the
table. It is important to note that the '.0' entry, which
represents the 'object level' can not be added or deleted,
they simply always exists. However the 'instanciated' table
rows can be added or deleted as necessary. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
RowStatus |
|
|
| xsecurityCompliance |
1.3.6.1.4.1.838.3.8.2.1.1 |
| The compliance statement for all agents that support this
MIB. A compliant agent implements all objects defined in this
MIB. |
| Status: current |
Access: read-create |
| MODULE-COMPLIANCE |
|
|
|
| xsecurityAllGroup |
1.3.6.1.4.1.838.3.8.2.2.1 |
| The set of all accessible objects in this MIB. |
| Status: current |
Access: read-create |
| OBJECT-GROUP |
|
|
|