The state of this MPS Ingress cache.
The states are:
doesNotExist (1)
inactive (2)
For example,if using the Finite
State Machine in Appendix I.3,
the state resolving is `inactive'.
active (3)
For example,if using the Finite
State Machine in Appendix I.3,
the state resolved
is `active' state.
negative (4)
For example,if using the Finite
State Machine in Appendix I.3,
the state purging is `negative'.
Parsed from file MPOA-MIB.mib
Module: MPOA-MIB
The state of this MPS Ingress cache.
The states are:
doesNotExist (1)
inactive (2)
For example,if using the Finite
State Machine in Appendix I.3,
the state resolving is `inactive'.
active (3)
For example,if using the Finite
State Machine in Appendix I.3,
the state resolved
is `active' state.
negative (4)
For example,if using the Finite
State Machine in Appendix I.3,
the state purging is `negative'.
The state of this MPS Ingress cache.
The states are:
doesNotExist (1)
inactive (2)
For example,if using the Finite
State Machine in Appendix I.3,
the state resolving is `inactive'.
active (3)
For example,if using the Finite
State Machine in Appendix I.3,
the state resolved
is `active' state.
negative (4)
For example,if using the Finite
State Machine in Appendix I.3,
the state purging is `negative'.
Parsed from file MPOA100.MIB.txt
Company: None
Module: MPOA-MIB
The state of this MPS Ingress cache.
The states are:
doesNotExist (1)
inactive (2)
For example,if using the Finite
State Machine in Appendix I.3,
the state resolving is `inactive'.
active (3)
For example,if using the Finite
State Machine in Appendix I.3,
the state resolved
is `active' state.
negative (4)
For example,if using the Finite
State Machine in Appendix I.3,
the state purging is `negative'.
mpsIngressCacheEntryState OBJECT-TYPE SYNTAX INTEGER { doesNotExist(1), inactive(2), active(3), negative(4) } ACCESS read-only STATUS mandatory DESCRIPTION "The state of this MPS Ingress cache. The states are: doesNotExist (1) inactive (2) For example,if using the Finite State Machine in Appendix I.3, the state resolving is `inactive'. active (3) For example,if using the Finite State Machine in Appendix I.3, the state resolved is `active' state. negative (4) For example,if using the Finite State Machine in Appendix I.3, the state purging is `negative'." REFERENCE "Multiprotocol Over ATM, Letter Ballot, Appendix I.3." ::= { mpsIngressCacheEntry 4 }
mpsIngressCacheEntryState OBJECT-TYPE SYNTAX INTEGER { doesNotExist(1), inactive(2), active(3), negative(4) } ACCESS read-only STATUS mandatory DESCRIPTION "The state of this MPS Ingress cache. The states are: doesNotExist (1) inactive (2) For example,if using the Finite State Machine in Appendix I.3, the state resolving is `inactive'. active (3) For example,if using the Finite State Machine in Appendix I.3, the state resolved is `active' state. negative (4) For example,if using the Finite State Machine in Appendix I.3, the state purging is `negative'." REFERENCE "Multiprotocol Over ATM, Letter Ballot, Appendix I.3." ::= { mpsIngressCacheEntry 4 }
Vendor: ATM Forum
Module: MPOA-MIB
[Automatically extracted from oidview.com]
mpsImpositionState OBJECT-TYPE SYNTAX INTEGER { pending (1), done (2) } MAX-ACCESS read-only STATUS current DESCRIPTION "" ::= { mpsImpositionsEntry 4 }
mpsIngressCacheEntryState OBJECT-TYPE SYNTAX INTEGER { doesNotExist (1), inactive(2), active(3), negative(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The state of this MPS Ingress cache. The states are: doesNotExist (1) inactive (2) For example,if using the Finite State Machine in Appendix I.3, the state resolving is `inactive'. active (3) For example,if using the Finite State Machine in Appendix I.3, the state resolved is `active' state. negative (4) For example,if using the Finite State Machine in Appendix I.3, the state purging is `negative'." REFERENCE "Multiprotocol Over ATM, Letter Ballot, Appendix I.3." ::= { mpsIngressCacheEntry 4 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.353.5.8.1.1.3.7.1.1 | mpsIngressCacheDestInternetworkAddrType, mpsImpositionClientAtmAddr | 0 | 0 | The type of internetwork layer address of the Destination Address. |
| 1.3.6.1.4.1.353.5.8.1.1.3.7.1.2 | mpsIngressCacheDestAddr, mpsImpositionCacheID | 0 | 0 | The Ingress MPS Destination Internetwork Layer Address. |
| 1.3.6.1.4.1.353.5.8.1.1.3.7.1.3 | mpsIngressCachePrefixLen, mpsImpositionHoldTime | 0 | 0 | The Prefix Length of the mpsIngressCacheDestAddr. |
| 1.3.6.1.4.1.353.5.8.1.1.3.7.1.5 | mpsIngressCacheSrcInternetworkAddrType, mpsImpositionDataLinkHeader | 0 | 0 | The type of internetwork layer address of the Source Address. |
| 1.3.6.1.4.1.353.5.8.1.1.3.7.1.6 | mpsIngressCacheSrcAddr, mpsImpositionEncapTag | 0 | 0 | The Ingress MPS Source Internetwork Layer Address. |
| 1.3.6.1.4.1.353.5.8.1.1.3.7.1.7 | mpsIngressCacheSourceMpcCtrlAtmAddr, mpsImpositionSourceClientAtmAddr | 0 | 0 | The ATM Address from the source of this MPOA request. In other words, the Ingress MPC's Control Atm Address. |
| 1.3.6.1.4.1.353.5.8.1.1.3.7.1.8 | mpsIngressCacheResolvedAtmAddr | 0 | 0 | The ATM Address which has been resolved by an Egress MPC. |
| 1.3.6.1.4.1.353.5.8.1.1.3.7.1.9 | mpsIngressCacheHoldTime | 0 | 0 | Time interval that this value is valid. |
| 1.3.6.1.4.1.353.5.8.1.1.3.7.1.10 | mpsIngressCacheMpoaRequestId | 0 | 0 | The request ID contained in the MPOA resolution request from the local Ingress MPC. |
| 1.3.6.1.4.1.353.5.8.1.1.3.7.1.11 | mpsIngressCacheNhrpRequestId | 0 | 0 | The request ID which this MPS generates to identify the NHRP resolution request. |
| 1.3.6.1.4.1.353.5.8.1.1.3.7.1.12 | mpsIngressCacheServiceCategory | 0 | 0 | The service categories supported for this shortcut. |