The present state of this MPC egress cache entry.
The states are:
doesNotExist (1)
inactive (2)
active (3)
For example,if using the Finite State
Machine in Appendix 1.5,
the states active and flooding
are `active' state.
negative (4)
For example,if using the Finite
State Machine in Appendix 1.5,
the state purging is `negative'.
Parsed from file MPC-MIB.mib
Module: MPC-MIB.mib
The present state of this MPC egress cache entry.
The states are:
doesNotExist (1)
inactive (2)
active (3)
For example,if using the Finite State
Machine in Appendix 1.5,
the states active and flooding
are `active' state.
negative (4)
For example,if using the Finite
State Machine in Appendix 1.5,
the state purging is `negative'.
The present state of this MPC egress cache entry.
The states are:
doesNotExist (1)
inactive (2)
active (3)
For example,if using the Finite State
Machine in Appendix 1.5,
the states active and flooding
are `active' state.
negative (4)
For example,if using the Finite
State Machine in Appendix 1.5,
the state purging is `negative'.
Parsed from file MPOA100.MIB.txt
Company: None
Module: MPOA-MIB
The present state of this MPC egress cache entry.
The states are:
doesNotExist (1)
inactive (2)
active (3)
For example,if using the Finite State
Machine in Appendix 1.5,
the states active and flooding
are `active' state.
negative (4)
For example,if using the Finite
State Machine in Appendix 1.5,
the state purging is `negative'.
mpcEgressCacheEntryState OBJECT-TYPE SYNTAX INTEGER { doesNotExist(1), inactive(2), active (3), negative (4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The present state of this MPC egress cache entry. The states are: doesNotExist (1) inactive (2) active (3) For example,if using the Finite State Machine in Appendix 1.5, the states active and flooding are `active' state. negative (4) For example,if using the Finite State Machine in Appendix 1.5, the state purging is `negative'." REFERENCE "MPOA Letter Ballot, Appendix I.5." ::= { mpcEgressCacheEntry 5 }
mpcEgressCacheEntryState OBJECT-TYPE SYNTAX INTEGER { doesNotExist(1), inactive(2), active(3), negative(4) } ACCESS read-only STATUS mandatory DESCRIPTION "The present state of this MPC egress cache entry. The states are: doesNotExist (1) inactive (2) active (3) For example,if using the Finite State Machine in Appendix 1.5, the states active and flooding are `active' state. negative (4) For example,if using the Finite State Machine in Appendix 1.5, the state purging is `negative'." REFERENCE "MPOA Letter Ballot, Appendix I.5." ::= { mpcEgressCacheEntry 5 }
Vendor: ATM Forum
Module: MPC-MIB
[Automatically extracted from oidview.com]
mpcEgressCacheEntryState OBJECT-TYPE SYNTAX INTEGER { doesNotExist(1), inactive(2), active(3), negative(4) } ACCESS read-only STATUS mandatory DESCRIPTION "The present state of this MPC egress cache entry. The states are: doesNotExist (1) inactive (2) active (3) For example,if using the Finite State Machine in Appendix 1.5, the states active and flooding are `active' state. negative (4) For example,if using the Finite State Machine in Appendix 1.5, the state purging is `negative'." REFERENCE "MPOA Letter Ballot, Appendix I.5." ::= { mpcEgressCacheEntry 5 }
mpcEgressCacheEntryState OBJECT-TYPE SYNTAX INTEGER { doesNotExist(1), inactive(2), active (3), negative (4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The present state of this MPC egress cache entry. The states are: doesNotExist (1) inactive (2) active (3) For example,if using the Finite State Machine in Appendix 1.5, the states active and flooding are `active' state. negative (4) For example,if using the Finite State Machine in Appendix 1.5, the state purging is `negative'." REFERENCE "MPOA Letter Ballot, Appendix I.5." ::= { mpcEgressCacheEntry 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.353.5.8.1.1.2.15.1.1 | mpcEgressCacheId | 0 | 0 | Cache ID Provided by the MPS in the Cache Imposition Request. |
| 1.3.6.1.4.1.353.5.8.1.1.2.15.1.2 | mpcEgressCacheInetworkAddrType | 0 | 0 | Type of Internetwork Address in this cache entry. |
| 1.3.6.1.4.1.353.5.8.1.1.2.15.1.3 | mpcEgressCacheIDestAddr, mpcEgressCacheDestAddr | 0 | 0 | The destination internetwork layer address for which this entry is defined. |
| 1.3.6.1.4.1.353.5.8.1.1.2.15.1.4 | mpcEgressCachePrefixLen | 0 | 0 | Defines an equivalence class of addresses that match Prefix Length bit positions of the destination internetwork layer address. |
| 1.3.6.1.4.1.353.5.8.1.1.2.15.1.6 | mpcEgressCacheEgressCacheTagValid, mpcEgressCacheEncapTag | 0 | 0 | If the value of this object is true(1), then a valid Egress Cache Tag is present and the value of the Egress Cache Tag is in mpcE… |
| 1.3.6.1.4.1.353.5.8.1.1.2.15.1.7 | mpcEgressCacheEgressCacheTag | 0 | 0 | If a valid Egress Cache Tag is present, then this object contains the value of that tag. To determine if this object contains a … |
| 1.3.6.1.4.1.353.5.8.1.1.2.15.1.8 | mpcEgressCacheHoldTime | 0 | 0 | The remaining time for which this entry is valid. |
| 1.3.6.1.4.1.353.5.8.1.1.2.15.1.9 | mpcEgressCacheDataLinkHeader | 0 | 0 | The DataLink header that the egress client rebuilds the original DataLink packet with. |
| 1.3.6.1.4.1.353.5.8.1.1.2.15.1.10 | mpcEgressCacheIngressMpcDataAtmAddr, mpcEgressCacheIngressMpcAtmAddr | 0 | 0 | The Data ATM Address of the ingress MPC that issued the MPOA Resolution request |
| 1.3.6.1.4.1.353.5.8.1.1.2.15.1.11 | mpcEgressCacheLecIndex, mpcEgressCacheCIMPErrCode | 0 | 0 | This is the lecIndex of the LANE Client that this flow is associated with. This can be used to get the ELAN name as well as othe… |
| 1.3.6.1.4.1.353.5.8.1.1.2.15.1.12 | mpcEgressCacheServiceCategory, mpcEgressCacheRxPackets | 0 | 0 | This is a bitmap describing the service categories supported for this shortcut. This value represents an inclusive OR of the bit… |
| 1.3.6.1.4.1.353.5.8.1.1.2.15.1.13 | mpcEgressCacheRxOctets | 0 | 0 | None |