ALCATEL-IND1-POLICY-MIB: View SNMP OID List / Download MIB

VENDOR: ALCATEL


 Home MIB: ALCATEL-IND1-POLICY-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, ALCATEL-IND1-BASE, SNMPv2-TC

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).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
   alcatelIND1PolicyMIB 1.3.6.1.4.1.6486.800.1.2.1.14.1
       alcatelIND1PolicyMIBObjects 1.3.6.1.4.1.6486.800.1.2.1.14.1.1
Branch for policy manager application objects
           serverPolicyDecision 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.1
This object allows an NMS application to influence the policy managers treatment of existing policy decisions that were established by the policy manager. By setting recachePolicies, an NMS can cause the policy manager to reload all its policies from the current primary LDAP server. By setting flushPolicies, all the policies are deleted by the policy manager.
           rsvpDefaultPolicy 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.2
This object allows an NMS application to define the agent action when there are no policy servers available to a switch. When this object is set to accept(1), the policy manager in the switch will allow all RSVP control message requests. When set to deny(2), the policy manager will deny all RSVP control message requests.
           policyManagerEventTableSize 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.3
This object defines the size of the policy manager event table. When this object is set, the subagent adjusts the event table to meet the size defined.
           directoryServerTable 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4
This table contains information related to the LDAP-based directory server from the perspective of the policy manager.
               directoryServerEntry 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1
An entry in the directory server table. Each entry represents a directory server instance to the policy manager.
                   directoryServerAddress 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.1
The IP Address of an LDAP server. The policy manager uses this object combined with the directory server port number to uniquely identify an LDAP server to use for directory queries and updates.
                   directoryServerPort 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.2
This object contains the TCP port number, which, along with the directory server IP address, identifies the LDAP server.
                   directoryServerPreference 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.3
This object represents the relative preference of the server entry. The higher the value of this object, the greater the preference the policy manager places on using this server for LDAP queries. This object is used when the policy manager uses server selection based on the configured preference.
                   directoryServerAuthenticationType 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.4
The value of this object specifies what authentication mechanism the LDAP server expects. For simplePassword(1), the policy manager uses the directoryServerPassword object for each LDAP query. kerberos and publicKey mechanisms are currently unsupported. The none(0) value directs the policy manager to use the anonymous method for LDAP queries.
                   directoryServerUserId 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.5
This object only has significance when the directoryServerAuthenticationType has a value of simplePassword(1). This simple display string is used by the policy manager in LDAP queries and updates.
                   directoryServerPassword 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.6
This object only has significance when the directoryServerAuthenticationType has a value of simplePassword(1). This simple display string is used by the policy manager in LDAP queries and updates.
                   directoryServerPublicKey 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.7
This object only has significance when the directoryServerAuthenticationType has a value of publicKey(3), which is not a currently supported value
                   directoryServerSearchbase 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.8
This object specifies the base object required for LDAP search operations. This object represents, in distinguished name format, the point where server searches start. Generally, this object represents the base object of the organization.
                   directoryServerCacheChange 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.9
This object allows an NMS application to influence the policy managers cache of policy-related data when this server becomes the primary LDAP server selected for the switch. Setting this object to recachePolicy(1) conveys to the policy manager that the policy class object should be obtained from the LDAP server represented by this table entry when this server becomes the primary LDAP server. By setting this object to none, the policy manager will use the existing policy and policy rule cache rather than reloading the policy data from this server. In the case where there is no policy cache (for instance, when the switch powers up) the policy manager will attempt to reload the policy class cache even if this object is set to none.
                   directoryServerLastChange 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.10
This object contains the value of sysUpTime at the time of the last creation, deletion or modification of an object in this table entry.
                   directoryServerAdminStatus 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.11
This object specifies the desired administrative state of the directory server. The up and down states control the policy managers decision to user the server for LDAP queries and updates.
                   directoryServerOperStatus 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.12
This object identifies the current operational state of the LDAP server. Semantics of this object closely resemble the ifOperStatus definition, however, the LDAP application layer is NOT modeled as an interface as defined by RFC2233.
                   directoryServerRowStatus 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.13
This object is used to create a new table entry or modify or delete an existing table entry in this table.
                   directoryServerEnableSSL 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.4.1.14
This object enables or disables SSL for the LDAP server.
           policyEventTable 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.5
This table contains significant events related to the operation of the policy manager.
               policyEventEntry 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.5.1
An entry in the policy manager event table.
                   policyEventIndex 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.5.1.1
This object uniquely identifies the event record.
                   policyEventCode 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.5.1.2
This object identifies the event that occurred. The internal protocol error and LDAP error events are rollup events that represent a collection of events with similar characteristics. The internal error event occurs due to software resource or logic problems; the LDAP error occurs because of LDAP init, search, format, protocol or other similar errors.
                   policyEventDetailString 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.5.1.3
This object gives details about the event that took place. Included in the string are (potentially) fields that provide more specific fault location and isolation, context resolution, and event (error) instance information.
                   policyEventTime 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.5.1.4
This object contains the value of sysUpTime at the time the event occurred.
           policyRuleNamesTable 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.6
This table contains information that identifies the LDAP-based policy rules defined on a directory server that are pushed by the policy manager to the QoS&F manager for making policy decisions.
               policyRuleNamesEntry 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.6.1
