XEDIA-POLICY-MIB
AI MIB Summary
The XEDIA-POLICY-MIB enables SNMP-based configuration and monitoring of routing policy definitions, including match conditions, action sets, and policy application states, specifically within Xedia networking hardware. This module provides granular visibility into the operational status and parameter values of traffic steering rules to facilitate automated policy enforcement and troubleshooting.
This module defines objects for the management of Routing Policies in Xedia devices.
Main OID:
xediaPolicyMIB.1.3.6.1.4.1.838.3.10
114
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
114 total| Object Name |
|---|
xediaPolicyMIBThis module defines objects for the management of Routing Policies in Xedia devices. MODULE-IDENTITY .1.3.6.1.4.1.838.3.10 |
xpolicyObjects OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.10.1 |
xpolicyGeneral OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.10.1.1 |
xpolicyCounts OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.10.1.2 |
xpolicyRxCounts OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.10.1.2.1 |
xpolicyNumRxConfiguredTotalThe total number of configured 'receive' policies.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.1.1 |
xpolicyNumRxConfiguredValidRepresents the number of configured 'receive' policies that have a RowStatus of 'active'. This means that they are configured correctly without any conflicts among the elements in the row.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.1.2 |
xpolicyNumRxConfiguredInValidRepresents the number of configured 'receive' policies that have a RowStatus of 'notReady'. This means that they are configured, but have conflicts among the elements in the row.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.1.3 |
xpolicyNumRxInUseTotalRepresents the number of 'receive' policies that are currently being used by the run-time application. Normally this number is the same as the number of Configured Valid Policies.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.1.4 |
xpolicyNumRxInUseBGPRepresents the number of BGP 'receive' policies that are currently being used by the run-time application.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.1.5 |
xpolicyNumRxInUseOSPFRepresents the number of OSPF 'receive' policies that are currently being used by the run-time application.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.1.6 |
xpolicyNumRxInUseRIPRepresents the number of RIP 'receive' policies that are currently being used by the run-time application.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.1.7 |
xpolicyNumRxInUseStaticRepresents the number of static 'receive' policies that are currently being used by the run-time application.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.1.8 |
xpolicyTxCounts OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.10.1.2.2 |
xpolicyNumTxConfiguredTotalThe total number of configured 'send' policies.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.2.1 |
xpolicyNumTxConfiguredValidRepresents the number of configured 'send' policies that have a RowStatus of 'active'. This means that they are configured correctly without any conflicts among the elements in the row.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.2.2 |
xpolicyNumTxConfiguredInValidRepresents the number of configured 'send' policies that have a RowStatus of 'notReady'. This means that they are configured, but have conflicts among the elements in the row.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.2.3 |
xpolicyNumTxInUseTotalRepresents the number of 'send' policies that are currently being used by the run-time application. Normally this number is the same as the number of Configured Valid Policies.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.2.4 |
xpolicyNumTxInUseBGPRepresents the number of BGP 'send' policies that are currently being used by the run-time application.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.2.5 |
xpolicyNumTxInUseOSPFRepresents the number of OSPF 'send' policies that are currently being used by the run-time application.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.2.6 |
xpolicyNumTxInUseRIPRepresents the number of RIP 'send' policies that are currently being used by the run-time application.ro Integer32 .1.3.6.1.4.1.838.3.10.1.2.2.7 |
xpolicyTables OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.10.2 |
xpolicyRouting OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.10.2.1 |
xpolicyReceiveTableThis entity's Route Policy Receive table. SEQUENCE OF XpolicyReceiveEntry .1.3.6.1.4.1.838.3.10.2.1.1 |
xpolicyReceiveEntryAn entry to the Route Policy Receive Table. XpolicyReceiveEntry .1.3.6.1.4.1.838.3.10.2.1.1.1 |
xpolicyRxProtocolThe protocol from which the update was received.ro Enumeration .1.3.6.1.4.1.838.3.10.2.1.1.1.1 |
xpolicyRxPeerThe destination IP address of the routing update. If it is zero, then all peers are accepted.ro IpAddress .1.3.6.1.4.1.838.3.10.2.1.1.1.2 |
xpolicyRxNameA unique name for this entry, including the optional priority number, which can be represented in dotted notation. When used, the priority numbers allow hiearchical matching. Format of the string is: <name>.<priority> Examples of strings: name, name.1, name.1.1, name.2ro XPolicyName .1.3.6.1.4.1.838.3.10.2.1.1.1.3 |
xpolicyRxAddrStartThe base of the IP Address range to match in routing update destinations.rw IpAddress .1.3.6.1.4.1.838.3.10.2.1.1.1.4 |
xpolicyRxAddrEndThe end of the IP Address range to match in routing update destinations.rw IpAddress .1.3.6.1.4.1.838.3.10.2.1.1.1.5 |
xpolicyRxAsStringA string describing a complete, or partial 'Autonomyous System' inwhich to perform matches. This string uses a limited form of regular expression syntax to define what values of an AS path to match. The special characters used are '^' and '$' to specify 'start' and 'end' respectively. 100 - a path with 100 in it ^100$ - exactly the path of 100 (adjacent AS) ^100 - any path starting with 100 100$ - any path ending with 100 100.200 - a path with the sequence 100.200 in it. note: this is only valid for routes sourced from BGP.rw XPolicyAsString .1.3.6.1.4.1.838.3.10.2.1.1.1.6 |
xpolicyRxCommunityIdAllows matching on one of the integers listed in the community attrubute list. This is only valid for routes sourced from BGP.rw INTEGER('00'h..'ffffffff'h) .1.3.6.1.4.1.838.3.10.2.1.1.1.7 |
xpolicyRxReceiveOptionReceive action/options taken on 'matching' entries.rw Enumeration .1.3.6.1.4.1.838.3.10.2.1.1.1.8 |
xpolicyRxLocalPrefA positive four byte integer defining the preference to a matched routes. Higher values assign greater preference. Internal routes use 0xffffffff. note: It is only used for BGP.rw Integer32 .1.3.6.1.4.1.838.3.10.2.1.1.1.9 |
xpolicyRxRowStatusThis object is used to add and remove entries from the table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.838.3.10.2.1.1.1.10 |
xpolicyRxPrefixMinMinimum length of IP Address prefix to match in routing update destinations.rw INTEGER .1.3.6.1.4.1.838.3.10.2.1.1.1.11 |
xpolicyRxPrefixMaxMaximum length of IP Address prefix to match in routing update destinations.rw INTEGER .1.3.6.1.4.1.838.3.10.2.1.1.1.12 |
xpolicySendTableThis entity's Route Policy Send table. SEQUENCE OF XpolicySendEntry .1.3.6.1.4.1.838.3.10.2.1.2 |
xpolicySendEntryAn entry to the Route Policy Table. XpolicySendEntry .1.3.6.1.4.1.838.3.10.2.1.2.1 |
xpolicyTxProtocolThe protocol identifying where the update will be sent.ro Enumeration .1.3.6.1.4.1.838.3.10.2.1.2.1.1 |
xpolicyTxPeerThe destination IP address of the routing update. If zero, then all peers receive them. For OSPF and RIP, this value should be zero. BGP should not use 0.ro IpAddress .1.3.6.1.4.1.838.3.10.2.1.2.1.2 |
xpolicyTxNameA unique name for this entry, including the optional priority number, which can be represented in dotted notation. When used, the priority numbers allow hiearchical matching. Format of the string is: <name>.<priority> Examples of strings: name, name.1, name.1.1, name.2ro XPolicyName .1.3.6.1.4.1.838.3.10.2.1.2.1.3 |
xpolicyTxSrcProtocolThe protocol identifying the origin of the update. Often this 'src protocol will be the same as the TX Protocol index. This allows routes learned by BGP to be filtered towards other BGP routes.rw Enumeration .1.3.6.1.4.1.838.3.10.2.1.2.1.4 |
xpolicyTxSrcProtSubTypeThe protocol sub-type discription. Currently, this only applies to OSPF entries.rw Enumeration .1.3.6.1.4.1.838.3.10.2.1.2.1.5 |
xpolicyTxAddrStartThe base of the IP Address range to match in routing update destinations.rw IpAddress .1.3.6.1.4.1.838.3.10.2.1.2.1.6 |
xpolicyTxAddrEndThe end of the IP Address range to match in routing update destinations.rw IpAddress .1.3.6.1.4.1.838.3.10.2.1.2.1.7 |
xpolicyTxAsStringA string describing a complete, or partial 'Autonomyous System' inwhich to perform matches. This string uses a limited form of regular expression syntax to define what values of an AS path to match. The special characters used are '^' and '$' to specify 'start' and 'end' respectively. 100 - a path with 100 in it ^100$ - exactly the path of 100 (adjacent AS) ^100 - any path starting with 100 100$ - any path ending with 100 100.200 - a path with the sequence 100.200 in it. note: this is only valid for routes sourced from BGP.rw XPolicyAsString .1.3.6.1.4.1.838.3.10.2.1.2.1.8 |
xpolicyTxCommunityIdAllows matching on one of the integers listed in the community attrubute list. This is only valid for routes sourced from BGP.rw INTEGER('00'h..'ffffffff'h) .1.3.6.1.4.1.838.3.10.2.1.2.1.9 |
xpolicyTxSendOptionSend action/options taken on 'matching' entries. Never, indicates that routes within the range are not sent to the peer. Normal, allows routes within the specified range to be sent to the peer. Aggregate adds the specified range to routes that are currently within the specified range. In the aggregate case, the range must be a power of two.rw Enumeration .1.3.6.1.4.1.838.3.10.2.1.2.1.10 |
xpolicyTxMEDThe 'Multi-Exit-Descriminator'. A lower value assigns a higher preference to the route. Normally, the MED attribute ia attached to all matched routes. Except in the case of 0xffffffff, which means the MED will not be sent. note: It is only used for BGP. If it is used (>0), then the 'xpolicyTxSendOption' can NOT be set to 'never'.rw Integer32 .1.3.6.1.4.1.838.3.10.2.1.2.1.11 |
xpolicyTxMEDAutoAdmininstative status for calculating the 'Multi-Exit-Descriminator' using IGP_metric + 1.rw Enumeration .1.3.6.1.4.1.838.3.10.2.1.2.1.12 |
xpolicyTxAsPrependThe number of times to prepend the router's AS to the transmitted AS path in updates to the peer for all matching routes. note: It is only used for BGP. If it is used (>0), then the 'xpolicyTxSendOption' can NOT be set to 'never'.rw Integer32 .1.3.6.1.4.1.838.3.10.2.1.2.1.13 |
xpolicyTxSendCommunityIdThe value that is added to the community attribute for all matched routes. note: It is only used for BGP. If it is used (>0), then the 'xpolicyTxSendOption' can NOT be set to 'never'.rw INTEGER('00'h..'ffffffff'h) .1.3.6.1.4.1.838.3.10.2.1.2.1.14 |
xpolicyTxIgpMetricThe metric used for IGP.rw Integer32 .1.3.6.1.4.1.838.3.10.2.1.2.1.15 |
xpolicyTxIgpMetricTypeType of metric being used. Currently, only for defining OSPF internal and external routes.rw Enumeration .1.3.6.1.4.1.838.3.10.2.1.2.1.16 |
xpolicyTxIgpMetricAutoAdministrative status for generating an 'auto' metric. If set to localPref, the igp's metric is igpMetric - localPref. If set to MED, the the igp's metric is igpMetric + MED. If set to igp, then the entry controls routes imported from one IGP to another.rw Enumeration .1.3.6.1.4.1.838.3.10.2.1.2.1.17 |
xpolicyTxNextHopSelfSetting this object to the value 'true(1)' will set the BGP NEXT_HOP attribute to the local router address instead of leaving it as it was received from an EBGP peer.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.838.3.10.2.1.2.1.18 |
xpolicyTxRowStatusThis object is used to add and remove entries from the table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.838.3.10.2.1.2.1.19 |
xpolicyTxPrefixMinMinimum length of IP Address prefix to match in routing update destinations.rw INTEGER .1.3.6.1.4.1.838.3.10.2.1.2.1.20 |
xpolicyTxPrefixMaxMaximum length of IP Address prefix to match in routing update destinations.rw INTEGER .1.3.6.1.4.1.838.3.10.2.1.2.1.21 |
xpolicyDisplayTableThis table contains a read-only display of the internally linked list of policy entries. SEQUENCE OF XpolicyDisplayEntry .1.3.6.1.4.1.838.3.10.2.2 |
xpolicyDisplayEntryIndividual piece of text information regarding a policy entry. XpolicyDisplayEntry .1.3.6.1.4.1.838.3.10.2.2.1 |
xpolicyDisplayIndexThe row number in the table. Integer32 .1.3.6.1.4.1.838.3.10.2.2.1.1 |
xpolicyRxDisplayStringA single text line of information about a particular Receive policy.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.838.3.10.2.2.1.2 |
xpolicyTxDisplayStringA single text line of information about a particular Send policy.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.838.3.10.2.2.1.3 |
xpolicyPeerGroupTableThis table contains configuration for policy peer group members. SEQUENCE OF XpolicyPeerGroupEntry .1.3.6.1.4.1.838.3.10.2.3 |
xpolicyPeerGroupEntryIndividual peer group configuration. XpolicyPeerGroupEntry .1.3.6.1.4.1.838.3.10.2.3.1 |
xpolicyPeerGroupIndexThe index used to identify this peer group.ro INTEGER .1.3.6.1.4.1.838.3.10.2.3.1.1 |
xpolicyPeerGroupPeerThe peer contained in this group.ro IpAddress .1.3.6.1.4.1.838.3.10.2.3.1.2 |
xpolicyPeerGroupRowStatusThis object is used to add and remove entries from the table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.838.3.10.2.3.1.3 |
xpolicyPriRouting OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.10.2.4 |
xpolicyPriReceiveTableThis entity's Route Policy Receive table. SEQUENCE OF XpolicyPriReceiveEntry .1.3.6.1.4.1.838.3.10.2.4.1 |
xpolicyPriReceiveEntryAn entry to the Route Policy Receive Table. XpolicyPriReceiveEntry .1.3.6.1.4.1.838.3.10.2.4.1.1 |
xpolicyPriRxProtocolThe protocol from which the update was received.ro Enumeration .1.3.6.1.4.1.838.3.10.2.4.1.1.1 |
xpolicyPriRxPeerThe destination IP address of the routing update. If it is zero, then all peers are accepted.rw IpAddress .1.3.6.1.4.1.838.3.10.2.4.1.1.2 |
xpolicyPriRxNameA unique name for this entry, including the optional priority number, which can be represented in dotted notation. When used, the priority numbers allow hiearchical matching. Format of the string is: <name>.<priority> Examples of strings: name, name.1, name.1.1, name.2ro XPriPolicyName .1.3.6.1.4.1.838.3.10.2.4.1.1.3 |
xpolicyPriRxAddrStartThe base of the IP Address range to match in routing update destinations.rw IpAddress .1.3.6.1.4.1.838.3.10.2.4.1.1.4 |
xpolicyPriRxAddrEndThe end of the IP Address range to match in routing update destinations.rw IpAddress .1.3.6.1.4.1.838.3.10.2.4.1.1.5 |
xpolicyPriRxAsStringA string describing a complete, or partial 'Autonomyous System' inwhich to perform matches. This string uses a limited form of regular expression syntax to define what values of an AS path to match. The special characters used are '^' and '$' to specify 'start' and 'end' respectively. 100 - a path with 100 in it ^100$ - exactly the path of 100 (adjacent AS) ^100 - any path starting with 100 100$ - any path ending with 100 100.200 - a path with the sequence 100.200 in it. note: this is only valid for routes sourced from BGP.rw XPolicyAsString .1.3.6.1.4.1.838.3.10.2.4.1.1.6 |
xpolicyPriRxCommunityIdAllows matching on one of the integers listed in the community attrubute list. This is only valid for routes sourced from BGP.rw INTEGER('00'h..'ffffffff'h) .1.3.6.1.4.1.838.3.10.2.4.1.1.7 |
xpolicyPriRxReceiveOptionReceive action/options taken on 'matching' entries.rw Enumeration .1.3.6.1.4.1.838.3.10.2.4.1.1.8 |
xpolicyPriRxLocalPrefA positive four byte integer defining the preference to a matched routes. Higher values assign greater preference. Internal routes use 0xffffffff. note: It is only used for BGP.rw Integer32 .1.3.6.1.4.1.838.3.10.2.4.1.1.9 |
xpolicyPriRxRowStatusThis object is used to add and remove entries from the table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.838.3.10.2.4.1.1.10 |
xpolicyPriRxPrefixMinMinimum length of IP Address prefix to match in routing update destinations.rw INTEGER .1.3.6.1.4.1.838.3.10.2.4.1.1.11 |
xpolicyPriRxPrefixMaxMaximum length of IP Address prefix to match in routing update destinations.rw INTEGER .1.3.6.1.4.1.838.3.10.2.4.1.1.12 |
xpolicyPriRxDistanceAdministrative distance value to be set to a matched route.rw INTEGER (-1..255) .1.3.6.1.4.1.838.3.10.2.4.1.1.13 |
xpolicyPriSendTableThis entity's Route Policy Send table. SEQUENCE OF XpolicyPriSendEntry .1.3.6.1.4.1.838.3.10.2.4.2 |
xpolicyPriSendEntryAn entry to the Route Policy Table. XpolicyPriSendEntry .1.3.6.1.4.1.838.3.10.2.4.2.1 |
xpolicyPriTxProtocolThe protocol identifying where the update will be sent.ro Enumeration .1.3.6.1.4.1.838.3.10.2.4.2.1.1 |
xpolicyPriTxPeerThe destination IP address of the routing update. If zero, then all peers receive them. For OSPF and RIP, this value should be zero. BGP should not use 0.rw IpAddress .1.3.6.1.4.1.838.3.10.2.4.2.1.2 |
xpolicyPriTxNameA unique name for this entry, including the optional priority number, which can be represented in dotted notation. When used, the priority numbers allow hiearchical matching. Format of the string is: <name>.<priority> Examples of strings: name, name.1, name.1.1, name.2ro XPriPolicyName .1.3.6.1.4.1.838.3.10.2.4.2.1.3 |
xpolicyPriTxSrcProtocolThe protocol identifying the origin of the update. Often this 'src protocol will be the same as the TX Protocol index. This allows routes learned by BGP to be filtered towards other BGP routes.rw Enumeration .1.3.6.1.4.1.838.3.10.2.4.2.1.4 |
xpolicyPriTxSrcProtSubTypeThe protocol sub-type discription. Currently, this only applies to OSPF entries.rw Enumeration .1.3.6.1.4.1.838.3.10.2.4.2.1.5 |
xpolicyPriTxAddrStartThe base of the IP Address range to match in routing update destinations.rw IpAddress .1.3.6.1.4.1.838.3.10.2.4.2.1.6 |
xpolicyPriTxAddrEndThe end of the IP Address range to match in routing update destinations.rw IpAddress .1.3.6.1.4.1.838.3.10.2.4.2.1.7 |
xpolicyPriTxAsStringA string describing a complete, or partial 'Autonomyous System' inwhich to perform matches. This string uses a limited form of regular expression syntax to define what values of an AS path to match. The special characters used are '^' and '$' to specify 'start' and 'end' respectively. 100 - a path with 100 in it ^100$ - exactly the path of 100 (adjacent AS) ^100 - any path starting with 100 100$ - any path ending with 100 100.200 - a path with the sequence 100.200 in it. note: this is only valid for routes sourced from BGP.rw XPolicyAsString .1.3.6.1.4.1.838.3.10.2.4.2.1.8 |
xpolicyPriTxCommunityIdAllows matching on one of the integers listed in the community attrubute list. This is only valid for routes sourced from BGP.rw INTEGER('00'h..'ffffffff'h) .1.3.6.1.4.1.838.3.10.2.4.2.1.9 |
xpolicyPriTxSendOptionSend action/options taken on 'matching' entries. Never, indicates that routes within the range are not sent to the peer. Normal, allows routes within the specified range to be sent to the peer. Aggregate adds the specified range to routes that are currently within the specified range. In the aggregate case, the range must be a power of two.rw Enumeration .1.3.6.1.4.1.838.3.10.2.4.2.1.10 |
xpolicyPriTxMEDThe 'Multi-Exit-Descriminator'. A lower value assigns a higher preference to the route. Normally, the MED attribute ia attached to all matched routes. Except in the case of 0xffffffff, which means the MED will not be sent. note: It is only used for BGP. If it is used (>0), then the 'xpolicyTxSendOption' can NOT be set to 'never'.rw Integer32 .1.3.6.1.4.1.838.3.10.2.4.2.1.11 |
xpolicyPriTxMEDAutoAdmininstative status for calculating the 'Multi-Exit-Descriminator' using IGP_metric + 1.rw Enumeration .1.3.6.1.4.1.838.3.10.2.4.2.1.12 |
xpolicyPriTxAsPrependThe number of times to prepend the router's AS to the transmitted AS path in updates to the peer for all matching routes. note: It is only used for BGP. If it is used (>0), then the 'xpolicyTxSendOption' can NOT be set to 'never'.rw Integer32 .1.3.6.1.4.1.838.3.10.2.4.2.1.13 |
xpolicyPriTxSendCommunityIdThe value that is added to the community attribute for all matched routes. note: It is only used for BGP. If it is used (>0), then the 'xpolicyTxSendOption' can NOT be set to 'never'.rw INTEGER('00'h..'ffffffff'h) .1.3.6.1.4.1.838.3.10.2.4.2.1.14 |
xpolicyPriTxIgpMetricThe metric used for IGP.rw Integer32 .1.3.6.1.4.1.838.3.10.2.4.2.1.15 |
xpolicyPriTxIgpMetricTypeType of metric being used. Currently, only for defining OSPF internal and external routes.rw Enumeration .1.3.6.1.4.1.838.3.10.2.4.2.1.16 |
xpolicyPriTxIgpMetricAutoAdministrative status for generating an 'auto' metric. If set to localPref, the igp's metric is igpMetric - localPref. If set to MED, the the igp's metric is igpMetric + MED. If set to igp, then the entry controls routes imported from one IGP to another.rw Enumeration .1.3.6.1.4.1.838.3.10.2.4.2.1.17 |
xpolicyPriTxNextHopSelfSetting this object to the value 'true(1)' will set the BGP NEXT_HOP attribute to the local router address instead of leaving it as it was received from an EBGP peer.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.838.3.10.2.4.2.1.18 |
xpolicyPriTxRowStatusThis object is used to add and remove entries from the table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.838.3.10.2.4.2.1.19 |
xpolicyPriTxPrefixMinMinimum length of IP Address prefix to match in routing update destinations.rw INTEGER .1.3.6.1.4.1.838.3.10.2.4.2.1.20 |
xpolicyPriTxPrefixMaxMaximum length of IP Address prefix to match in routing update destinations.rw INTEGER .1.3.6.1.4.1.838.3.10.2.4.2.1.21 |
xpolicyConformance OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.10.3 |
xpolicyCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.10.3.1 |
xpolicyComplianceThe compliance statement for all agents that support this MIB. A compliant agent implements all objects defined in this MIB. Unknown .1.3.6.1.4.1.838.3.10.3.1.1 |
xpolicyGroups OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.10.3.2 |
xpolicyAllGroupThe set of all accessible objects in this MIB. Unknown .1.3.6.1.4.1.838.3.10.3.2.1 |