XEDIA-SECURITY-MIB: View SNMP OID List / Download MIB
VENDOR: XEDIA CORPORATION
Home | MIB: XEDIA-SECURITY-MIB | |||
---|---|---|---|---|
Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
Object Name | OID | Type | Access | Info |
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. |
||
xsecurityObjects | 1.3.6.1.4.1.838.3.8.1 | |||
xsecurityGeneral | 1.3.6.1.4.1.838.3.8.1.1 | |||
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. |
||
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 parents parent, etc., until the maximun number of parents is reached, or there are no more parents. |
||
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. |
||
xsecurityObjectTables | 1.3.6.1.4.1.838.3.8.1.2 | |||
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. |
||
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. |
|||
xsecurityObjID | 1.3.6.1.4.1.838.3.8.1.2.1.1.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 |
||
xsecurityObjName | 1.3.6.1.4.1.838.3.8.1.2.1.1.2 |
The mib name of the specificed object. |
||
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. |
||
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. |
||
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. |
||
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. |
||
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. |
||
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. |
||
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. |
||
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. |
||
xsecurityConformance | 1.3.6.1.4.1.838.3.8.2 | |||
xsecurityCompliances | 1.3.6.1.4.1.838.3.8.2.1 | |||
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. |
||
xsecurityGroups | 1.3.6.1.4.1.838.3.8.2.2 | |||
xsecurityAllGroup | 1.3.6.1.4.1.838.3.8.2.2.1 |
The set of all accessible objects in this MIB. |