An entry in the policy rules table. Each entry represents the name of a policy rule on the directory server. The policy manager uses these names to build the correct policy rules.
                   policyRuleNamesIndex 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.6.1.1
This object is a unique index identifying the policyRuleNames entry.
                   policyRuleNamesName 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.6.1.2
This object defines the name of the policyRule that the policy manager will use to build a switch policy. The name coincides with the directory server class name equivalent.
                   policyRuleNamesRowStatus 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.6.1.3
Deprecated (to avoid proliferation of control planes) - rules to be changed should be updated in LDAP and flushed/pushed to switches accordingly.
                   policyRuleOperStatus 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.6.1.4
This object is used to convey to an NMS the state of the policy. A value of up implies that the policy rule has been pushed to the QoS / filtering manager (i.e. the PEP). A value of down means the policy is invalid, so it was not pushed to the QoS / filtering manager. A value of notReady means this rule is valid, but not currently active (PVP not active, etc).
           policyStatsTable 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.7
This table defines the objects maintained by the policy manager representing statistics available on a per policy server instance. The objects in this table correspond directly to the similarly named objects in <draft-white-slapm-mib-00.txt>, except that the objects in the draft are scalars. Note that the I-D is now RFC 2758, and experimental category RFC. There are semantic differences from RFC 2758 for some objects - the differences are detailed in the DESCRIPTION clauses. Some objects behave differently from the RFC because of our combined PDP/PEP implementation. Note that RFC 2758 applies to hosts more than switches.
               policyStatsEntry 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.7.1
An entry in the policy manager stats table.
                   policyStatsAddress 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.7.1.1
IP address of the policy server related to these statistics
                   policyStatsServerPort 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.7.1.2
TCP port number of the policy server related to these statistics
                   policyStatsQueryCount 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.7.1.3
The query count gives the total number of times a policy repository was queried by the policy decision point. The policy repository is the LDAP server where policies are stored.
                   policyStatsAccessCount 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.7.1.4
Total number of times that a policy repository was accessed with respect to a policy agent. The policy decision point (PDP) in this implementation accesses the repository via LDAP. The access count includes all operations required to access the policy rules (including role evaluations and discrete policy entry accesses.) The value of this object will increment on repository access.
                   policyStatsSuccessAccessCount 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.7.1.5
Total number of successful policy repository accesses. This value increments if a known attribute has been discovered in a repository search, regardless of its PDP processing status. This object will increment less than policyStatsAccessCount on most repository accesses, based on repository structure and what roles match the policy decision point.
                   policyStatsNotFoundCount 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.7.1.6
Total number of policy repository accesses that resulted in an entry not being located. Not found counts increment on protocol search failures and other attribute lookup problems. Generally, policyStatsNotFoundCount increments only in error cases.
           policyNotificationTable 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.8
This table contains an association between an event ID and the notification method that the policy manager uses to convey to an NMS that the event occurred.
               policyNotificationEntry 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.8.1
An entry in the policy manager notification table.
                   policyNotificationIndex 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.8.1.1
This object is a unique index identifying the policyNotification entry. This index corresponds to the same value as the policyEvent.
                   policyNotificationCode 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.8.1.2
This object defines the notification method used to convey information about switch events to the NMS. The notification code allows for multiple notification methods, updated by an NMS by setting the appropriate method corresponding to the event index.
                   policyEventCount 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.8.1.3
Total number of times that this event was recognized. This value increments for each event occurance. No advertised management facility exists to clear these history counters. This object is intended to be a hint to management applications as to the past operating history of a switch even if entries are no longer present in the policyEventTable.
           policyManagerSwitchIdentifier 1.3.6.1.4.1.6486.800.1.2.1.14.1.1.9
The value of this object type identifies the switch with a identifier that is unique through out the network This identifier is stored on the switch and the Directory Server for policies that are specific to this switch. If this variable is changed on the switch then the Directory Server also must be changed correspondingly. Changing the variable on the switch and not making the corresponding change on the Directory Server will render the policies defined for this switch unusable.The syntax of this variable is macAddress:Date:Time. Example: xx:xx:xx:xx:xx:xx:yyyymmdd:hhmmss
       alcatelIND1PolicyMIBConformance 1.3.6.1.4.1.6486.800.1.2.1.14.1.2
Branch for policy manager application conformance information
           alcatelIND1PolicyMIBGroups 1.3.6.1.4.1.6486.800.1.2.1.14.1.2.1
Branch for policy manager application units of conformance
           alcatelIND1PolicyMIBCompliances 1.3.6.1.4.1.6486.800.1.2.1.14.1.2.2
Branch for policy manager application compliance statements
 policyManagerTrapDesc 1.3.6.1.4.1.6486.800.1.3.2.3.1
         policyEventNotification 1.3.6.1.4.1.6486.800.1.3.2.3.1.0.1
The policyEventNotification allows the switch to notify an NMS when significant events happen. The NMS can then investigate and perform appropriate control functions. Other tables allow the NMS app to zone in on the problem as part of a proactive monitoring system by the NMS application.
 policyManagerTrapObjs 1.3.6.1.4.1.6486.800.1.3.2.3.2
     policyTrapEventDetailString 1.3.6.1.4.1.6486.800.1.3.2.3.2.1
Details about the event that took place
     policyTrapEventCode 1.3.6.1.4.1.6486.800.1.3.2.3.2.2
The code of the event